Searched full:discussed (Results 1 – 25 of 130) sorted by relevance
123456
| /Linux-v5.15/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 | dev-output.rst | 86 discussed in :ref:`pixfmt`. See also the specification of the
|
| D | dev-capture.rst | 89 discussed in :ref:`pixfmt`. See also the specification of the
|
| 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 | 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-v5.15/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-v5.15/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-v5.15/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-v5.15/Documentation/dev-tools/kunit/ |
| D | kunit-tool.rst | 98 The ``run`` command which is discussed above is equivalent to running all three
164 by the ``--qemu_config`` discussed later. If ``um`` is passed (or this
|
| /Linux-v5.15/include/crypto/ |
| D | aead.h | 31 * the *aead* pendants discussed in the following. In addition, for the AEAD
330 * and how it is filled with data is discussed with the aead_request_*
351 * and how it is filled with data is discussed with the aead_request_*
|
| D | hash.h | 444 * meaning as discussed for those separate functions.
474 * meaning as discussed for those separate three functions.
861 * meaning as discussed for those separate three functions.
990 * meaning as discussed for those separate functions.
|
| /Linux-v5.15/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-v5.15/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-v5.15/Documentation/vm/ |
| D | active_mm.rst | 21 > discussed on the mailing lists---I just returned from vacation and
|
| D | unevictable-lru.rst | 19 implementation. The latter design rationale is discussed in the context of an
367 mlock_fixup() simply returns. Because of the VMA filtering discussed above,
417 This has been discussed from the mlock/munlock perspective in the respective
605 when try_to_unmap() returns SWAP_MLOCK, as discussed above.
|
| /Linux-v5.15/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:
|
| /Linux-v5.15/Documentation/driver-api/80211/ |
| D | mac80211.rst | 67 Things related to AP mode should be discussed there.
|
| /Linux-v5.15/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.yaml | 67 The properties of mux-locked and parent-locked multiplexers are discussed
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 38 one of the more specific policy scopes discussed below. When
173 discussed in context, below, as required to explain the behavior.
357 API discussed below] or by another task using the /proc/<pid>/numa_maps
|
| /Linux-v5.15/Documentation/security/ |
| D | lsm.rst | 57 This capabilities module is discussed further in
|
| /Linux-v5.15/Documentation/virt/kvm/ |
| D | s390-pv.rst | 93 discussed before. Other data is either ignored or results in validity
|
| /Linux-v5.15/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 112 option discussed below) instead of /dev/etherd/interfaces to limit
|
123456
