Searched full:being (Results 1 – 25 of 994) sorted by relevance
12345678910>>...40
| /Documentation/devicetree/bindings/sound/ |
| D | audio-graph.yaml | 26 Each entry is a pair of strings, the first being the
27 connection's sink, the second being the connection's source.
32 Each entry is a pair of strings, the first being the type of
34 second being the machine specific name for the widget.
|
| D | widgets.txt | 9 The "template-wname" being the template widget name and currently includes:
12 The "user-supplied-wname" being the user specified widget name.
|
| D | mxs-audio-sgtl5000.txt | 9 Each entry is a pair of strings, the first being the
10 connection's sink, the second being the connection's
|
| D | sound-card-common.yaml | 17 pair of strings, the first being the connection's sink, the second
18 being the connection's source.
|
| D | audio-graph-card2.yaml | 23 Each entry is a pair of strings, the first being the
24 connection's sink, the second being the connection's source.
|
| D | imx-audio-sgtl5000.txt | 14 Each entry is a pair of strings, the first being the
15 connection's sink, the second being the connection's
|
| D | rockchip,rk3288-hdmi-analog.txt | 10 Each entry is a pair of strings, the first being the
11 connection's sink, the second being the connection's
|
| D | omap-twl4030.txt | 13 Each entry is a pair of strings, the first being the connection's sink,
14 the second being the connection's source.
|
| D | mediatek,mt2701-wm8960.yaml | 24 pair of strings, the first being the connection's sink, the second
25 being the connection's source.
|
| D | davinci-evm-audio.txt | 9 Each entry is a pair of strings, the first being the connection's sink,
10 the second being the connection's source. Valid names for sources and
|
| /Documentation/ABI/testing/ |
| D | configfs-most | 44 collected from the network before being
61 a physical device is being attached to the bus.
99 collected from the network before being
116 a physical device is being attached to the bus.
154 collected from the network before being
171 a physical device is being attached to the bus.
220 collected from the network before being
237 a physical device is being attached to the bus.
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 44 are being evaluated::
52 control method is being evaluated::
61 control method is being evaluated for the first time::
110 methods are being evaluated::
118 control method is being evaluated::
127 control method is being evaluated for the first time::
136 specified control method is being evaluated::
145 specified control method is being evaluated for the first time::
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 54 and we never got a single complaint about nice +19 being too _weak_ in
55 terms of CPU utilization, we only got complaints about it (still) being
90 To address the first complaint (of nice levels being not "punchy"
98 To address the second complaint (of nice levels not being consistent),
108 The third complaint (of negative nice levels not being "punchy" enough
|
| /Documentation/process/ |
| D | management-style.rst | 97 the first place, and your decision ended up being a big one after
126 answer may end up being that both teams get so frustrated by the
139 Most people are idiots, and being a manager means you'll have to deal
166 right), the harder it ends up being to apologize afterwards.
175 The option of being unfailingly polite really doesn't exist. Nobody will
245 There's one thing people hate even more than being called "d*ckhead",
246 and that is being called a "d*ckhead" in a sanctimonious voice. The
259 internet, nobody can hear you being subtle". Use a big blunt object to
264 overboard to the point of being ridiculous can drive a point home
265 without making it painful to the recipient, who just thinks you're being
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 33 test subsystem should match a single kernel module. If the code being tested
38 Test subsystems should be named after the code being tested, either after the
39 module (wherever possible), or after the directory or files being tested. Test
80 functionality being tested. Test suites can have shared initialization and
129 function being tested, with a description of the input or codepath being tested.
161 * be listed either alongside the config entries for the driver/subsystem being
|
| /Documentation/devicetree/bindings/serial/ |
| D | snps-dw-apb-uart.yaml | 109 always be reported as active instead of being obtained from the modem
116 always be reported as active instead of being obtained from the modem
123 always be reported as active instead of being obtained from the modem
130 be reported as inactive instead of being obtained from the modem status
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 47 kthreads from being created in the first place. (This will
114 from being initiated from tasks that might run on the CPU to
126 from being initiated from tasks that might run on the CPU to
138 from being initiated from tasks that might run on the CPU to
167 chances of being selected to do the load balancing work that
299 kthreads from being created in the first place, and also obviates
303 kthreads from being created in the first place. This approach
313 another way of preventing any callbacks from being queued on the
328 kthreads from being created in the first place. However, please
|
| /Documentation/arch/powerpc/ |
| D | elfnote.rst | 29 being run on a machine with ultravisor, the kernel will probably crash
34 the kernel from being run if the PowerPC ultravisor capability doesn't exist
|
| /Documentation/trace/ |
| D | user_events.rst | 44 /* Input: Size of the user_reg structure being used */
96 allows programs to prevent themselves from being blocked when their event
197 /* Input: Size of the user_unreg structure being used */
268 with the first 4 bytes being equal to 1 and the last 4 bytes being equal to the
277 as payloads. In those cases writev() can be used, with the first vector being
278 the index and the following vector(s) being the actual event payload.
300 **NOTE:** *The write_index is not emitted out into the trace being recorded.*
|
| /Documentation/arch/arm64/ |
| D | tagged-pointers.rst | 40 result in an error code being returned, a (fatal) signal being raised,
60 on the tag information for user virtual addresses being maintained
|
| /Documentation/input/ |
| D | userio.rst | 43 ``type`` describes the type of command that is being sent. This can be any one
68 Sets the type of port we're emulating, where ``data`` is the port type being
76 ``data`` is the interrupt data being sent.
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 57 infrastructure (introspection APIs in kernel, libbpf support, etc), being
61 a dedicated "container" object. On the other hand, by being a map, it can be
66 with hashed task's tgid being a look up key to preserve order, but reduce
168 record is still being worked on, and discard bit, which might be set at commit
195 a self-pacing notifications of new data being availability.
197 being available after commit only if consumer has already caught up right up to
198 the record being committed. If not, consumer still has to catch up and thus
|
| D | prog_cgroup_sysctl.rst | 30 * ``write`` indicates whether sysctl value is being read (``0``) or written
33 * ``file_pos`` indicates file position sysctl is being accessed at, read
71 * ``bpf_sysctl_get_new_value()`` to get new string value currently being
75 * ``bpf_sysctl_set_new_value()`` to override new string value currently being
|
| /Documentation/rust/ |
| D | quick-start.rst | 110 If ``rustup`` is being used, enter the kernel build directory (or use
133 If ``rustup`` is being used, run::
213 If ``rustup`` is being used, its ``default`` profile already installs the tool,
214 thus nothing needs to be done. If another profile is being used, the component
229 If ``rustup`` is being used, its ``default`` profile already installs the tool,
230 thus nothing needs to be done. If another profile is being used, the component
249 If ``rustup`` is being used, all the profiles already install the tool,
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/cpm/ |
| D | i2c.txt | 14 unspecified, a default frequency of 60kHz is being used.
22 being used. The definition of the classes can be found in
|
12345678910>>...40