| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | typec_bus.rst | 2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
17 mode a port supports, and separate device for every alternate mode the partner
19 mode devices, and the port alternate mode devices must be handled by the port
23 alternate mode device of the port that the partner is attached to, that has
24 matching SVID and mode. Communication between the port driver and alternate mode
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/usb/ |
| D | typec_bus.rst | 2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
10 The communication is SVID (Standard or Vendor ID) specific, i.e. specific for
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
17 mode a port supports, and separate device for every alternate mode the partner
19 mode devices, and the port alternate mode devices must be handled by the port
23 alternate mode device of the port that the partner is attached to, that has
24 matching SVID and mode. Communication between the port driver and alternate mode
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | dsa.rst | 19 they configured/queried a switch port network device or a regular network
22 An Ethernet switch is typically comprised of multiple front-panel ports, and one
23 or more CPU or management port. The DSA subsystem currently relies on the
24 presence of a management port connected to an Ethernet controller capable of
27 gateways, or even top-of-the rack switches. This host Ethernet controller will
32 using upstream and downstream Ethernet links between switches. These specific
36 For each front-panel port, DSA will create specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
42 which is a hardware feature making the switch insert a specific tag for each
43 Ethernet frames it received to/from specific ports to help the management
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
32 2.1 Master Port
33 ---------------
35 A master port (or mport) is a RapidIO interface controller that is local to the
36 processor executing the Linux code. A master port generates and receives RapidIO
37 packets (transactions). In the RapidIO subsystem each master port is represented
38 by a rio_mport data structure. This structure contains master port specific
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 5 The RapidIO standard is a packet-based fabric interconnect standard designed for
8 is publicly available for download from the RTA web-site [1].
17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
32 2.1 Master Port
33 ---------------
35 A master port (or mport) is a RapidIO interface controller that is local to the
36 processor executing the Linux code. A master port generates and receives RapidIO
37 packets (transactions). In the RapidIO subsystem each master port is represented
38 by a rio_mport data structure. This structure contains master port specific
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | dsa.rst | 19 they configured/queried a switch port network device or a regular network
22 An Ethernet switch typically comprises multiple front-panel ports and one
24 presence of a management port connected to an Ethernet controller capable of
27 gateways, or even top-of-rack switches. This host Ethernet controller will
32 using upstream and downstream Ethernet links between switches. These specific
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
42 which is a hardware feature making the switch insert a specific tag for each
43 Ethernet frame it receives to/from specific ports to help the management
46 - what port is this frame coming from
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | rio_drv.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
19 extern int __rio_local_read_config_32(struct rio_mport *port, u32 offset,
21 extern int __rio_local_write_config_32(struct rio_mport *port, u32 offset,
23 extern int __rio_local_read_config_16(struct rio_mport *port, u32 offset,
25 extern int __rio_local_write_config_16(struct rio_mport *port, u32 offset,
27 extern int __rio_local_read_config_8(struct rio_mport *port, u32 offset,
29 extern int __rio_local_write_config_8(struct rio_mport *port, u32 offset,
32 extern int rio_mport_read_config_32(struct rio_mport *port, u16 destid,
34 extern int rio_mport_write_config_32(struct rio_mport *port, u16 destid,
36 extern int rio_mport_read_config_16(struct rio_mport *port, u16 destid,
[all …]
|
| D | rio.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
24 #define RIO_NO_HOPCOUNT -1
34 has multiple (or per port)
57 * 1-15 RapidIO memory regions
89 * struct rio_switch - RIO switch info
92 * @port_ok: Status of each port (one bit per port) - OK=1 or UNINIT=0
93 * @ops: pointer to switch-specific operations
95 * @nextdev: Array of per-port pointers to the next attached device
107 * struct rio_switch_ops - Per-switch operations
109 * @add_entry: Callback for switch-specific route add function
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/hisilicon/ |
| D | dw-dsi.txt | 1 Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver
7 - compatible: value should be "hisilicon,hi6220-dsi".
8 - reg: physical base address and length of dsi controller's registers.
9 - clocks: contains APB clock phandle + clock-specifier pair.
10 - clock-names: should be "pclk".
11 - ports: contains DSI controller input and output sub port.
12 The input port connects to ADE output port with the reg value "0".
13 The output port with the reg value "1", it could connect to panel or
17 A example of HiKey board hi6220 SoC and board specific DT entry:
20 SoC specific:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/hisilicon/ |
| D | dw-dsi.txt | 1 Device-Tree bindings for DesignWare DSI Host Controller v1.20a driver
7 - compatible: value should be "hisilicon,hi6220-dsi".
8 - reg: physical base address and length of dsi controller's registers.
9 - clocks: contains APB clock phandle + clock-specifier pair.
10 - clock-names: should be "pclk".
11 - ports: contains DSI controller input and output sub port.
12 The input port connects to ADE output port with the reg value "0".
13 The output port with the reg value "1", it could connect to panel or
17 A example of HiKey board hi6220 SoC and board specific DT entry:
20 SoC specific:
[all …]
|
| /kernel/linux/linux-6.6/drivers/rapidio/ |
| D | rio.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
9 * Copyright 2009 - 2013 Integrated Device Technology, Inc.
30 * struct rio_pwrite - RIO portwrite event
33 * @context: Handler specific context to pass on event
65 * rio_local_get_device_id - Get the base/extended device id for a port
66 * @port: RIO master port from which to get the deviceid
69 * implementing the master port. Returns the 8/16-bit device
72 u16 rio_local_get_device_id(struct rio_mport *port) in rio_local_get_device_id() argument
76 rio_local_read_config_32(port, RIO_DID_CSR, &result); in rio_local_get_device_id()
78 return (RIO_GET_DID(port->sys_size, result)); in rio_local_get_device_id()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | rio_drv.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
19 extern int __rio_local_read_config_32(struct rio_mport *port, u32 offset,
21 extern int __rio_local_write_config_32(struct rio_mport *port, u32 offset,
23 extern int __rio_local_read_config_16(struct rio_mport *port, u32 offset,
25 extern int __rio_local_write_config_16(struct rio_mport *port, u32 offset,
27 extern int __rio_local_read_config_8(struct rio_mport *port, u32 offset,
29 extern int __rio_local_write_config_8(struct rio_mport *port, u32 offset,
32 extern int rio_mport_read_config_32(struct rio_mport *port, u16 destid,
34 extern int rio_mport_write_config_32(struct rio_mport *port, u16 destid,
36 extern int rio_mport_read_config_16(struct rio_mport *port, u16 destid,
[all …]
|
| D | rio.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
24 #define RIO_NO_HOPCOUNT -1
34 has multiple (or per port)
57 * 1-15 RapidIO memory regions
89 * struct rio_switch - RIO switch info
92 * @port_ok: Status of each port (one bit per port) - OK=1 or UNINIT=0
93 * @ops: pointer to switch-specific operations
95 * @nextdev: Array of per-port pointers to the next attached device
107 * struct rio_switch_ops - Per-switch operations
109 * @add_entry: Callback for switch-specific route add function
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 1 Device-tree bindings for I2C OPAL driver
2 ----------------------------------------
4 Most of the device node and properties layout is specific to the firmware and
5 used by the firmware itself for configuring the port. From the linux
6 perspective, the properties of use are "ibm,port-name" and "ibm,opal-id".
10 - reg: Port-id within a given master
11 - compatible: must be "ibm,opal-i2c"
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
14 - bus-frequency: Operating frequency of the i2c bus (in HZ). Informational for
18 - ibm,port-name: Firmware provides this name that uniquely identifies the i2c
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 1 Device-tree bindings for I2C OPAL driver
2 ----------------------------------------
4 Most of the device node and properties layout is specific to the firmware and
5 used by the firmware itself for configuring the port. From the linux
6 perspective, the properties of use are "ibm,port-name" and "ibm,opal-id".
10 - reg: Port-id within a given master
11 - compatible: must be "ibm,opal-i2c"
12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
14 - bus-frequency: Operating frequency of the i2c bus (in HZ). Informational for
18 - ibm,port-name: Firmware provides this name that uniquely identifies the i2c
[all …]
|
| /kernel/linux/linux-6.6/drivers/rapidio/switches/ |
| D | idt_gen2.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
105 * Program destination port for the specified destID in idtg2_route_add_entry()
219 * This routine performs device-specific initialization only. in idtg2_em_init()
223 pr_debug("RIO: %s [%d:%d]\n", __func__, rdev->destid, rdev->hopcount); in idtg2_em_init()
225 /* Set Port-Write info CSR: PRIO=3 and CRF=1 */ in idtg2_em_init()
237 /* Use Port-Writes for LT layer error reporting. in idtg2_em_init()
238 * Enable per-port reset in idtg2_em_init()
245 * Configure PORT error reporting. in idtg2_em_init()
251 /* Configure reporting of implementation specific errors/events */ in idtg2_em_init()
255 /* Use Port-Writes for port error reporting and enable error logging */ in idtg2_em_init()
[all …]
|
| /kernel/linux/linux-5.10/drivers/rapidio/switches/ |
| D | idt_gen2.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
105 * Program destination port for the specified destID in idtg2_route_add_entry()
219 * This routine performs device-specific initialization only. in idtg2_em_init()
223 pr_debug("RIO: %s [%d:%d]\n", __func__, rdev->destid, rdev->hopcount); in idtg2_em_init()
225 /* Set Port-Write info CSR: PRIO=3 and CRF=1 */ in idtg2_em_init()
237 /* Use Port-Writes for LT layer error reporting. in idtg2_em_init()
238 * Enable per-port reset in idtg2_em_init()
245 * Configure PORT error reporting. in idtg2_em_init()
251 /* Configure reporting of implementation specific errors/events */ in idtg2_em_init()
255 /* Use Port-Writes for port error reporting and enable error logging */ in idtg2_em_init()
[all …]
|
| /kernel/linux/linux-5.10/drivers/rapidio/ |
| D | rio.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
9 * Copyright 2009 - 2013 Integrated Device Technology, Inc.
30 * struct rio_pwrite - RIO portwrite event
33 * @context: Handler specific context to pass on event
65 * rio_local_get_device_id - Get the base/extended device id for a port
66 * @port: RIO master port from which to get the deviceid
69 * implementing the master port. Returns the 8/16-bit device
72 u16 rio_local_get_device_id(struct rio_mport *port) in rio_local_get_device_id() argument
76 rio_local_read_config_32(port, RIO_DID_CSR, &result); in rio_local_get_device_id()
78 return (RIO_GET_DID(port->sys_size, result)); in rio_local_get_device_id()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | intel-pmc-mux.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Intel North Mux-Agent
10 North Mux-Agent is a function of the Intel PMC firmware that is supported on
13 platforms that allow the mux-agent to be configured from the operating system
16 The North Mux-Agent (aka. Intel PMC Mux Control, or just mux-agent) driver
18 (drivers/platform/x86/intel_scu_ipc.c). The driver registers with the USB Type-C
19 Mux Class which allows the USB Type-C Controller and Interface drivers to
24 Port nodes
28 -------
30 For every USB Type-C connector under the mux-agent control on the system, there
[all …]
|
| /kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/ |
| D | intel-pmc-mux.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Intel North Mux-Agent
10 North Mux-Agent is a function of the Intel PMC firmware that is supported on
13 platforms that allow the mux-agent to be configured from the operating system
16 The North Mux-Agent (aka. Intel PMC Mux Control, or just mux-agent) driver
18 (drivers/platform/x86/intel_scu_ipc.c). The driver registers with the USB Type-C
19 Mux Class which allows the USB Type-C Controller and Interface drivers to
24 Port nodes
28 -------
30 For every USB Type-C connector under the mux-agent control on the system, there
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 -----------------------
23 controller port is done at init time based on default output and standard
29 board specific settings (specified in board-xxx-evm.c). This allows
32 API to set timings in VENC for a specific display resolution. As of this
39 setting timings at LCD controller port when external encoders are connected
40 at the port or LCD panel timings required. When external encoder/LCD panel
41 is connected, the timings for a specific standard/preset is retrieved from
42 the board specific table and the values are used to set the timings in
43 venc using non-standard timing mode.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/usb/ |
| D | typec.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
8 /* USB Type-C Specification releases */
76 * struct enter_usb_data - Enter_USB Message details
80 * @active_link_training is a flag that should be set with uni-directional SBRX
81 * communication, and left 0 with passive cables and with bi-directional SBRX
90 * struct usb_pd_identity - USB Power Delivery identity data
94 * @vdo: Product Type Specific VDOs
98 * REVISIT: This is USB Power Delivery specific information, so this structure
112 * struct typec_altmode_desc - USB Type-C Alternate Mode Descriptor
136 *typec_port_register_altmode(struct typec_port *port,
[all …]
|
| /kernel/linux/linux-5.10/drivers/thunderbolt/ |
| D | tb.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Thunderbolt driver - bus logic (NHI independent)
12 #include <linux/nvmem-provider.h>
24 /* Intel specific NVM offsets */
30 * struct tb_nvm - Structure holding NVM information
36 * @non_active: Non-active portion NVMem device
65 * enum tb_switch_tmu_rate - TMU refresh rate
81 * struct tb_switch_tmu - Structure holding switch TMU configuration
83 * @has_ucap: Does the switch support uni-directional mode
86 * @unidirectional: Is the TMU in uni-directional or bi-directional mode
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/ti/ |
| D | cpsw_ale.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Texas Instruments N-Port Ethernet Switch Address Lookup Engine APIs
17 /* NU Switch has specific handling as number of bits in ALE entries
18 * are different than other versions of ALE. Also there are specific
19 * registers for unknown vlan specific fields. So use nu_switch_ale
61 /* port controls */
87 /* ALE unicast entry flags - passed into cpsw_ale_add_ucast() */
111 int cpsw_ale_add_ucast(struct cpsw_ale *ale, const u8 *addr, int port,
113 int cpsw_ale_del_ucast(struct cpsw_ale *ale, const u8 *addr, int port,
119 int cpsw_ale_add_vlan(struct cpsw_ale *ale, u16 vid, int port, int untag,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/bridge/ |
| D | renesas,dw-hdmi.txt | 9 following device-specific properties.
14 - compatible : Shall contain one or more of
15 - "renesas,r8a774a1-hdmi" for R8A774A1 (RZ/G2M) compatible HDMI TX
16 - "renesas,r8a774b1-hdmi" for R8A774B1 (RZ/G2N) compatible HDMI TX
17 - "renesas,r8a774e1-hdmi" for R8A774E1 (RZ/G2H) compatible HDMI TX
18 - "renesas,r8a7795-hdmi" for R8A7795 (R-Car H3) compatible HDMI TX
19 - "renesas,r8a7796-hdmi" for R8A7796 (R-Car M3-W) compatible HDMI TX
20 - "renesas,r8a77961-hdmi" for R8A77961 (R-Car M3-W+) compatible HDMI TX
21 - "renesas,r8a77965-hdmi" for R8A77965 (R-Car M3-N) compatible HDMI TX
22 - "renesas,rcar-gen3-hdmi" for the generic R-Car Gen3 and RZ/G2 compatible
[all …]
|