Searched full:ref (Results 1 – 25 of 719) sorted by relevance
12345678910>>...29
| /Documentation/media/uapi/dvb/ |
| D | frontend-property-terrestrial-systems.rst | 24 - :ref:`DTV_API_VERSION <DTV-API-VERSION>`
26 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
28 - :ref:`DTV_TUNE <DTV-TUNE>`
30 - :ref:`DTV_CLEAR <DTV-CLEAR>`
32 - :ref:`DTV_FREQUENCY <DTV-FREQUENCY>`
34 - :ref:`DTV_MODULATION <DTV-MODULATION>`
36 - :ref:`DTV_BANDWIDTH_HZ <DTV-BANDWIDTH-HZ>`
38 - :ref:`DTV_INVERSION <DTV-INVERSION>`
40 - :ref:`DTV_CODE_RATE_HP <DTV-CODE-RATE-HP>`
42 - :ref:`DTV_CODE_RATE_LP <DTV-CODE-RATE-LP>`
[all …]
|
| D | frontend-property-satellite-systems.rst | 24 - :ref:`DTV_API_VERSION <DTV-API-VERSION>`
26 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
28 - :ref:`DTV_TUNE <DTV-TUNE>`
30 - :ref:`DTV_CLEAR <DTV-CLEAR>`
32 - :ref:`DTV_FREQUENCY <DTV-FREQUENCY>`
34 - :ref:`DTV_INVERSION <DTV-INVERSION>`
36 - :ref:`DTV_SYMBOL_RATE <DTV-SYMBOL-RATE>`
38 - :ref:`DTV_INNER_FEC <DTV-INNER-FEC>`
40 - :ref:`DTV_VOLTAGE <DTV-VOLTAGE>`
42 - :ref:`DTV_TONE <DTV-TONE>`
[all …]
|
| D | frontend-property-cable-systems.rst | 31 - :ref:`DTV_API_VERSION <DTV-API-VERSION>`
33 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
35 - :ref:`DTV_TUNE <DTV-TUNE>`
37 - :ref:`DTV_CLEAR <DTV-CLEAR>`
39 - :ref:`DTV_FREQUENCY <DTV-FREQUENCY>`
41 - :ref:`DTV_MODULATION <DTV-MODULATION>`
43 - :ref:`DTV_INVERSION <DTV-INVERSION>`
45 - :ref:`DTV_SYMBOL_RATE <DTV-SYMBOL-RATE>`
47 - :ref:`DTV_INNER_FEC <DTV-INNER-FEC>`
49 - :ref:`DTV_LNA <DTV-LNA>`
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | dev-output.rst | 36 :ref:`VIDIOC_QUERYCAP` ioctl. As secondary device
37 functions they may also support the :ref:`raw VBI output <raw-vbi>`
46 Video output devices shall support :ref:`audio output <audio>`,
47 :ref:`modulator <tuner>`, :ref:`controls <control>`,
48 :ref:`cropping and scaling <crop>` and
49 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
50 :ref:`video output <video>` ioctls must be supported by all video
63 As usual these parameters are *not* reset at :ref:`open() <func-open>`
69 defaults. An example is given in :ref:`crop`.
74 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer
[all …]
|
| D | dev-capture.rst | 37 :ref:`VIDIOC_QUERYCAP` ioctl. As secondary device
38 functions they may also support the :ref:`video overlay <overlay>`
39 (``V4L2_CAP_VIDEO_OVERLAY``) and the :ref:`raw VBI capture <raw-vbi>`
48 Video capture devices shall support :ref:`audio input <audio>`,
49 :ref:`tuner`, :ref:`controls <control>`,
50 :ref:`cropping and scaling <crop>` and
51 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
52 :ref:`video input <video>` ioctls must be supported by all video
65 As usual these parameters are *not* reset at :ref:`open() <func-open>`
71 defaults. An example is given in :ref:`crop`.
[all …]
|
| D | diff-v4l.rst | 20 V4L calls were removed from Kernel, but the library :ref:`libv4l`
29 not change from those used by V4L. They are listed in :ref:`devices`
30 and below in :ref:`v4l-dev`.
65 V4L2 drivers *may* support multiple opens, see :ref:`open` for details
75 :ref:`VIDIOC_QUERYCAP`.
82 capturing, video overlay and VBI capturing. See :ref:`open` for an
99 - The :ref:`video capture <capture>` interface is supported.
102 - The device has a :ref:`tuner or modulator <tuner>`.
105 - The :ref:`raw VBI capture <raw-vbi>` interface is supported.
108 - The :ref:`video overlay <overlay>` interface is supported.
[all …]
|
| D | func-select.rst | 57 With the :ref:`select() <func-select>` function applications can suspend
63 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. When buffers are already in
66 On success :ref:`select() <func-select>` returns the total number of bits set in
70 :ref:`VIDIOC_QBUF` or
71 :ref:`VIDIOC_STREAMON` yet the :ref:`select() <func-select>`
73 or ``writefds``, but subsequent :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>`
76 When use of the :ref:`read() <func-read>` function has been negotiated and the
77 driver does not capture yet, the :ref:`select() <func-select>` function starts
78 capturing. When that fails, :ref:`select() <func-select>` returns successful and
79 a subsequent :ref:`read() <func-read>` call, which also attempts to start
[all …]
|
| D | libv4l-introduction.rst | 23 :ref:`v4l2grab <v4l2grab-example>`.
35 :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR24>`,
36 :ref:`V4L2_PIX_FMT_HM12 <V4L2-PIX-FMT-HM12>`,
37 :ref:`V4L2_PIX_FMT_JPEG <V4L2-PIX-FMT-JPEG>`,
38 :ref:`V4L2_PIX_FMT_MJPEG <V4L2-PIX-FMT-MJPEG>`,
39 :ref:`V4L2_PIX_FMT_MR97310A <V4L2-PIX-FMT-MR97310A>`,
40 :ref:`V4L2_PIX_FMT_OV511 <V4L2-PIX-FMT-OV511>`,
41 :ref:`V4L2_PIX_FMT_OV518 <V4L2-PIX-FMT-OV518>`,
42 :ref:`V4L2_PIX_FMT_PAC207 <V4L2-PIX-FMT-PAC207>`,
43 :ref:`V4L2_PIX_FMT_PJPG <V4L2-PIX-FMT-PJPG>`,
[all …]
|
| D | func-poll.rst | 41 With the :ref:`poll() <func-poll>` function applications can suspend execution
47 the :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. For output devices this
49 queued up with the :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl for
54 On success :ref:`poll() <func-poll>` returns the number of file descriptors
62 :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>` the :ref:`poll() <func-poll>`
65 :ref:`VIDIOC_STREAMON <VIDIOC_STREAMON>` for a capture device but
66 hasn't yet called :ref:`VIDIOC_QBUF <VIDIOC_QBUF>`, the
67 :ref:`poll() <func-poll>` function succeeds and sets the ``POLLERR`` flag in
69 :ref:`poll() <func-poll>` to succeed as well, but it sets the ``POLLOUT`` and
72 If an event occurred (see :ref:`VIDIOC_DQEVENT`)
[all …]
|
| D | userp.rst | 19 :ref:`VIDIOC_QUERYCAP` ioctl is set. If the
21 must be determined by calling the :ref:`VIDIOC_REQBUFS` ioctl
31 :ref:`VIDIOC_REQBUFS` with the desired buffer type.
34 :ref:`VIDIOC_QUERYBUF <VIDIOC_QUERYBUF>` ioctl.
57 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl. Although buffers are commonly
59 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` call. If required by the hardware the
67 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. The driver can unlock the
70 :ref:`VIDIOC_STREAMOFF <VIDIOC_STREAMON>` is called,
71 :ref:`VIDIOC_REQBUFS`, or when the device is closed.
86 more buffers can be dequeued. By default :ref:`VIDIOC_DQBUF
[all …]
|
| D | func-read.rst | 37 File descriptor returned by :ref:`open() <func-open>`.
48 :ref:`read() <func-read>` attempts to read up to ``count`` bytes from file
51 section, see ##. If ``count`` is zero, :ref:`read() <func-read>` returns zero
54 :ref:`read() <func-read>` call will provide at most one frame (two fields)
57 By default :ref:`read() <func-read>` blocks until data becomes available. When
58 the ``O_NONBLOCK`` flag was given to the :ref:`open() <func-open>`
60 is available. The :ref:`select() <func-select>` or
61 :ref:`poll() <func-poll>` functions can always be used to suspend
63 :ref:`read() <func-read>` function must also support :ref:`select() <func-select>` and
64 :ref:`poll() <func-poll>`.
[all …]
|
| D | vidioc-g-fmt.rst | 38 File descriptor returned by :ref:`open() <func-open>`.
55 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills
66 :ref:`devices`. Good practice is to query the current parameters
68 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
75 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
76 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
79 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
81 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
85 The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl is equivalent to :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` …
92 The format as returned by :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` must be identical to what
[all …]
|
| D | dmabuf.rst | 24 Refer to :ref:`DMABUF exporting <VIDIOC_EXPBUF>` for details about
30 :ref:`VIDIOC_QUERYCAP <VIDIOC_QUERYCAP>` ioctl is set. Whether
32 determined by calling the :ref:`VIDIOC_REQBUFS <VIDIOC_REQBUFS>`
44 :ref:`VIDIOC_REQBUFS <VIDIOC_REQBUFS>` with the desired buffer type.
69 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl. In case of multiplanar
72 a different DMABUF descriptor at each :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` call.
129 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. The driver can unlock the
132 :ref:`VIDIOC_STREAMOFF <VIDIOC_STREAMON>` is called,
133 :ref:`VIDIOC_REQBUFS <VIDIOC_REQBUFS>`, or when the device is closed.
143 more buffers can be dequeued. By default :ref:`VIDIOC_DQBUF
[all …]
|
| D | dev-overlay.rst | 27 files as :ref:`video capture <capture>` devices.
33 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
54 :ref:`VIDIOC_QUERYCAP` ioctl. The overlay I/O
62 Video overlay devices shall support :ref:`audio input <audio>`,
63 :ref:`tuner`, :ref:`controls <control>`,
64 :ref:`cropping and scaling <crop>` and
65 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
66 :ref:`video input <video>` and :ref:`video standard <standard>`
76 :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` and
77 :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` ioctls are available to get and
[all …]
|
| D | tuner.rst | 24 returned by the :ref:`VIDIOC_ENUMINPUT` ioctl is
32 :ref:`VIDIOC_G_TUNER <VIDIOC_G_TUNER>` and
33 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` ioctls, respectively. The
34 struct :c:type:`v4l2_tuner` returned by :ref:`VIDIOC_G_TUNER <VIDIOC_G_TUNER>`
40 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` does not switch the
44 returned by the :ref:`VIDIOC_QUERYCAP` ioctl when the
57 :ref:`VIDIOC_ENUMOUTPUT` ioctl is set to
68 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctl where you
72 :ref:`VIDIOC_G_MODULATOR <VIDIOC_G_MODULATOR>` and
73 :ref:`VIDIOC_S_MODULATOR <VIDIOC_G_MODULATOR>` ioctl. Note that
[all …]
|
| D | vidioc-querycap.rst | 33 File descriptor returned by :ref:`open() <func-open>`.
116 :ref:`device-capabilities`. The same physical device can export
128 :ref:`device-capabilities`. Should contain the available
157 :ref:`Video Capture <capture>` interface.
160 - The device supports the :ref:`multi-planar API <planar-apis>`
161 through the :ref:`Video Capture <capture>` interface.
165 :ref:`Video Output <output>` interface.
168 - The device supports the :ref:`multi-planar API <planar-apis>`
169 through the :ref:`Video Output <output>` interface.
176 - The device supports the :ref:`multi-planar API <planar-apis>`
[all …]
|
| D | format.rst | 33 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
34 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
35 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine
38 respective device section in :ref:`devices`. For a closer look at
39 image formats see :ref:`pixfmt`.
41 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the
44 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
60 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
62 with the :ref:`VIDIOC_REQBUFS` ioctl or implicit
63 with the first :ref:`read() <func-read>` or
[all …]
|
| D | dv-timings.rst | 21 it is not possible to extend the :ref:`v4l2_std_id <v4l2-std-id>`
29 the timings of the formats in the :ref:`cea861` and :ref:`vesadmt`
34 :ref:`VIDIOC_ENUM_DV_TIMINGS` and
35 :ref:`VIDIOC_DV_TIMINGS_CAP` ioctls. To set
37 :ref:`VIDIOC_S_DV_TIMINGS <VIDIOC_G_DV_TIMINGS>` ioctl and to get
39 :ref:`VIDIOC_G_DV_TIMINGS <VIDIOC_G_DV_TIMINGS>` ioctl. To detect
41 :ref:`VIDIOC_QUERY_DV_TIMINGS` ioctl.
43 Applications can make use of the :ref:`input-capabilities` and
44 :ref:`output-capabilities` flags to determine whether the digital
|
| D | hist-v4l2.rst | 30 1998-08-27: The :ref:`select() <func-select>` function was introduced.
35 meaningless ``O_TRUNC`` :ref:`open() <func-open>` flag, and the
48 renamed. The :ref:`VIDIOC_QUERYSTD` ioctl was
49 renamed to :ref:`VIDIOC_ENUMSTD`,
50 :ref:`VIDIOC_G_INPUT <VIDIOC_G_INPUT>` to
51 :ref:`VIDIOC_ENUMINPUT`. A first draft of the
62 :ref:`VIDIOC_G_CTRL <VIDIOC_G_CTRL>` and
63 :ref:`VIDIOC_S_CTRL <VIDIOC_G_CTRL>` ioctls under names starting
152 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
153 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl taking a union and a
[all …]
|
| /Documentation/devicetree/bindings/reset/ |
| D | zynq-reset.txt | 35 166: gem0 ref reset
36 167: gem1 ref reset
39 196: sdio0 ref reset
40 197: sdio1 ref reset
43 226: spi0 ref reset
44 227: spi1 ref reset
47 258: can0 ref reset
48 259: can1 ref reset
53 322: uart0 ref reset
54 323: uart1 ref reset
[all …]
|
| /Documentation/media/uapi/ |
| D | fdl-appendix.rst | 69 the :ref:`Document <fdl-document>` that deals exclusively with the
83 :ref:`Secondary Sections <fdl-secondary>` whose titles are designated,
85 :ref:`Document <fdl-document>` is released under this License.
92 :ref:`Document <fdl-document>` is released under this License.
97 A “Transparent” copy of the :ref:`Document <fdl-document>` means a
134 You may copy and distribute the :ref:`Document <fdl-document>` in any
143 :ref:`section 3 <fdl-section3>`.
154 If you publish printed copies of the :ref:`Document <fdl-document>`
156 :ref:`Cover Texts <fdl-cover-texts>`, you must enclose the copies in
164 :ref:`Document <fdl-document>` and satisfy these conditions, can be
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-controller.yaml | 34 $ref: /schemas/types.yaml#/definitions/flag
43 $ref: /schemas/types.yaml#/definitions/flag
67 $ref: /schemas/types.yaml#/definitions/flag
72 $ref: /schemas/types.yaml#/definitions/flag
80 - $ref: /schemas/types.yaml#/definitions/uint32
88 - $ref: /schemas/types.yaml#/definitions/uint32
95 $ref: /schemas/types.yaml#/definitions/flag
115 $ref: /schemas/types.yaml#/definitions/flag
121 $ref: /schemas/types.yaml#/definitions/flag
126 $ref: /schemas/types.yaml#/definitions/flag
[all …]
|
| /Documentation/media/uapi/rc/ |
| D | lirc-get-features.rst | 59 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` can only be used for transmitting.
66 :ref:`LIRC_MODE_MODE2 <lirc-mode-MODE2>` is used. This also implies
67 that :ref:`LIRC_MODE_SCANCODE <lirc-mode-SCANCODE>` is also supported,
69 :ref:`lirc_set_rec_mode` to switch modes.
82 :ref:`LIRC_MODE_SCANCODE <lirc-mode-SCANCODE>` is used.
89 :ref:`ioctl LIRC_SET_SEND_CARRIER <LIRC_SET_SEND_CARRIER>`.
96 :ref:`ioctl LIRC_SET_SEND_DUTY_CYCLE <LIRC_SET_SEND_DUTY_CYCLE>`.
103 :ref:`ioctl LIRC_SET_TRANSMITTER_MASK <LIRC_SET_TRANSMITTER_MASK>`.
110 :ref:`ioctl LIRC_SET_REC_CARRIER <LIRC_SET_REC_CARRIER>`.
123 :ref:`ioctl LIRC_SET_REC_CARRIER_RANGE <LIRC_SET_REC_CARRIER_RANGE>`.
[all …]
|
| /Documentation/devicetree/bindings/arm/socionext/ |
| D | uniphier.txt | 11 - Reference Board: "socionext,uniphier-ld4-ref"
14 - Reference Board: "socionext,uniphier-pro4-ref"
19 - Reference Board: "socionext,uniphier-sld8-ref"
26 - Reference Board: "socionext,uniphier-ld6b-ref"
29 - Reference Board: "socionext,uniphier-ld11-ref"
33 - Reference Board: "socionext,uniphier-ld20-ref"
37 - Reference Board: "socionext,uniphier-pxs3-ref"
44 compatible = "socionext,uniphier-ld20-ref", "socionext,uniphier-ld20";
|
| /Documentation/translations/zh_CN/process/ |
| D | programming-language.rst | 3 :Original: :ref:`Documentation/process/programming-language.rst <programming_language>`
11 内核是用C语言 :ref:`c-language <cn_c-language>` 编写的。更准确地说，内核通常是用 :ref:`gcc <cn_gcc>`
12 在 ``-std=gnu89`` :ref:`gcc-c-dialect-options <cn_gcc-c-dialect-options>` 下编译的：ISO C90的 GNU 方言（
15 这种方言包含对语言 :ref:`gnu-extensions <cn_gnu-extensions>` 的许多扩展，当然，它们许多都在内核中使用。
17 对于一些体系结构，有一些使用 :ref:`clang <cn_clang>` 和 :ref:`icc <cn_icc>` 编译内核
23 在整个内核中使用的一个常见扩展是属性（attributes） :ref:`gcc-attribute-syntax <cn_gcc-attribute-syntax>`
25 重大的语法更改（例如添加新关键字） :ref:`n2049 <cn_n2049>`
|
12345678910>>...29