| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | standard.rst | 6 Video Standards
9 Video devices typically support one or more different video standards or
10 variations of standards. Each video input and output may support another
11 set of standards. This set is reported by the ``std`` field of struct
18 worldwide, and sets aside bits for driver defined standards, e. g.
19 hybrid standards to watch NTSC video tapes on PAL TVs and vice versa.
21 standard, although presenting the user a menu of supported standards is
23 standards applications use the :ref:`VIDIOC_ENUMSTD`
26 Many of the defined standards are actually just variations of a few
27 major standards. The hardware may in fact not distinguish between them,
[all …]
|
| H A D | vidioc-enumstd.rst | 13 VIDIOC_ENUMSTD - VIDIOC_SUBDEV_ENUMSTD - Enumerate supported video standards
43 bounds. To enumerate all standards applications shall begin at index
45 enumerate a different set of standards after switching the video input
63 standards listed in :ref:`v4l2-std-id`, or if bits 32 to 63 are
64 set as custom standards. Multiple bits can be set if the hardware
65 does not distinguish between these standards, however separate
115 as listed below and in :ref:`video-standards`. The 32 most
117 standards.
168 terrestrial digital TV standards. Presently the V4L2 API does not
233 .. _video-standards:
[all …]
|
| H A D | vidioc-dv-timings-cap.rst | 86 - ``standards``
88 :ref:`dv-bt-standards` for a list of standards.
152 the standards set in the ``standards`` field.
|
| H A D | vidioc-g-dv-timings.rst | 60 the formats in the :ref:`cea861` and :ref:`vesadmt` standards. If
151 - ``standards``
154 :ref:`dv-bt-standards` for a list of standards.
222 .. _dv-bt-standards:
224 .. flat-table:: DV BT Timing standards
264 1.001 speed to be compatible with 60 Hz based standards such as
|
| H A D | vidioc-enumoutput.rst | 86 - Every video output supports one or more different video standards.
87 This field is a set of all supported standards. For details on
88 video standards and how to switch see :ref:`standard`.
|
| H A D | vidioc-querystd.rst | 42 supported standards if for example the hardware can only distinguish
45 the set must contain all standards supported by the current video input
|
| H A D | dv-timings.rst | 9 The video standards discussed so far have been dealing with Analog TV
23 standards.
|
| H A D | vidioc-enuminput.rst | 85 - Every video input supports one or more different video standards.
86 This field is a set of all supported standards. For details on
87 video standards and how to switch see :ref:`standard`.
|
| H A D | colorspaces.rst | 147 colorspace standards correctly define all four, quite often the
149 standards for the missing pieces. The fact that colorspaces are often a
150 mix of different standards also led to very confusing naming conventions
|
| /linux/Documentation/devicetree/bindings/display/connector/ |
| H A D | analog-tv-connector.yaml | 20 sdtv-standards:
22 Limit the supported TV standards on a connector to the given ones. If
23 not specified all TV standards are allowed. Possible TV standards are
24 defined in include/dt-bindings/display/sdtv-standards.h.
39 #include <dt-bindings/display/sdtv-standards.h>
44 sdtv-standards = <(SDTV_STD_PAL | SDTV_STD_NTSC)>;
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | dvbproperty.rst | 14 TV standards, and may change as the digital TV specs evolves.
19 generation standards appeared, the size of such union was not big
21 standards. Also, extending it would break userspace.
40 newer standards. Such API provides no support or a very limited
41 support to new standards and/or new hardware.
114 provides abstraction to work with the supported digital TV standards and
|
| /linux/Documentation/userspace-api/media/ |
| H A D | intro.rst | 29 Internet reception via one of the several digital tv standards. While it is
30 called as DVB API, in fact it covers several different video standards
32 complete list of supported standards can be found at
|
| /linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | techwell,tw9900.yaml | 13 The tw9900 is a multi-standard video decoder, supporting NTSC, PAL standards
88 #include <dt-bindings/display/sdtv-standards.h>
94 sdtv-standards = <(SDTV_STD_PAL | SDTV_STD_NTSC)>;
|
| /linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 14 NVM Express is an open collection of standards and information.
62 Sometimes implementations of open standards fail to correctly implement parts
63 of the standards. Linux uses identifier-based quirks to work around such
|
| /linux/drivers/net/wireless/mediatek/mt76/mt76x0/ |
| H A D | Kconfig | 14 which comply with IEEE 802.11ac standards and support 1x1
26 which comply with IEEE 802.11ac standards and support 1x1
|
| /linux/include/net/ |
| H A D | dscp.h | 17 * Pool 1 (Standards Action Pool):
20 * Standards Action. It is intended for globally recognized traffic classes,
36 * values ending in '01' (binary) are assigned via Standards Action, with a
|
| /linux/drivers/net/wireless/mediatek/mt76/mt76x2/ |
| H A D | Kconfig | 13 devices, which comply with IEEE 802.11ac standards and support
26 which comply with IEEE 802.11ac standards and support 2SS to
|
| /linux/Documentation/driver-api/media/ |
| H A D | dtv-core.rst | 27 .. [#f1] Some standards use TCP/IP for multiplexing data, like DVB-H (an
29 proposals. Currently, the DVB subsystem doesn't implement those standards.
|
| H A D | dtv-frontend.rst | 20 tells what type of digital TV standards are supported, and points to a
100 #) For satellite digital TV standards (DVB-S, DVB-S2, ISDB-S), the
102 standards, they're specified in Hz. Due to that, if the same frontend
117 #) Other callbacks are required for satellite TV standards, in order to
179 that's usually 1 for most video standards [#f2]_.
|
| /linux/include/dt-bindings/display/ |
| H A D | sdtv-standards.h | 64 /* Standards for Countries with 60Hz Line frequency */
70 /* Standards for Countries with 50Hz Line frequency */
|
| /linux/drivers/media/dvb-frontends/ |
| H A D | helene.h | 47 * helene_attach - Attach a helene tuner (terrestrial and cable standards)
60 * helene_attach_s - Attach a helene tuner (satellite standards)
|
| /linux/Documentation/process/ |
| H A D | code-of-conduct.rst | 16 Our Standards
44 Maintainers are responsible for clarifying the standards of acceptable behavior
|
| /linux/include/media/ |
| H A D | tveeprom.h | 42 * @tuner_formats: Supported analog TV standards (V4L2_STD_*).
47 * @tuner2_formats: Tuner 2 supported analog TV standards
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 13 Documentation and Standards
231 port. Such configurations might support a range of PoE standards and require
284 4. **Support for PoE Standards**
286 - *Description:* Lists the PoE standards and configurations supported by the
289 to industry standards.
292 do not necessarily imply support for multiple PoE standards.
|
| /linux/Documentation/admin-guide/media/ |
| H A D | vivid.rst | 359 both support all TV standards. If the standard is queried, then the Vivid
365 TV standards. This is particularly noticeable when generating a horizontally
367 visible. For 50 Hz standards the top field is the oldest and the bottom field
368 is the newest in time. For 60 Hz standards that is reversed: the bottom field
372 contain the top field for 50 Hz standards and the bottom field for 60 Hz
373 standards. This is what capture hardware does as well.
375 Finally, for PAL/SECAM standards the first half of the top line contains noise.
458 The S-Video output supports all TV standards.
494 cases the driver will generate valid VBI data: for 60 Hz standards it will
497 The XDS stream will give the current time once a minute. For 50 Hz standards
[all …]
|