Searched full:standard (Results 1 – 25 of 762) sorted by relevance
12345678910>>...31
| /Documentation/devicetree/bindings/pinctrl/ |
| D | brcm,bcm11351-pinctrl.txt | 49 Standard, I2C, and HDMI. Each type accepts a different set of pin config
57 Optional Properties (for standard pins):
68 0: Standard(100kbps)& Fast(400kbps) mode
94 0: Standard(100kbps)& Fast(400kbps) mode
112 0: Standard(100kbps)& Fast(400kbps) mode
127 //group node defining 1 standard pin
194 "adcsync", Standard
195 "bat_rm", Standard
200 "classgpwr", Standard
201 "clk_cx8", Standard
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | standard.rst | 24 V4L2 defines one bit for each analog video standard currently in use
28 standard, although presenting the user a menu of supported standards is
36 standards also contain sets of one or more standard bits.
39 signals. The first enumerated standard is a set of B and G/PAL, switched
45 To query and select the standard used by the current video input or
48 *received* standard can be sensed with the
54 :ref:`v4l2_std_id <v4l2-std-id>` type (a standard set), *not* an
55 index into the standard enumeration. Drivers must implement all video
56 standard ioctls when the device has one or more video inputs or outputs.
63 video standard, or
[all …]
|
| D | vidioc-querystd.rst | 19 VIDIOC_QUERYSTD - VIDIOC_SUBDEV_QUERYSTD - Sense the video standard received by the current input
45 The hardware may be able to detect the current video standard
57 Drivers shall *not* switch the video standard
58 automatically if a new video standard is detected. Instead, drivers
61 :ref:`VIDIOC_QUERYSTD`. The reason is that a new video standard can mean
65 standard is valid they will have to stop streaming, set the new
66 standard, allocate new buffers and start streaming again.
77 Standard video timings are not supported for this input or output.
|
| D | pixfmt-intro.rst | 11 Standard Image Formats
15 necessary to have standard image data formats which both sides will
17 section is intended to be an unambiguous specification of the standard
22 to convert images to one of the standard formats when needed. But the
29 Even so, ultimately, some standard formats are needed, so the V4L2
30 specification would not be complete without well-defined standard
33 The V4L2 standard formats are mainly uncompressed formats. The pixels
|
| D | vidioc-g-std.rst | 19 …- VIDIOC_SUBDEV_G_STD - VIDIOC_SUBDEV_S_STD - Query or select the video standard of the current in…
51 To query and select the current video standard applications use the
60 does not return the actual new standard as :ref:`VIDIOC_G_STD <VIDIOC_G_STD>` does. When
62 standard the driver returns an ``EINVAL`` error code. When the standard set
64 standards. If the current input or output does not support standard
81 Standard video timings are not supported for this input or output.
|
| D | vidioc-g-dv-timings.rst | 150 - The video standard(s) this format belongs to. This will be filled
163 - The Video Identification Code according to the CEA-861 standard.
167 - The Video Identification Code according to the HDMI standard.
227 * - Timing standard
230 - The timings follow the CEA-861 Digital TV Profile standard
232 - The timings follow the VESA Discrete Monitor Timings standard
234 - The timings follow the VESA Coordinated Video Timings standard
236 - The timings follow the VESA Generalized Timings Formula standard
238 - The timings follow the SDI Timings standard.
304 Identification Code as per the CEA-861 standard.
[all …]
|
| D | dev-rds.rst | 21 For more information see the core RDS standard :ref:`iec62106` and the
22 RBDS standard :ref:`nrsc4`.
26 Note that the RBDS standard as is used in the USA is almost
27 identical to the RDS standard. Any RDS decoder/encoder can also handle
29 RBDS standard for more information.
31 The RBDS standard also specifies support for MMBS (Modified Mobile
|
| D | vidioc-enumstd.rst | 45 To query the attributes of a video standard, especially a custom (driver
67 - Number of the video standard, set by the application.
70 - The bits in this field identify the standard as one of the common
79 - Name of the standard, a NUL-terminated ASCII string, for example:
124 - This type is a set, each bit representing another video standard
147 ``V4L2_STD_PAL_60`` is a hybrid standard with 525 lines, 60 Hz refresh
159 ``V4L2_STD_NTSC_443`` is a hybrid standard with 525 lines, 60 Hz refresh
326 Standard video timings are not supported for this input or output.
330 find the current standard returned by :ref:`VIDIOC_G_STD <VIDIOC_G_STD>`.
333 Japan uses a standard similar to M/NTSC (V4L2_STD_NTSC_M_JP).
|
| /Documentation/devicetree/bindings/perf/ |
| D | arm-ccn.txt | 5 - compatible: (standard compatible string) should be one of:
10 - reg: (standard registers property) physical address and size
13 - interrupts: (standard interrupt property) single interrupt
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-nomadik.txt | 3 Required (non-standard) properties:
6 Recommended (non-standard) properties:
9 Optional (non-standard) properties:
|
| /Documentation/hwmon/ |
| D | pmbus-core.rst | 8 [from pmbus.org] The Power Management Bus (PMBus) is an open standard
11 protocol is implemented over the industry-standard SMBus serial interface and
13 conversion products. This flexible and highly versatile standard allows for
17 semiconductor companies, this open power system standard is maintained and
22 commands, and manufacturers can add as many non-standard commands as they like.
67 standard PMBus commands and virtual PMBus commands.
69 Standard PMBus commands
72 Standard PMBus commands (commands values 0x00 to 0xff) are defined in the PMBUs
78 Virtual PMBus commands are provided to enable support for non-standard
83 distinguished from standard PMBus commands (which can not have values larger
[all …]
|
| /Documentation/media/uapi/dvb/ |
| D | fe-type-t.rst | 44 - For DVB-S standard
54 - For DVB-C annex A standard
64 - For DVB-T standard
74 - For ATSC standard (terrestrial) or for DVB-C Annex B (cable) used
96 filled with the currently standard, as selected by the last call to
|
| /Documentation/devicetree/bindings/serial/ |
| D | mvebu-uart.txt | 1 * Marvell UART : Non standard UART used in some of Marvell EBU SoCs
6 - "marvell,armada-3700-uart" for the standard variant of the UART
19 - Must contain three elements for the standard variant of the IP
29 property is also supported for the standard variant of the IP,
|
| /Documentation/admin-guide/ |
| D | svga.rst | 27 (present in standard Linux utility packages). You can use the following values
30 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
32 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
54 the standard 80x25 mode.
89 the standard modes (80x25 and 80x50) followed by "special" modes (80x28 and
120 0x0100 to 0x017f - standard BIOS modes. The ID is a BIOS video mode number
128 945=132x28 for the standard Video7 BIOS)
131 by modifying one of the standard modes). Currently available:
132 0x0f00 standard 80x25, don't reset mode if already set (=FFFF)
133 0x0f01 standard with 8-point font: 80x43 on EGA, 80x50 on VGA
[all …]
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec6.txt | 28 Definition: A standard property. Define the 'ERA' of the SEC
34 Definition: A standard property. Defines the number of cells
40 Definition: A standard property. Defines the number of cells
47 Definition: A standard property. Specifies the physical
53 Definition: A standard property. Specifies the physical address
58 Note: All other standard properties (see the Devicetree Specification)
|
| /Documentation/driver-api/80211/ |
| 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".
|
| /Documentation/arm/stm32/ |
| D | stm32mp157-overview.rst | 13 - Standard memories interface support
14 - Standard connectivity, widely inherited from the STM32 MCU family
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-typec-displayport | 20 USB Type-C Standard. Functionally it equals to the situation
29 VESA DisplayPort Alt Mode on USB Type-C Standard defines six
44 Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
|
| D | sysfs-platform-at91 | 8 Default: 0x7ff (standard frame)
21 - standard id 0x7ff:
|
| D | sysfs-bus-platform | 6 will override standard OF, ACPI, ID table, and name matching.
12 (echo > driver_override). This returns the device to standard
|
| D | sysfs-bus-vmbus | 6 will override standard static and dynamic ID matching. When
12 This returns the device to standard matching rules binding.
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| 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 …]
|
| 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)
|
| /Documentation/devicetree/bindings/security/tpm/ |
| D | tpm_tis_mmio.txt | 3 The TCG defines multi vendor standard for accessing a TPM chip, this
4 is the standard protocol defined to access the TPM via MMIO. Typically
|
| /Documentation/networking/ |
| D | PLIP.txt | 21 printer port. PLIP is a non-standard, but [can use] uses the standard
48 an existing Ethernet. Isn't standard (not even de facto standard, like
113 only one implemented in the early version of the code) uses a standard
125 The cable for the first transfer mode is a standard
131 bits with standard status register implementation.
191 standard in Mode 0. That standard specifies the following protocol:
|
12345678910>>...31