| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | standard.rst | 10 Video devices typically support one or more different video standards or 11 variations of standards. Each video input and output may support another 12 set of standards. This set is reported by the ``std`` field of struct 19 worldwide, and sets aside bits for driver defined standards, e. g. 20 hybrid standards to watch NTSC video tapes on PAL TVs and vice versa. 22 standard, although presenting the user a menu of supported standards is 24 standards applications use the :ref:`VIDIOC_ENUMSTD` 27 Many of the defined standards are actually just variations of a few 28 major standards. The hardware may in fact not distinguish between them, 30 standards also contain sets of one or more standard bits. [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 | 10 The video standards discussed so far have been dealing with Analog TV 24 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 | vidioc-log-status.rst | 35 channels. Also many modern devices autodetect video and audio standards
|
| /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
|
| H A D | intro.rst | 21 Various Digital TV standards documents are available for download at: 23 - European standards (DVB): http://www.dvb.org and/or http://www.etsi.org. 24 - American standards (ATSC): https://www.atsc.org/standards/ 25 - Japanese standards (ISDB): http://www.dibeg.org/ 44 based on open standards, Nokia and Convergence made it available to all
|
| H A D | frontend_legacy_dvbv3_api.rst | 10 TV standards, doesn't provide good statistics measurements and provides
|
| /linux/drivers/media/v4l2-core/ |
| H A D | v4l2-dv-timings.c | 161 cap->standards && bt->standards && in v4l2_valid_dv_timings() 162 !(bt->standards & cap->standards)) || in v4l2_valid_dv_timings() 361 pr_info("%s: standards (0x%x):%s%s%s%s%s\n", dev_prefix, bt->standards, in v4l2_print_dv_timings() 362 (bt->standards & V4L2_DV_BT_STD_CEA861) ? " CEA" : "", in v4l2_print_dv_timings() 363 (bt->standards & V4L2_DV_BT_STD_DMT) ? " DMT" : "", in v4l2_print_dv_timings() 364 (bt->standards & V4L2_DV_BT_STD_CVT) ? " CVT" : "", in v4l2_print_dv_timings() 365 (bt->standards & V4L2_DV_BT_STD_GTF) ? " GTF" : "", in v4l2_print_dv_timings() 366 (bt->standards & V4L2_DV_BT_STD_SDI) ? " SDI" : ""); in v4l2_print_dv_timings() 656 t.bt.standards = V4L2_DV_BT_STD_CVT; in v4l2_detect_cvt() 820 t.bt.standards = V4L2_DV_BT_STD_GTF; in v4l2_detect_gtf()
|
| /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/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/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/include/media/ |
| H A D | v4l2-dv-timings.h | 223 if ((bt->standards & V4L2_DV_BT_STD_CVT) && (bt->vsync == 8)) in can_reduce_fps() 226 if ((bt->standards & V4L2_DV_BT_STD_CEA861) && in can_reduce_fps()
|
| /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/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/staging/media/meson/vdec/ |
| H A D | TODO | 6 with compression standards like MPEG1/2 where the driver does not support
|
| /linux/drivers/media/pci/netup_unidvb/ |
| H A D | Kconfig | 16 Card can receive two independent streams in following standards:
|
| /linux/Documentation/translations/zh_TW/admin-guide/ |
| H A D | unicode.rst | 107 https://www.evertype.com/standards/csur/klingon.html 168 https://www.evertype.com/standards/csur/
|
| /linux/Documentation/translations/zh_CN/admin-guide/ |
| H A D | unicode.rst | 104 https://www.evertype.com/standards/csur/klingon.html 165 https://www.evertype.com/standards/csur/
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 231 port. Such configurations might support a range of PoE standards and require 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.
|