Searched full:do (Results 1 – 25 of 1167) sorted by relevance
12345678910>>...47
| /Documentation/devicetree/bindings/ |
| D | writing-bindings.rst | 17 - DO attempt to make bindings complete even if a driver doesn't support some
24 - DO use node names matching the class of the device. Many standard names are
27 - DO check that the example matches the documentation especially after making
42 - DO make 'compatible' properties specific. DON'T use wildcards in compatible
43 strings. DO use fallback compatibles when devices are the same as or a subset
44 of prior implementations. DO add new compatibles in case there are new
47 - DO use a vendor prefix on device specific property names. Consider if
54 - DO use common property unit suffixes for properties with scientific units.
57 - DO define properties in terms of constraints. How many entries? What are
64 - DO put all MMIO devices under a bus node and not at the top-level.
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 43 To reduce its OS jitter, do any of the following:
50 2. Do all eHCA-Infiniband-related work on other CPUs, including
62 To reduce its OS jitter, do the following:
73 To reduce its OS jitter, do one of the following:
93 Do all of the following:
103 do not offline any other CPUs, because doing so could force the
109 Do all of the following:
121 Do all of the following:
133 Do all of the following:
145 Do one or more of the following:
[all …]
|
| D | README.rst | 8 kernel, and what to do if something goes wrong.
70 Do NOT use the /usr/src/linux area! This area has a (usually
151 Do not skip this step even if you are only upgrading one minor
266 - Do a ``make`` to create a compressed kernel image. It is also
267 possible to do ``make install`` if you have lilo installed to suit the
270 To do the actual install, you have to be root, but none of the normal
274 will also have to do ``make modules_install``.
295 do a ``make modules_install``.
370 Alternatively, you can do the dump lookup by hand:
375 kernel setup. What you should do is take the hex value from the EIP
[all …]
|
| /Documentation/power/ |
| D | opp.rst | 111 Do not use this function in interrupt context.
117 /* Do things */
123 /* Do cpufreq things */
125 /* Do remaining things */
152 /* dont operate on the pointer.. just do a sanity check.. */
190 /* Do stuff like policy checks etc. */
197 /* do something when we can't satisfy the req */
198 /* do other stuff */
211 Do not use these functions in interrupt context.
217 implementation might choose to do something as follows::
[all …]
|
| D | swsusp.rst | 14 If you do resume from initrd after your filesystems are mounted...
22 between suspend and resume, it may do something wrong. If you change
60 should not do that.]
62 If you want to limit the suspend image size to N bytes, do::
138 You bought new UPS for your server. How do you install it without
143 seconds to failure. What do you do? Suspend to disk.
150 We do use the regular I/O paths. However we cannot restore the data
210 "platform" is actually right thing to do where supported, but
214 I do not understand why you have such strong objections to idea of
218 Do selective suspend during runtime power management, that's okay. But
[all …]
|
| /Documentation/sound/cards/ |
| D | audiophile-usb.rst | 41 * Digital Stereo Output (Do)
59 - Ai+Ao+Di+Do
64 - Ai+Ao+Do or Ai+Di+Ao or Ai+Di+Do or Di+Ao+Do
68 - Ai or Ao or Di or Do
73 * The Do port additionally supports surround-encoded AC-3 and DTS passthrough,
76 - Note that in this setup only the Do interface can be enabled
128 * hw:1,1 is Do in playback and Ai in capture
129 * hw:1,2 is Do in AC3/DTS passthrough mode
150 * playing a S16_BE encoded raw file to the Do port::
154 * playing an ac3 sample file to the Do port::
[all …]
|
| /Documentation/process/ |
| D | stable-api-nonsense.rst | 28 You think you want a stable kernel interface, but you really do not, and
42 the world, they neither see this interface, nor do they care about it at
47 that describes kernel drivers that do not have their source code
51 are real, and you do need to be aware of them at all times.)
110 current interfaces, or figure out a better way to do things. If they do
111 that, they then fix the current interfaces to work better. When they do
134 interfaces and do things in improper ways, causing the stability of the
142 to extra work for the USB developers. Since all Linux USB developers do
143 their work on their own time, asking programmers to do extra work for no
163 What to do
[all …]
|
| D | management-style.rst | 14 to do with reality. It started as a lark, but that doesn't mean that it
18 lead persons, not the people who do traditional management inside
57 needs to do is to turn the big and painful ones into small things where
70 Thus the key to avoiding big decisions becomes to just avoiding to do
112 actually do the work also think twice about whether it's worth doing or
118 Remember: they'd better know more about the details than you do, and
120 thing you can do as a manager is not to instill confidence, but rather a
121 healthy dose of critical thinking on what they do.
124 we just do both?" and look pitiful. Trust me, it works. If it's not
159 The problem with #1 is that it's very easy to do, since you can say
[all …]
|
| D | coding-style.rst | 115 we do y
119 while, do). E.g.:
151 ie a ``while`` in a do-statement or an ``else`` in an if-statement, like
156 do {
157 body of do-loop
180 Do not unnecessarily use braces where a single statement will do.
229 if, switch, case, for, do, while
238 Do not add spaces around (inside) parenthesized expressions. This example is
276 Do not leave trailing whitespace at the ends of lines. Some editors with
279 However, some such editors do not remove the whitespace if you end up not
[all …]
|
| /Documentation/scsi/ |
| D | qlogicfas.rst | 31 thing to do is load the kernel without resetting the hardware, which
59 Make sure it works properly under DOS. You should also do an initial FDISK
71 you can do multiple tests on smaller files. Then do a COMP to verify
73 tests, otherwise you will test your RAM and not the files). Then do
75 realbig.doc realbig.doc". Then do it after the computer gets warm.
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 58 testing services. If you do expose a branch that may be unstable in
61 - Do not rebase a branch that contains history created by others. If you
67 - Do not reparent a tree without a good reason to do so. Just being on a
71 - If you must reparent a repository, do not pick some random kernel commit
109 Subsystem maintainers find themselves having to do two types of merges:
128 branches. Failure to do so threatens the security of the development
162 should do it first.
174 So what should a maintainer do when there is a conflict between their
185 asking upstream to do.
188 resolve dependencies. These dependency issues do happen at times, and
[all …]
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 23 * Please use the standard multi-line comment style. Do not mix C and C++
63 through Lindent. Lindent is not perfect, and you may have to do some minor
117 only do it after you have already gathered enough data to be certain that the
130 possible. Do not use hwmon_device_register().
135 * Do not provide support for deprecated sysfs attributes.
137 * Do not create non-standard attributes unless really needed. If you have to use
138 non-standard attributes, or you believe you do, discuss it on the mailing list
144 capabilities. While we do not expect your driver to support everything the
|
| /Documentation/core-api/ |
| D | kref.rst | 38 You must initialize the kref after you allocate it. To do this, call
63 refcount cannot go to zero) you may do this without a lock.
72 holding a valid pointer, it is safe to do this without
93 . do stuff with data here
117 . do stuff with data here
136 do something like::
151 bad style. Don't do it.
156 to do a get then a put::
163 Just do the enqueue. A comment about this is always welcome::
211 The kref_put() return value is useful if you do not want to hold the
[all …]
|
| /Documentation/vm/ |
| D | active_mm.rst | 15 and when I do I feel better about more people reading them.
28 user-level page tables at all, so when we do a context switch into an
63 user exited on another CPU while a lazy user was still active, so you do
76 should generally just do
80 instead (which makes more sense anyway - the test is basically one of "do
|
| /Documentation/networking/ |
| D | 6lowpan.rst | 28 Example to evaluate the private usually you can do::
39 /* do great stuff which is ARPHRD_6LOWPAN related */
42 /* do 802.15.4 6LoWPAN handling here */
|
| /Documentation/locking/ |
| D | preempt-locking.rst | 62 means you can't do oddball things like acquire a lock and go off to
63 play while another task releases it. If you want to do something
79 preempt_enable_no_resched() decrement, but do not immediately preempt
88 Note that you do not need to explicitly prevent preemption if you are holding
96 know that the affected codepath does not do any of this. Best policy is to use
142 be made. Do note that calls from interrupt context or bottom half/ tasklets
143 are also protected by preemption locks and so may use the versions which do
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 12 do audio/video muxing/encoding/decoding makes it more complex than most.
21 This meant that all drivers had to do the setup of device instances and
23 to do right and many drivers never did do it correctly.
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-g-topology.rst | 133 - Unique ID for the entity. Do not expect that the ID will
135 do not hardcode entity IDs in an application.
170 - Unique ID for the interface. Do not expect that the ID will
172 do not hardcode interface IDs in an application.
220 - Unique ID for the pad. Do not expect that the ID will
222 do not hardcode pad IDs in an application.
255 - Unique ID for the link. Do not expect that the ID will
257 do not hardcode link IDs in an application.
|
| /Documentation/fb/ |
| D | intel810.rst | 84 Recommendation: do not set
132 Recommendation: do not set
147 Recommendation: do not set
155 Recommendation: do not set
159 Forces the hardware engine to do a "sync" or wait for the hardware
163 Recommendation: do not set
170 Recommendation: do not set
227 and just do a::
235 a. Do your usual method of configuring the kernel
|
| D | fbcon.rst | 39 you don't do anything, the kernel configuration tool will select one for you,
63 do a 'modprobe fbcon'.
204 So, how do we unbind fbcon from the console? Part of the answer is in
219 restored properly. The following is one of the several methods that you can do:
232 hardware to <vga state file>. You need to do this step only once as
265 you can reattach vesafb. However, to reattach vesafb, you need to do one of
270 a. Before detaching fbcon, do::
272 vbetool vbemode save > <vesa state file> # do once for each vesafb mode,
284 a. Before detaching fbcon, do::
317 do
[all …]
|
| /Documentation/admin-guide/blockdev/ |
| D | paride.rst | 102 of the parallel port communication protocols. If you do not know
143 (eg: LILO), how to do that is beyond the scope of this document.
272 do mkdev pd$D$P b 45 $[ $1 * 16 + $P ]
278 for u in 0 1 2 3 ; do pd $u ; done
279 for u in 0 1 2 3 ; do mkdev pcd$u b 46 $u ; done
280 for u in 0 1 2 3 ; do mkdev pf$u b 47 $u ; done
281 for u in 0 1 2 3 ; do mkdev pt$u c 96 $u ; done
282 for u in 0 1 2 3 ; do mkdev npt$u c 96 $[ $u + 128 ] ; done
283 for u in 0 1 2 3 ; do mkdev pg$u c 97 $u ; done
293 might do something like::
[all …]
|
| /Documentation/driver-api/driver-model/ |
| D | overview.rst | 30 computer: namely the ability to do seamless device "plug and play", power
45 Other bus layers are encouraged to do what has been done for the PCI layer.
66 driver model generally do not and should not touch the fields of struct device,
67 unless there is a compelling reason to do so.
102 If sysfs is not automatically mounted, you can always do it manually with::
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-mbus-code.rst | 97 See :ref:`v4l2-mbus-format` on how to do this.
104 See :ref:`v4l2-mbus-format` on how to do this.
111 See :ref:`v4l2-mbus-format` on how to do this.
118 See :ref:`v4l2-mbus-format` on how to do this.
125 See :ref:`v4l2-mbus-format` on how to do this.
|
| /Documentation/ABI/ |
| D | README | 32 layout of the files below for details on how to do this.)
54 with userspace developers to ensure that things do not
57 sure they are working in a proper way and do not need to
93 - Kernel-internal symbols. Do not rely on the presence, absence, location, or
|
| /Documentation/x86/ |
| D | tlb.rst | 19 Which method to do depends on a few things:
29 damage we do with a full flush. So, the larger the TLB, the
31 instructions have separate TLBs, as do different page sizes.
48 This will cause us to do the global flush for more cases.
|
12345678910>>...47