Home
last modified time | relevance | path

Searched full:ref (Results 1 – 25 of 1313) sorted by relevance

12345678910>>...53

/Documentation/userspace-api/media/dvb/
Dfrontend-property-terrestrial-systems.rst17 - :ref:`DTV_API_VERSION <DTV-API-VERSION>`
19 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
21 - :ref:`DTV_TUNE <DTV-TUNE>`
23 - :ref:`DTV_CLEAR <DTV-CLEAR>`
25 - :ref:`DTV_FREQUENCY <DTV-FREQUENCY>`
27 - :ref:`DTV_MODULATION <DTV-MODULATION>`
29 - :ref:`DTV_BANDWIDTH_HZ <DTV-BANDWIDTH-HZ>`
31 - :ref:`DTV_INVERSION <DTV-INVERSION>`
33 - :ref:`DTV_CODE_RATE_HP <DTV-CODE-RATE-HP>`
35 - :ref:`DTV_CODE_RATE_LP <DTV-CODE-RATE-LP>`
[all …]
Dfrontend-property-satellite-systems.rst17 - :ref:`DTV_API_VERSION <DTV-API-VERSION>`
19 - :ref:`DTV_DELIVERY_SYSTEM <DTV-DELIVERY-SYSTEM>`
21 - :ref:`DTV_TUNE <DTV-TUNE>`
23 - :ref:`DTV_CLEAR <DTV-CLEAR>`
25 - :ref:`DTV_FREQUENCY <DTV-FREQUENCY>`
27 - :ref:`DTV_INVERSION <DTV-INVERSION>`
29 - :ref:`DTV_SYMBOL_RATE <DTV-SYMBOL-RATE>`
31 - :ref:`DTV_INNER_FEC <DTV-INNER-FEC>`
33 - :ref:`DTV_VOLTAGE <DTV-VOLTAGE>`
35 - :ref:`DTV_TONE <DTV-TONE>`
[all …]
Dfrontend-property-cable-systems.rst24 - :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_INVERSION <DTV-INVERSION>`
38 - :ref:`DTV_SYMBOL_RATE <DTV-SYMBOL-RATE>`
40 - :ref:`DTV_INNER_FEC <DTV-INNER-FEC>`
42 - :ref:`DTV_LNA <DTV-LNA>`
[all …]
/Documentation/userspace-api/media/v4l/
Ddev-capture.rst30 :ref:`VIDIOC_QUERYCAP` ioctl. As secondary device
31 functions they may also support the :ref:`video overlay <overlay>`
32 (``V4L2_CAP_VIDEO_OVERLAY``) and the :ref:`raw VBI capture <raw-vbi>`
40 Video capture devices shall support :ref:`audio input <audio>`,
41 :ref:`tuner`, :ref:`controls <control>`,
42 :ref:`cropping and scaling <crop>` and
43 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
44 :ref:`video input <video>` ioctls must be supported by all video
62 defaults. An example is given in :ref:`crop`.
68 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this
[all …]
Ddev-output.rst29 :ref:`VIDIOC_QUERYCAP` ioctl. As secondary device
30 functions they may also support the :ref:`raw VBI output <raw-vbi>`
38 Video output devices shall support :ref:`audio output <audio>`,
39 :ref:`modulator <tuner>`, :ref:`controls <control>`,
40 :ref:`cropping and scaling <crop>` and
41 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
42 :ref:`video output <video>` ioctls must be supported by all video
60 defaults. An example is given in :ref:`crop`.
65 and call the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer
75 of :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>`, and call the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
[all …]
Ddiff-v4l.rst14 V4L calls were removed from Kernel, but the library :ref:`libv4l`
22 not change from those used by V4L. They are listed in :ref:`devices`
23 and below in :ref:`v4l-dev`.
56 V4L2 drivers *may* support multiple opens, see :ref:`open` for details
65 :ref:`VIDIOC_QUERYCAP`.
72 capturing, video overlay and VBI capturing. See :ref:`open` for an
89 - The :ref:`video capture <capture>` interface is supported.
92 - The device has a :ref:`tuner or modulator <tuner>`.
95 - The :ref:`raw VBI capture <raw-vbi>` interface is supported.
98 - The :ref:`video overlay <overlay>` interface is supported.
[all …]
Dlibv4l-introduction.rst17 :ref:`v4l2grab <v4l2grab-example>`.
28 :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR24>`,
29 :ref:`V4L2_PIX_FMT_HM12 <V4L2-PIX-FMT-HM12>`,
30 :ref:`V4L2_PIX_FMT_JPEG <V4L2-PIX-FMT-JPEG>`,
31 :ref:`V4L2_PIX_FMT_MJPEG <V4L2-PIX-FMT-MJPEG>`,
32 :ref:`V4L2_PIX_FMT_MR97310A <V4L2-PIX-FMT-MR97310A>`,
33 :ref:`V4L2_PIX_FMT_OV511 <V4L2-PIX-FMT-OV511>`,
34 :ref:`V4L2_PIX_FMT_OV518 <V4L2-PIX-FMT-OV518>`,
35 :ref:`V4L2_PIX_FMT_PAC207 <V4L2-PIX-FMT-PAC207>`,
36 :ref:`V4L2_PIX_FMT_PJPG <V4L2-PIX-FMT-PJPG>`,
[all …]
Dvidioc-subdev-enum-mbus-code.rst38 call the :ref:`VIDIOC_SUBDEV_ENUM_MBUS_CODE` ioctl with a pointer to this
46 See :ref:`VIDIOC_SUBDEV_G_FMT` for more
67 :ref:`v4l2-mbus-format`.
71 :ref:`v4l2_subdev_format_whence <v4l2-subdev-format-whence>`.
74 - See :ref:`v4l2-subdev-mbus-code-flags`
95 subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
96 ioctl with :ref:`V4L2_MBUS_FRAMEFMT_SET_CSC <mbus-framefmt-set-csc>` set.
97 See :ref:`v4l2-mbus-format` on how to do this.
102 the subdevice when calling the :ref:`VIDIOC_SUBDEV_S_FMT <VIDIOC_SUBDEV_G_FMT>`
103 ioctl with :ref:`V4L2_MBUS_FRAMEFMT_SET_CSC <mbus-framefmt-set-csc>` set.
[all …]
Dvidioc-g-fmt.rst50 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` ioctl with a pointer to this structure the driver fills
61 :ref:`devices`. Good practice is to query the current parameters
63 application. When the application calls the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl with
70 prepare for data exchange. Finally the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl returns
71 the current format parameters as :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` does. Very simple,
74 application must implement the :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and :ref:`VIDIOC_S_FMT <VIDIOC_G_…
76 EINVAL error code on a :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` attempt. When I/O is already in
80 The :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl is equivalent to :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` …
87 The format as returned by :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` must be identical to what
88 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` returns for the same input or output.
[all …]
Ddv-timings.rst14 it is not possible to extend the :ref:`v4l2_std_id <v4l2-std-id>`
22 the timings of the formats in the :ref:`cea861` and :ref:`vesadmt`
27 :ref:`VIDIOC_ENUM_DV_TIMINGS` and
28 :ref:`VIDIOC_DV_TIMINGS_CAP` ioctls. To set
30 :ref:`VIDIOC_S_DV_TIMINGS <VIDIOC_G_DV_TIMINGS>` ioctl and to get
32 :ref:`VIDIOC_G_DV_TIMINGS <VIDIOC_G_DV_TIMINGS>` ioctl. To detect
34 :ref:`VIDIOC_QUERY_DV_TIMINGS` ioctl.
36 Applications can make use of the :ref:`input-capabilities` and
37 :ref:`output-capabilities` flags to determine whether the digital
Dtuner.rst17 returned by the :ref:`VIDIOC_ENUMINPUT` ioctl is
25 :ref:`VIDIOC_G_TUNER <VIDIOC_G_TUNER>` and
26 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` ioctls, respectively. The
27 struct :c:type:`v4l2_tuner` returned by :ref:`VIDIOC_G_TUNER <VIDIOC_G_TUNER>`
33 :ref:`VIDIOC_S_TUNER <VIDIOC_G_TUNER>` does not switch the
37 returned by the :ref:`VIDIOC_QUERYCAP` ioctl when the
50 :ref:`VIDIOC_ENUMOUTPUT` ioctl is set to
61 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctl where you
65 :ref:`VIDIOC_G_MODULATOR <VIDIOC_G_MODULATOR>` and
66 :ref:`VIDIOC_S_MODULATOR <VIDIOC_G_MODULATOR>` ioctl. Note that
[all …]
Ddev-overlay.rst20 files as :ref:`video capture <capture>` devices.
26 the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl.
47 :ref:`VIDIOC_QUERYCAP` ioctl. The overlay I/O
55 Video overlay devices shall support :ref:`audio input <audio>`,
56 :ref:`tuner`, :ref:`controls <control>`,
57 :ref:`cropping and scaling <crop>` and
58 :ref:`streaming parameter <streaming-par>` ioctls as needed. The
59 :ref:`video input <video>` and :ref:`video standard <standard>`
69 :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` and
70 :ref:`VIDIOC_S_FBUF <VIDIOC_G_FBUF>` ioctls are available to get and
[all …]
Duserp.rst13 :ref:`VIDIOC_QUERYCAP` ioctl is set. If the
15 must be determined by calling the :ref:`VIDIOC_REQBUFS` ioctl
25 :ref:`VIDIOC_REQBUFS` with the desired buffer type.
28 :ref:`VIDIOC_QUERYBUF <VIDIOC_QUERYBUF>` ioctl.
51 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl. Although buffers are commonly
53 :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` call. If required by the hardware the
61 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. The driver can unlock the
64 :ref:`VIDIOC_STREAMOFF <VIDIOC_STREAMON>` is called,
65 :ref:`VIDIOC_REQBUFS`, or when the device is closed.
80 more buffers can be dequeued. By default :ref:`VIDIOC_DQBUF
[all …]
Dquerycap.rst14 The :ref:`VIDIOC_QUERYCAP` ioctl is available to
16 query the :ref:`functions <devices>` and :ref:`I/O methods <io>`
19 Starting with kernel version 3.1, :ref:`VIDIOC_QUERYCAP`
22 :ref:`VIDIOC_QUERYCAP` to check if a specific ioctl
27 example :ref:`VIDIOC_ENUMINPUT` to learn about the
30 :ref:`VIDIOC_QUERYCAP` ioctl also allows driver
33 All V4L2 drivers must support :ref:`VIDIOC_QUERYCAP`.
Dvidioc-querycap.rst107 :ref:`device-capabilities`. The same physical device can export
119 :ref:`device-capabilities`. Should contain the available
147 :ref:`Video Capture <capture>` interface.
150 - The device supports the :ref:`multi-planar API <planar-apis>`
151 through the :ref:`Video Capture <capture>` interface.
155 :ref:`Video Output <output>` interface.
158 - The device supports the :ref:`multi-planar API <planar-apis>`
159 through the :ref:`Video Output <output>` interface.
166 - The device supports the :ref:`multi-planar API <planar-apis>`
170 - The device supports the :ref:`Video Overlay <overlay>`
[all …]
Dpixfmt-compressed.rst24 - TBD. See also :ref:`VIDIOC_G_JPEGCOMP <VIDIOC_G_JPEGCOMP>`,
25 :ref:`VIDIOC_S_JPEGCOMP <VIDIOC_G_JPEGCOMP>`.
32 :ref:`mpeg-control-id`.
40 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
60 H264 pipeline (using the :ref:`mem2mem` and :ref:`media-request-api`).
70 :ref:`associated Codec Control IDs <v4l2-mpeg-h264>`. Exactly
76 The syntax for this format is documented in :ref:`h264`, section
96 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
105 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
114 MPEG-2 pipeline (using the :ref:`mem2mem` and :ref:`media-request-api`).
[all …]
Dformat.rst26 :ref:`VIDIOC_G_FMT <VIDIOC_G_FMT>` and
27 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctls. Additionally the
28 :ref:`VIDIOC_TRY_FMT <VIDIOC_G_FMT>` ioctl can be used to examine
31 respective device section in :ref:`devices`. For a closer look at
32 image formats see :ref:`pixfmt`.
34 The :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl is a major turning-point in the
37 change controls or modify other properties. The first :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
53 When applications omit the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` ioctl its locking side
55 with the :ref:`VIDIOC_REQBUFS` ioctl or implicit
64 *may* support a switch using :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.
[all …]
/Documentation/devicetree/bindings/reset/
Dzynq-reset.txt35 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/devicetree/bindings/sound/
Dsimple-card.yaml16 $ref: /schemas/types.yaml#/definitions/phandle-array
21 $ref: /schemas/types.yaml#/definitions/phandle-array
26 $ref: /schemas/types.yaml#/definitions/flag
30 $ref: /schemas/types.yaml#/definitions/flag
34 $ref: /schemas/types.yaml#/definitions/uint32
38 $ref: /schemas/types.yaml#/definitions/uint32
45 $ref: /schemas/types.yaml#/definitions/uint32
51 $ref: /schemas/types.yaml#/definitions/flag
57 $ref: /schemas/types.yaml#/definitions/uint32
63 $ref: /schemas/types.yaml#/definitions/phandle-array
[all …]
/Documentation/userspace-api/media/
Dfdl-appendix.rst62 the :ref:`Document <fdl-document>` that deals exclusively with the
76 :ref:`Secondary Sections <fdl-secondary>` whose titles are designated,
78 :ref:`Document <fdl-document>` is released under this License.
85 :ref:`Document <fdl-document>` is released under this License.
90 A “Transparent” copy of the :ref:`Document <fdl-document>` means a
127 You may copy and distribute the :ref:`Document <fdl-document>` in any
136 :ref:`section 3 <fdl-section3>`.
147 If you publish printed copies of the :ref:`Document <fdl-document>`
149 :ref:`Cover Texts <fdl-cover-texts>`, you must enclose the copies in
157 :ref:`Document <fdl-document>` and satisfy these conditions, can be
[all …]
/Documentation/userspace-api/media/rc/
Dlirc-get-features.rst52 :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` can only be used for transmitting.
59 :ref:`LIRC_MODE_MODE2 <lirc-mode-MODE2>` is used. This also implies
60 that :ref:`LIRC_MODE_SCANCODE <lirc-mode-SCANCODE>` is also supported,
62 :ref:`lirc_set_rec_mode` to switch modes.
75 :ref:`LIRC_MODE_SCANCODE <lirc-mode-SCANCODE>` is used.
82 :ref:`ioctl LIRC_SET_SEND_CARRIER <LIRC_SET_SEND_CARRIER>`.
89 :ref:`ioctl LIRC_SET_SEND_DUTY_CYCLE <LIRC_SET_SEND_DUTY_CYCLE>`.
96 :ref:`ioctl LIRC_SET_TRANSMITTER_MASK <LIRC_SET_TRANSMITTER_MASK>`.
103 :ref:`ioctl LIRC_SET_REC_CARRIER <LIRC_SET_REC_CARRIER>`.
116 :ref:`ioctl LIRC_SET_REC_CARRIER_RANGE <LIRC_SET_REC_CARRIER_RANGE>`.
[all …]
/Documentation/devicetree/bindings/mmc/
Dmmc-controller.yaml38 $ref: /schemas/types.yaml#/definitions/flag
47 $ref: /schemas/types.yaml#/definitions/flag
71 $ref: /schemas/types.yaml#/definitions/flag
76 $ref: /schemas/types.yaml#/definitions/flag
85 $ref: /schemas/types.yaml#/definitions/uint32
92 $ref: /schemas/types.yaml#/definitions/uint32
97 $ref: /schemas/types.yaml#/definitions/flag
116 $ref: /schemas/types.yaml#/definitions/flag
122 $ref: /schemas/types.yaml#/definitions/flag
127 $ref: /schemas/types.yaml#/definitions/flag
[all …]
Dsdhci-am654.yaml14 - $ref: mmc-controller.yaml#
53 $ref: "/schemas/types.yaml#/definitions/uint32"
59 $ref: "/schemas/types.yaml#/definitions/uint32"
65 $ref: "/schemas/types.yaml#/definitions/uint32"
71 $ref: "/schemas/types.yaml#/definitions/uint32"
77 $ref: "/schemas/types.yaml#/definitions/uint32"
83 $ref: "/schemas/types.yaml#/definitions/uint32"
89 $ref: "/schemas/types.yaml#/definitions/uint32"
95 $ref: "/schemas/types.yaml#/definitions/uint32"
101 $ref: "/schemas/types.yaml#/definitions/uint32"
[all …]
/Documentation/devicetree/bindings/input/touchscreen/
Dtouchscreen.yaml15 $ref: /schemas/types.yaml#/definitions/uint32
20 $ref: /schemas/types.yaml#/definitions/uint32
25 $ref: /schemas/types.yaml#/definitions/uint32
29 $ref: /schemas/types.yaml#/definitions/uint32
33 $ref: /schemas/types.yaml#/definitions/uint32
38 $ref: /schemas/types.yaml#/definitions/uint32
42 $ref: /schemas/types.yaml#/definitions/uint32
46 $ref: /schemas/types.yaml#/definitions/uint32
51 $ref: /schemas/types.yaml#/definitions/uint32
56 $ref: /schemas/types.yaml#/definitions/uint32
[all …]
/Documentation/userspace-api/media/mediactl/
Dmedia-ioc-request-alloc.rst34 If the media device supports :ref:`requests <media-request-api>`, then
40 can be passed to the :ref:`VIDIOC_QBUF <VIDIOC_QBUF>`,
41 :ref:`VIDIOC_G_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>`,
42 :ref:`VIDIOC_S_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>` and
43 :ref:`VIDIOC_TRY_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>` ioctls.
46 :ref:`MEDIA_REQUEST_IOC_QUEUE` and re-initialized by calling
47 :ref:`MEDIA_REQUEST_IOC_REINIT`.
49 Finally, the file descriptor can be :ref:`polled <request-func-poll>` to wait
55 :ref:`here <media-request-life-time>` for more information.
62 :ref:`Generic Error Codes <gen-errors>` chapter.

12345678910>>...53