| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | standard.rst | 18 V4L2 defines one bit for each analog video standard currently in use 22 standard, although presenting the user a menu of supported standards is 30 standards also contain sets of one or more standard bits. 33 signals. The first enumerated standard is a set of B and G/PAL, switched 39 To query and select the standard used by the current video input or 42 *received* standard can be sensed with the 48 :ref:`v4l2_std_id <v4l2-std-id>` type (a standard set), *not* an 49 index into the standard enumeration. Drivers must implement all video 50 standard ioctls when the device has one or more video inputs or outputs. 57 video standard, or [all …]
|
| H A D | vidioc-querystd.rst | 13 VIDIOC_QUERYSTD - VIDIOC_SUBDEV_QUERYSTD - Sense the video standard received by the current input 38 The hardware may be able to detect the current video standard 50 Drivers shall *not* switch the video standard 51 automatically if a new video standard is detected. Instead, drivers 54 :ref:`VIDIOC_QUERYSTD`. The reason is that a new video standard can mean 58 standard is valid they will have to stop streaming, set the new 59 standard, allocate new buffers and start streaming again.
|
| H A D | vidioc-g-std.rst | 13 …- VIDIOC_SUBDEV_G_STD - VIDIOC_SUBDEV_S_STD - Query or select the video standard of the current in… 46 To query and select the current video standard applications use the 55 does not return the actual new standard as :ref:`VIDIOC_G_STD <VIDIOC_G_STD>` does. When 57 standard the driver returns an ``EINVAL`` error code. When the standard set 59 standards. If the current input or output does not support standard
|
| H A D | pixfmt-intro.rst | 9 necessary to have standard image data formats which both sides will 11 section is intended to be an unambiguous specification of the standard 16 to convert images to one of the standard formats when needed. But the 23 Even so, ultimately, some standard formats are needed, so the V4L2 24 specification would not be complete without well-defined standard 27 The V4L2 standard formats are mainly uncompressed formats. The pixels
|
| H A D | colorspaces-details.rst | 14 The :ref:`smpte170m` standard defines the colorspace used by NTSC and 80 the :ref:`itu601` standard and this colorspace is sometimes called 92 The :ref:`itu709` standard defines the colorspace used by HDTV in 120 The full name of this standard is Rec. ITU-R BT.709-5. 195 The non-standard xvYCC 709 or xvYCC 601 encodings can be 209 The :ref:`srgb` standard defines the colorspace used by most webcams 214 Note that the :ref:`sycc` standard specifies full range quantization, 287 The :ref:`oprgb` standard defines the colorspace used by computer 293 Note that the :ref:`oprgb` standard specifies full range quantization, 356 The :ref:`itu2020` standard defines the colorspace used by Ultra-high [all …]
|
| H A D | vidioc-g-dv-timings.rst | 152 - The video standard(s) this format belongs to. This will be filled 165 - The Video Identification Code according to the CEA-861 standard. 169 - The Video Identification Code according to the HDMI standard. 228 * - Timing standard 231 - The timings follow the CEA-861 Digital TV Profile standard 233 - The timings follow the VESA Discrete Monitor Timings standard 235 - The timings follow the VESA Coordinated Video Timings standard 237 - The timings follow the VESA Generalized Timings Formula standard 239 - The timings follow the SDI Timings standard. 307 Identification Code as per the CEA-861 standard. [all …]
|
| H A D | vidioc-enumstd.rst | 38 To query the attributes of a video standard, especially a custom (driver 59 - Number of the video standard, set by the application. 62 - The bits in this field identify the standard as one of the common 71 - Name of the standard, a NUL-terminated ASCII string, for example: 114 - This type is a set, each bit representing another video standard 136 ``V4L2_STD_PAL_60`` is a hybrid standard with 525 lines, 60 Hz refresh 147 ``V4L2_STD_NTSC_443`` is a hybrid standard with 525 lines, 60 Hz refresh 314 find the current standard returned by :ref:`VIDIOC_G_STD <VIDIOC_G_STD>`. 317 Japan uses a standard similar to M/NTSC (V4L2_STD_NTSC_M_JP).
|
| H A D | dev-rds.rst | 15 For more information see the core RDS standard :ref:`iec62106` and the 16 RBDS standard :ref:`nrsc4`. 20 Note that the RBDS standard as is used in the USA is almost 21 identical to the RDS standard. Any RDS decoder/encoder can also handle 23 RBDS standard for more information. 25 The RBDS standard also specifies support for MMBS (Modified Mobile
|
| H A D | metafmt-uvc.rst | 16 This format describes standard UVC metadata, extracted from UVC packet headers 18 exact copies of the standard part of UVC Payload Header contents and auxiliary 52 - Flags, indicating presence of other standard UVC fields
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-type-t.rst | 37 - For DVB-S standard 47 - For DVB-C annex A standard 57 - For DVB-T standard 67 - For ATSC standard (terrestrial) or for DVB-C Annex B (cable) used 89 filled with the currently standard, as selected by the last call to
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-version.txt | 15 on the standard output. 18 compiled-in libraries are printed on the standard output. 24 standard output.
|
| H A D | perf-help.txt | 17 on the standard output. 20 printed on the standard output. 33 Prints all the available commands on the standard output. This
|
| /linux/arch/arm/boot/dts/xilinx/ |
| H A D | zynq-ebaz4205.dts | 70 io-standard = <3>; 88 io-standard = <3>; 100 io-standard = <3>; 115 io-standard = <3>;
|
| /linux/Documentation/arch/riscv/ |
| H A D | uabi.rst | 20 #. Additional standard extensions (starting with 'Z') will be sorted after 23 #. For additional standard extensions, the first letter following the 'Z' 30 after standard unprivileged extensions. If multiple supervisor-level 34 after any lower-privileged, standard extensions. If multiple machine-level 37 #. Non-standard extensions (starting with 'X') will be listed after all standard 38 extensions. If multiple non-standard extensions are listed, they will be
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | dcsr.txt | 30 Definition: A standard property. Defines the number of cells 36 Definition: A standard property. Defines the number of cells 43 Definition: A standard property. Specifies the physical address 90 Definition: A standard property. Specifies the physical address 119 Definition: A standard property. Specifies the physical address 156 Definition: A standard property. Specifies the physical address 181 Definition: A standard property. Specifies the physical address 218 Definition: A standard property. Specifies the physical address 246 Definition: A standard property. Specifies the physical address 277 Definition: A standard property. Specifies the physical address [all …]
|
| H A D | srio.txt | 18 Definition: A standard property. Specifies the physical address and 46 Definition: A standard property. Matches the port id. 51 Definition: A standard property. Utilized to describe the memory mapped 75 Note: All other standard properties (see the Devicetree Specification)
|
| /linux/drivers/bcma/ |
| H A D | README | 5 AMBA standard fields like CID and PID. 9 as standard AMBA device. Reading it's CID or PID can cause machine lockup. 10 2) AMBA standard devices called ports or wrappers. They have CIDs (AMBA_CID)
|
| /linux/drivers/media/dvb-frontends/drx39xyj/ |
| H A D | drxj.h | 173 enum drx_standard standard; /* standard for which these settings apply */ member 189 enum drx_standard standard; /* standard to which these settings apply */ member 199 enum drx_standard standard; /* standard to which these settings apply */ member 425 enum drx_standard standard; /*< current standard information */ member
|
| /linux/Documentation/networking/ |
| H A D | plip.rst | 25 printer port. PLIP is a non-standard, but [can use] uses the standard 52 an existing Ethernet. Isn't standard (not even de facto standard, like 117 only one implemented in the early version of the code) uses a standard 129 The cable for the first transfer mode is a standard 135 bits with standard status register implementation. 197 standard in Mode 0. That standard specifies the following protocol::
|
| /linux/Documentation/admin-guide/ |
| H A D | svga.rst | 28 (present in standard Linux utility packages). You can use the following values 55 the standard 80x25 mode. 90 the standard modes (80x25 and 80x50) followed by "special" modes (80x28 and 121 0x0100 to 0x017f - standard BIOS modes. The ID is a BIOS video mode number 129 945=132x28 for the standard Video7 BIOS) 132 by modifying one of the standard modes). Currently available: 133 0x0f00 standard 80x25, don't reset mode if already set (=FFFF) 134 0x0f01 standard with 8-point font: 80x43 on EGA, 80x50 on VGA 136 0x0f03 VGA 80x28 (standard VGA scans, but 14-point font) 146 This is the only fully portable way to refer to a non-standard mode, [all …]
|
| /linux/Documentation/driver-api/80211/ |
| H A D | introduction.rst | 15 The reader is expected to be familiar with the 802.11 standard as 17 References to this standard will be given as "802.11-2007 8.1.5".
|
| /linux/drivers/media/common/saa7146/ |
| H A D | saa7146_video.c | 335 v4l2_video_std_frame_period(vv->standard->id, in vidioc_g_parm() 374 maxw = vv->standard->h_max_out; in vidioc_try_fmt_vid_cap() 375 maxh = vv->standard->v_max_out; in vidioc_try_fmt_vid_cap() 453 *norm = vv->standard->id; in vidioc_g_std() 471 vv->standard == &dev->ext_vv_data->stds[i]) in vidioc_s_std() 480 vv->standard = &dev->ext_vv_data->stds[i]; in vidioc_s_std() 482 dev->ext_vv_data->std_callback(dev, vv->standard); in vidioc_s_std() 491 DEB_EE("VIDIOC_S_STD: set to standard to '%s'\n", vv->standard->name); in vidioc_s_std() 697 vv->standard = &dev->ext_vv_data->stds[0]; in video_init()
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | introduction.rst | 17 PSE in the IEEE 802.3 standard generally refers to equipment that provides 29 Key addenda to the IEEE 802.3-2018 standard relevant to power delivery over 58 Clause 33 of the IEEE 802.3 standard defines the functional and electrical 67 Clause 104 of the IEEE 802.3 standard delineates the functional and electrical
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | uniwill-laptop.rst | 47 the standard ``charge_control_end_threshold`` power supply sysfs attribute. All values 50 Additionally the driver signals the presence of battery charging issues through the standard 56 The ``uniwill-laptop`` driver exposes the lightbar found on some models as a standard multicolor
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-at91 | 8 Default: 0x7ff (standard frame) 21 - standard id 0x7ff::
|