Searched full:discussed (Results 1 – 25 of 147) sorted by relevance
123456
| /linux-6.14.4/Documentation/userspace-api/media/v4l/ |
| D | dev-radio.rst | 43 Radio devices may have a couple audio controls (as discussed in
46 discussed in :ref:`tuner`) with index number zero to select the radio
|
| D | dv-timings.rst | 9 The video standards discussed so far have been dealing with Analog TV
|
| D | diff-v4l.rst | 180 :c:type:`v4l2_input` as discussed in :ref:`video`.
203 discussed in :ref:`tuner`.
356 :c:type:`v4l2_audio` as discussed in :ref:`audio`.
|
| D | dev-capture.rst | 89 discussed in :ref:`pixfmt`. See also the specification of the
|
| D | dev-output.rst | 86 discussed in :ref:`pixfmt`. See also the specification of the
|
| D | func-read.rst | 41 data in the buffer is discussed in the respective device interface
|
| D | vidioc-g-fmt.rst | 118 - Raw VBI capture or output parameters. This is discussed in more
|
| /linux-6.14.4/Documentation/driver-api/pm/ |
| D | devices.rst | 522 1. The ``prepare`` phase is discussed in the "Entering System Suspend"
536 discussed earlier, except again that the device should not be put into
544 discussed earlier. The main difference is that its methods can assume
552 7. The ``thaw`` phase is analogous to the ``resume`` phase discussed
556 8. The ``complete`` phase is discussed in the "Leaving System Suspend"
564 9. The ``prepare`` phase is discussed above.
633 4. The ``complete`` phase is discussed above.
651 callbacks discussed above, because the callbacks occur too late or too early.
|
| /linux-6.14.4/Documentation/locking/ |
| D | seqlock.rst | 95 As discussed at :ref:`seqcount_t`, sequence count write side critical
164 This contains the :ref:`seqcount_t` mechanism earlier discussed, plus an
|
| /linux-6.14.4/Documentation/trace/rv/ |
| D | monitor_wip.rst | 50 This problem was reported and discussed here:
|
| /linux-6.14.4/Documentation/networking/ |
| D | bareudp.rst | 7 There are various L3 encapsulation standards using UDP being discussed to
|
| D | mac80211-injection.rst | 15 The radiotap format is discussed in
|
| /linux-6.14.4/include/crypto/ |
| D | aead.h | 33 * pendants discussed in the following. In addition, for the AEAD operation,
345 * and how it is filled with data is discussed with the aead_request_*
366 * and how it is filled with data is discussed with the aead_request_*
|
| D | hash.h | 434 * meaning as discussed for those separate functions.
464 * meaning as discussed for those separate three functions.
820 * meaning as discussed for those separate three functions.
938 * meaning as discussed for those separate functions.
|
| /linux-6.14.4/Documentation/driver-api/usb/ |
| D | writing_musb_glue_layer.rst | 223 driver (line 16). Platform data will be discussed in
276 will be discussed later in :ref:`musb-dev-quirks` and
400 device controller, which will be discussed later in :ref:`musb-dev-quirks`.
552 registers. This issue will be discussed when we get to device quirks in
|
| /linux-6.14.4/tools/memory-model/Documentation/ |
| D | ordering.txt | 238 Note that the barriers discussed previously use barrier() or its low-level
488 discussed in the "RMW Ordering Augmentation Barriers" section.
512 primitive can be helpful, as can the various ordering primitives discussed
|
| /linux-6.14.4/Documentation/process/ |
| D | 1.Intro.rst | 28 have been encountered by other developers are discussed. Some requirements for
130 discussed in greater detail later in this document. Consider:
|
| D | embargoed-hardware-issues.rst | 189 Patches are posted, discussed, and reviewed and if agreed upon, applied to
225 The patches discussed and developed on the list can neither be distributed
|
| /linux-6.14.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.yaml | 66 The properties of mux-locked and parent-locked multiplexers are discussed
|
| /linux-6.14.4/Documentation/mm/ |
| D | active_mm.rst | 25 > discussed on the mailing lists---I just returned from vacation and
|
| D | physical_memory.rst | 30 be discussed further in Section :ref:`Nodes <nodes>`
79 discussed further in Section :ref:`Zones <zones>`.
|
| /linux-6.14.4/Documentation/driver-api/80211/ |
| D | mac80211.rst | 67 Things related to AP mode should be discussed there.
|
| /linux-6.14.4/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 36 one of the more specific policy scopes discussed below. When
171 discussed in context, below, as required to explain the behavior.
364 API discussed below] or by another task using the /proc/<pid>/numa_maps
|
| /linux-6.14.4/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 112 option discussed below) instead of /dev/etherd/interfaces to limit
|
| /linux-6.14.4/Documentation/security/ |
| D | lsm.rst | 57 This capabilities module is discussed further in
|
123456