Home
last modified time | relevance | path

Searched +full:industry +full:- +full:standard (Results 1 – 25 of 50) sorted by relevance

12

/kernel/linux/linux-6.6/drivers/net/arcnet/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
25 tristate "Enable standard ARCNet packet format (RFC 1201)"
29 industry-standard RFC1201 implementations, like the arcether.com
39 software complying with the "old" standard, specifically, the DOS
42 industry-standard RFC1201 implementations, like the arcether.com
71 Cap only listens to protocol 1-8.
76 This is the chipset driver for the standard COM90xx cards. If you
87 IO-mapped mode instead of memory-mapped mode. This is slower than
98 time only using memory-mapped mode, and no IO ports at all. This
103 be called arc-rimi.
/kernel/linux/linux-5.10/drivers/net/arcnet/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
25 tristate "Enable standard ARCNet packet format (RFC 1201)"
29 industry-standard RFC1201 implementations, like the arcether.com
39 software complying with the "old" standard, specifically, the DOS
42 industry-standard RFC1201 implementations, like the arcether.com
71 Cap only listens to protocol 1-8.
76 This is the chipset driver for the standard COM90xx cards. If you
87 IO-mapped mode instead of memory-mapped mode. This is slower than
98 time only using memory-mapped mode, and no IO ports at all. This
103 be called arc-rimi.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/ata/
Dcavium-compact-flash.txt5 industry standard compact flash devices.
8 - compatible: "cavium,ebt3000-compact-flash";
12 - reg: The base address of the CF chip select banks. Depending on
15 - cavium,bus-width: The width of the connection to the CF devices. Valid
18 - cavium,true-ide: Optional, if present the CF connection is in True IDE mode.
20 - cavium,dma-engine-handle: Optional, a phandle for the DMA Engine connected
24 compact-flash@5,0 {
25 compatible = "cavium,ebt3000-compact-flash";
27 cavium,bus-width = <16>;
28 cavium,true-ide;
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/ata/
Dcavium-compact-flash.txt5 industry standard compact flash devices.
8 - compatible: "cavium,ebt3000-compact-flash";
12 - reg: The base address of the CF chip select banks. Depending on
15 - cavium,bus-width: The width of the connection to the CF devices. Valid
18 - cavium,true-ide: Optional, if present the CF connection is in True IDE mode.
20 - cavium,dma-engine-handle: Optional, a phandle for the DMA Engine connected
24 compact-flash@5,0 {
25 compatible = "cavium,ebt3000-compact-flash";
27 cavium,bus-width = <16>;
28 cavium,true-ide;
[all …]
/kernel/linux/linux-5.10/drivers/eisa/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
13 The Extended Industry Standard Architecture (EISA) bus was
21 Say Y here if you are building a kernel for an EISA-based machine.
32 the Adaptec AHA-284x).
/kernel/linux/linux-6.6/drivers/eisa/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
13 The Extended Industry Standard Architecture (EISA) bus was
21 Say Y here if you are building a kernel for an EISA-based machine.
32 the Adaptec AHA-284x).
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dfsl,esai.txt3 The Enhanced Serial Audio Interface (ESAI) provides a full-duplex serial port
4 for serial communication with a variety of serial devices, including industry
5 standard codecs, Sony/Phillips Digital Interface (S/PDIF) transceivers, and
10 - compatible : Compatible list, should contain one of the following
12 "fsl,imx35-esai",
13 "fsl,vf610-esai",
14 "fsl,imx6ull-esai",
15 "fsl,imx8qm-esai",
17 - reg : Offset and length of the register set for the device.
19 - interrupts : Contains the spdif interrupt.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/
Dfsl,esai.txt3 The Enhanced Serial Audio Interface (ESAI) provides a full-duplex serial port
4 for serial communication with a variety of serial devices, including industry
5 standard codecs, Sony/Phillips Digital Interface (S/PDIF) transceivers, and
10 - compatible : Compatible list, should contain one of the following
12 "fsl,imx35-esai",
13 "fsl,vf610-esai",
14 "fsl,imx6ull-esai",
15 "fsl,imx8qm-esai",
17 - reg : Offset and length of the register set for the device.
19 - interrupts : Contains the spdif interrupt.
[all …]
/kernel/linux/linux-6.6/drivers/net/ethernet/freescale/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
35 Say Y here if you want to use the built-in 10/100 Fast ethernet
45 This option enables support for the MPC5200's on-chip
55 an external MII PHY chip or 10 Mbps 7-wire interface
56 (Motorola? industry standard).
/kernel/linux/linux-5.10/drivers/net/ethernet/freescale/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
32 Say Y here if you want to use the built-in 10/100 Fast ethernet
42 This option enables support for the MPC5200's on-chip
52 an external MII PHY chip or 10 Mbps 7-wire interface
53 (Motorola? industry standard).
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/i2c/
Dmaxim,max96712.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Quad GMSL2 to CSI-2 Deserializer with GMSL1 Compatibility
11 - Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
15 CSI-2 D-PHY or C-PHY formatted outputs. The device allows each link to
16 simultaneously transmit bidirectional control-channel data while forward
18 four remotely located sensors using industry-standard coax or STP
23 MAX96712 can be paired with first-generation 3.12Gbps or 1.5Gbps GMSL1
34 enable-gpios: true
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/
Dgenerate_udp_fragments.py2 # SPDX-License-Identifier: GPL-2.0
9 said code. `scapy` is relatively industry standard and really
33 f.write("// SPDX-License-Identifier: GPL-2.0\n")
34 f.write("/* DO NOT EDIT -- this file is generated */\n")
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/
Dlvds-codec.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/lvds-codec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
16 LVDS is a physical layer specification defined in ANSI/TIA/EIA-644-A. Multiple
21 [JEIDA] "Digital Interface Standards for Monitor", JEIDA-59-1999, February
22 1999 (Version 1.0), Japan Electronic Industry Development Association (JEIDA)
25 [VESA] "VESA Notebook Panel Standard", October 2007 (Version 1.0), Video
28 Those devices have been marketed under the FPD-Link and FlatLink brand names
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/
Dlvds.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 LVDS is a physical layer specification defined in ANSI/TIA/EIA-644-A. Multiple
19 [JEIDA] "Digital Interface Standards for Monitor", JEIDA-59-1999, February
20 1999 (Version 1.0), Japan Electronic Industry Development Association (JEIDA)
23 [VESA] "VESA Notebook Panel Standard", October 2007 (Version 1.0), Video
27 FPD-Link and FlatLink brands.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/bridge/
Dlvds-codec.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/lvds-codec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
16 LVDS is a physical layer specification defined in ANSI/TIA/EIA-644-A. Multiple
21 [JEIDA] "Digital Interface Standards for Monitor", JEIDA-59-1999, February
22 1999 (Version 1.0), Japan Electronic Industry Development Association (JEIDA)
25 [VESA] "VESA Notebook Panel Standard", October 2007 (Version 1.0), Video
28 Those devices have been marketed under the FPD-Link and FlatLink brand names
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/
Dlvds.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
11 - Thierry Reding <thierry.reding@gmail.com>
14 LVDS is a physical layer specification defined in ANSI/TIA/EIA-644-A. Multiple
19 [JEIDA] "Digital Interface Standards for Monitor", JEIDA-59-1999, February
20 1999 (Version 1.0), Japan Electronic Industry Development Association (JEIDA)
23 [VESA] "VESA Notebook Panel Standard", October 2007 (Version 1.0), Video
27 FPD-Link and FlatLink brands.
[all …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dlm75.rst10 Addresses scanned: I2C 0x48 - 0x4f
20 Addresses scanned: I2C 0x48 - 0x4f
44 http://www.maxim-ic.com/
134 https://www.nxp.com/docs/en/data-sheet/PCT2075.pdf
139 -----------
143 set and read to half-degree accuracy.
148 range of -55 to +125 degrees.
154 The original LM75 was typically used in combination with LM78-like chips
158 The LM75 is essentially an industry standard; there may be other
162 therefore be instantiated explicitly. Higher resolution up to 16-bit
Dpmbus-core.rst8 [from pmbus.org] The Power Management Bus (PMBus) is an open standard
9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
13 conversion products. This flexible and highly versatile standard allows for
17 semiconductor companies, this open power system standard is maintained and
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
[all …]
/kernel/linux/linux-5.10/Documentation/hwmon/
Dlm75.rst10 Addresses scanned: I2C 0x48 - 0x4f
20 Addresses scanned: I2C 0x48 - 0x4f
44 http://www.maxim-ic.com/
132 https://www.nxp.com/docs/en/data-sheet/PCT2075.pdf
137 -----------
141 set and read to half-degree accuracy.
146 range of -55 to +125 degrees.
152 The original LM75 was typically used in combination with LM78-like chips
156 The LM75 is essentially an industry standard; there may be other
160 therefore be instantiated explicitly. Higher resolution up to 16-bit
Dpmbus-core.rst8 [from pmbus.org] The Power Management Bus (PMBus) is an open standard
9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
13 conversion products. This flexible and highly versatile standard allows for
17 semiconductor companies, this open power system standard is maintained and
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dbiblio.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 CEA 608-E
14 :title: CEA-608-E R-2014 "Line 21 Data Services"
24 :title: EN 300 294 "625-line television Wide Screen Signalling (WSS)"
50 ISO 13818-1
54 :title: ITU-T Rec. H.222.0 | ISO/IEC 13818-1 "Information technology — Generic coding of moving…
60 ISO 13818-2
64 :title: ITU-T Rec. H.262 | ISO/IEC 13818-2 "Information technology — Generic coding of moving p…
74 :title: ITU-R Recommendation BT.470-6 "Conventional Television Systems"
84 :title: ITU-R Recommendation BT.601-5 "Studio Encoding Parameters of Digital Television for Sta…
[all …]
/kernel/linux/linux-5.10/Documentation/misc-devices/
Deeprom.rst11 Addresses scanned: I2C 0x50 - 0x57
28 24C01 1K 0x50 (shadows at 0x51 - 0x57)
29 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs)
30 24C02 2K 0x50 - 0x57
35 24C16 16K 0x50 (additional data at 0x51 - 0x57)
38 Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
39 Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
40 Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
41 Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
42 Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
[all …]
/kernel/linux/linux-6.6/Documentation/misc-devices/
Deeprom.rst11 Addresses scanned: I2C 0x50 - 0x57
28 24C01 1K 0x50 (shadows at 0x51 - 0x57)
29 24C01A 1K 0x50 - 0x57 (Typical device on DIMMs)
30 24C02 2K 0x50 - 0x57
35 24C16 16K 0x50 (additional data at 0x51 - 0x57)
38 Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
39 Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
40 Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
41 Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
42 Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
[all …]
/kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/
Dbiblio.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 CEA 608-E
14 :title: CEA-608-E R-2014 "Line 21 Data Services"
24 :title: EN 300 294 "625-line television Wide Screen Signalling (WSS)"
50 ISO 13818-1
54 :title: ITU-T Rec. H.222.0 | ISO/IEC 13818-1 "Information technology --- Generic coding of movi…
60 ISO 13818-2
64 :title: ITU-T Rec. H.262 | ISO/IEC 13818-2 "Information technology --- Generic coding of moving…
74 :title: ITU-R Recommendation BT.470-6 "Conventional Television Systems"
84 :title: ITU-R Recommendation BT.601-5 "Studio Encoding Parameters of Digital Television for Sta…
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/
Dslimbus.rst9 ----------------
11 MIPI (Mobile Industry Processor Interface) alliance. The bus uses master/slave
12 configuration, and is a 2-wire multi-drop implementation (clock, and data).
15 (System-on-Chip) and peripheral components (typically codec). SLIMbus uses
16 Time-Division-Multiplexing to accommodate multiple data channels, and
24 A data channel is used for data-transfer between 2 SLIMbus devices. Data
28 ---------------------
36 Framer device is responsible for clocking the bus, and transmitting frame-sync
49 responsible to select the active-framer for clocking the bus.
55 Each device has a 6-byte enumeration-address and the manager assigns every
[all …]

12