Home
last modified time | relevance | path

Searched full:discussed (Results 1 – 25 of 98) sorted by relevance

1234

/linux/Documentation/userspace-api/media/v4l/
H A Ddev-radio.rst44 Radio devices may have a couple audio controls (as discussed in
47 discussed in :ref:`tuner`) with index number zero to select the radio
H A Ddv-timings.rst10 The video standards discussed so far have been dealing with Analog TV
H A Ddiff-v4l.rst180 :c:type:`v4l2_input` as discussed in :ref:`video`.
203 discussed in :ref:`tuner`.
356 :c:type:`v4l2_audio` as discussed in :ref:`audio`.
H A Ddev-capture.rst89 discussed in :ref:`pixfmt`. See also the specification of the
H A Ddev-output.rst86 discussed in :ref:`pixfmt`. See also the specification of the
H A Dfunc-read.rst41 data in the buffer is discussed in the respective device interface
H A Dvidioc-g-fmt.rst118 - Raw VBI capture or output parameters. This is discussed in more
/linux/Documentation/trace/rv/
H A Dmonitor_wip.rst50 This problem was reported and discussed here:
/linux/Documentation/driver-api/usb/
H A Dwriting_musb_glue_layer.rst223 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/Documentation/networking/
H A Dbareudp.rst7 There are various L3 encapsulation standards using UDP being discussed to
H A Dmac80211-injection.rst15 The radiotap format is discussed in
/linux/tools/memory-model/Documentation/
H A Dordering.txt238 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/include/crypto/
H A Daead.h33 * pendants discussed in the following. In addition, for the AEAD operation,
426 * and how it is filled with data is discussed with the aead_request_*
447 * and how it is filled with data is discussed with the aead_request_*
/linux/Documentation/admin-guide/mm/
H A Dnuma_memory_policy.rst36 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/Documentation/driver-api/80211/
H A Dmac80211.rst67 Things related to AP mode should be discussed there.
H A Dmac80211-advanced.rst70 Some parts of the if_conf should be discussed here instead
/linux/Documentation/mm/
H A Dactive_mm.rst25 > discussed on the mailing lists---I just returned from vacation and
/linux/Documentation/process/
H A Dembargoed-hardware-issues.rst189 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/drivers/comedi/drivers/
H A Djr3_pci.h401 * the units value discussed on page 16. The full scales for Fx, Fy,
595 * respectively. The format of these two words is discussed on page
660 * values are discussed in the section detailing the force_units
/linux/Documentation/admin-guide/aoe/
H A Daoe.rst112 option discussed below) instead of /dev/etherd/interfaces to limit
/linux/Documentation/security/
H A Dlsm.rst57 This capabilities module is discussed further in
/linux/Documentation/virt/kvm/s390/
H A Ds390-pv.rst93 discussed before. Other data is either ignored or results in validity
/linux/Documentation/filesystems/fuse/
H A Dfuse-passthrough.rst55 discussed and worked on. The primary reasons for this restriction are detailed
/linux/Documentation/userspace-api/
H A Ddma-buf-alloc-exchange.rst143 in order to ensure a compatible and optimal pipeline, as discussed below.
314 In the latter case, the allocation is as discussed above, being provided with a
/linux/Documentation/scsi/
H A Dscsi_eh.rst174 This will be discussed further in [2-1].
179 performs during recovery. This will be discussed in [2-2].

1234