| /kernel/linux/linux-6.6/drivers/usb/typec/ucsi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Connector System Software Interface driver"
9 USB Type-C Connector System Software Interface (UCSI) is a
10 specification for an interface that allows the operating system to
11 control the USB Type-C ports. On UCSI system the USB Type-C ports
15 that are equipped with Embedded Controller and USB Type-C ports.
17 UCSI specification does not define the interface method, so depending
20 for every supported interface method.
23 https://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html
31 tristate "UCSI Interface Driver for Cypress CCGx"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | cci.txt | 5 ARM multi-cluster systems maintain intra-cluster coherency through a
10 clusters, through memory mapped interface, with a global control register
11 space and multiple sets of interface control registers, one per slave
12 interface.
24 - compatible
26 Value type: <string>
28 "arm,cci-400"
29 "arm,cci-500"
30 "arm,cci-550"
32 - reg
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | network.txt | 4 - fsl,cpm1-scc-enet
5 - fsl,cpm2-scc-enet
6 - fsl,cpm1-fec-enet
7 - fsl,cpm2-fcc-enet (third resource is GFEMR)
8 - fsl,qe-enet
13 compatible = "fsl,mpc8272-fcc-enet",
14 "fsl,cpm2-fcc-enet";
16 local-mac-address = [ 00 00 00 00 00 00 ];
18 interrupt-parent = <&PIC>;
19 phy-handle = <&PHY0>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | network.txt | 4 - fsl,cpm1-scc-enet
5 - fsl,cpm2-scc-enet
6 - fsl,cpm1-fec-enet
7 - fsl,cpm2-fcc-enet (third resource is GFEMR)
8 - fsl,qe-enet
13 compatible = "fsl,mpc8272-fcc-enet",
14 "fsl,cpm2-fcc-enet";
16 local-mac-address = [ 00 00 00 00 00 00 ];
18 interrupt-parent = <&PIC>;
19 phy-handle = <&PHY0>;
[all …]
|
| /kernel/linux/linux-5.10/drivers/usb/typec/ucsi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Connector System Software Interface driver"
7 USB Type-C Connector System Software Interface (UCSI) is a
8 specification for an interface that allows the operating system to
9 control the USB Type-C ports. On UCSI system the USB Type-C ports
13 that are equipped with Embedded Controller and USB Type-C ports.
15 UCSI specification does not define the interface method, so depending
18 for every supported interface method.
21 https://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html
29 tristate "UCSI Interface Driver for Cypress CCGx"
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | net_failover.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 original paravirtual interface is registered as 'standby' slave netdev and
19 'pci' device. The user accesses the network interface via 'failover' netdev.
28 virtio-net accelerated datapath: STANDBY mode
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
35 feature on the virtio-net interface and assign the same MAC address to both
36 virtio-net and VF interfaces.
41 <interface type='network'>
45 <model type='virtio'/>
48 <teaming type='persistent'/>
[all …]
|
| D | statistics.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Interface statistics
10 This document is a guide to Linux network interface statistics.
12 There are three main sources of interface statistics in Linux:
14 - standard interface statistics based on
15 :c:type:`struct rtnl_link_stats64 <rtnl_link_stats64>`;
16 - protocol-specific statistics; and
17 - driver-defined statistics available via ethtool.
19 Standard interface statistics
20 -----------------------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 .. _dsa-config-showcases:
13 -----------------------
33 interface. The CPU port is the switch port connected to an Ethernet MAC chip.
34 The corresponding linux Ethernet interface is called the master interface.
37 The slave interfaces depend on the master interface. They can only brought up,
38 when the master interface is up.
43 the master interface
46 a slave interface
49 another slave interface
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 .. _dsa-config-showcases:
13 -----------------------
33 interface. The CPU port is the switch port connected to an Ethernet MAC chip.
34 The corresponding linux Ethernet interface is called the master interface.
37 The slave interfaces depend on the master interface being up in order for them
39 interface had to be managed explicitly by the user. Starting with kernel v5.12,
42 - when a DSA slave interface is brought up, the master interface is
44 - when the master interface is brought down, all DSA slave interfaces are
50 the master interface
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/dvb/ |
| D | ca_high_level.rst | 1 .. SPDX-License-Identifier: GPL-2.0
25 Why the need for another CI interface?
29 Strictly speaking this is not a new interface.
31 The CI interface is defined in the DVB API in ca.h as:
33 .. code-block:: c
38 int type; /* CA interface this slot supports */
39 #define CA_CI 1 /* CI high level interface */
40 #define CA_CI_LINK 2 /* CI link layer level interface */
41 #define CA_CI_PHYS 4 /* CI physical layer level interface */
42 #define CA_DESCR 8 /* built-in descrambler */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | ca_high_level.rst | 1 .. SPDX-License-Identifier: GPL-2.0
25 Why the need for another CI interface?
29 Strictly speaking this is not a new interface.
31 The CI interface is defined in the DVB API in ca.h as:
33 .. code-block:: c
38 int type; /* CA interface this slot supports */
39 #define CA_CI 1 /* CI high level interface */
40 #define CA_CI_LINK 2 /* CI link layer level interface */
41 #define CA_CI_PHYS 4 /* CI physical layer level interface */
42 #define CA_DESCR 8 /* built-in descrambler */
[all …]
|
| /kernel/linux/linux-5.10/drivers/char/ipmi/ |
| D | ipmi_si_hardcode.c | 1 // SPDX-License-Identifier: GPL-2.0+
34 module_param_string(type, si_type_str, MAX_SI_TYPE_STR, 0);
35 MODULE_PARM_DESC(type, "Defines the type of each interface, each"
36 " interface separated by commas. The types are 'kcs',"
38 " the first interface to kcs and the second to bt");
40 MODULE_PARM_DESC(addrs, "Sets the memory address of each interface, the"
41 " addresses separated by commas. Only use if an interface"
45 MODULE_PARM_DESC(ports, "Sets the port address of each interface, the"
46 " addresses separated by commas. Only use if an interface"
50 MODULE_PARM_DESC(irqs, "Sets the interrupt of each interface, the"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | statistics.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Interface statistics
10 This document is a guide to Linux network interface statistics.
12 There are three main sources of interface statistics in Linux:
14 - standard interface statistics based on
15 :c:type:`struct rtnl_link_stats64 <rtnl_link_stats64>`;
16 - protocol-specific statistics; and
17 - driver-defined statistics available via ethtool.
19 Standard interface statistics
20 -----------------------------
[all …]
|
| D | net_failover.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 original paravirtual interface is registered as 'standby' slave netdev and
19 'pci' device. The user accesses the network interface via 'failover' netdev.
28 virtio-net accelerated datapath: STANDBY mode
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
35 feature on the virtio-net interface and assign the same MAC address to both
36 virtio-net and VF interfaces.
41 <interface type='network'>
45 <model type='virtio'/>
48 <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | qcom,q6afe.txt | 7 - compatible:
9 Value type: <stringlist>
10 Definition: must be "qcom,q6afe-v<MAJOR-NUMBER>.<MINOR-NUMBER>"
15 = AFE DAIs (Digial Audio Interface)
20 - compatible:
22 Value type: <stringlist>
23 Definition: must be "qcom,q6afe-dais"
25 - #sound-dai-cells
27 Value type: <u32>
30 - #address-cells
[all …]
|
| /kernel/linux/linux-6.6/drivers/greybus/ |
| D | interface.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Greybus interface code
20 /* Time required for interface to enter standby before disabling REFCLK */
23 /* Don't-care selector index */
51 return gb_svc_dme_peer_get(intf->hd->svc, intf->interface_id, in gb_interface_dme_attr_get()
64 if (intf->ddbl1_manufacturer_id != TOSHIBA_DMID) { in gb_interface_read_ara_dme()
65 dev_err(&intf->dev, "unknown manufacturer %08x\n", in gb_interface_read_ara_dme()
66 intf->ddbl1_manufacturer_id); in gb_interface_read_ara_dme()
67 return -ENODEV; in gb_interface_read_ara_dme()
71 &intf->vendor_id); in gb_interface_read_ara_dme()
[all …]
|
| /kernel/linux/linux-5.10/drivers/greybus/ |
| D | interface.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Greybus interface code
20 /* Time required for interface to enter standby before disabling REFCLK */
23 /* Don't-care selector index */
51 return gb_svc_dme_peer_get(intf->hd->svc, intf->interface_id, in gb_interface_dme_attr_get()
64 if (intf->ddbl1_manufacturer_id != TOSHIBA_DMID) { in gb_interface_read_ara_dme()
65 dev_err(&intf->dev, "unknown manufacturer %08x\n", in gb_interface_read_ara_dme()
66 intf->ddbl1_manufacturer_id); in gb_interface_read_ara_dme()
67 return -ENODEV; in gb_interface_read_ara_dme()
71 &intf->vendor_id); in gb_interface_read_ara_dme()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/ |
| D | arm,cci-400.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/arm/arm,cci-400.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
13 ARM multi-cluster systems maintain intra-cluster coherency through a cache
18 clusters, through memory mapped interface, with a global control register
19 space and multiple sets of interface control registers, one per slave
20 interface.
24 pattern: "^cci(@[0-9a-f]+)?$"
[all …]
|
| /kernel/linux/linux-6.6/include/uapi/linux/dvb/ |
| D | ca.h | 1 /* SPDX-License-Identifier: LGPL-2.1+ WITH Linux-syscall-note */
14 * struct ca_slot_info - CA slot interface types and info.
17 * @type: slot type.
22 * @type can be:
24 * - %CA_CI - CI high level interface;
25 * - %CA_CI_LINK - CI link layer level interface;
26 * - %CA_CI_PHYS - CI physical layer level interface;
27 * - %CA_DESCR - built-in descrambler;
28 * - %CA_SC -simple smart card interface.
32 * - %CA_CI_MODULE_PRESENT - module (or card) inserted;
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 3 Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
4 Description: Read-only. Attribute group to describe the magic bits
6 (See ABI/testing/sysfs-bus-event_source-devices-format).
12 counter_info_version = "config:16-23"
13 length = "config:24-31"
14 partition_id = "config:32-63"
15 request = "config:0-31"
16 sibling_part_id = "config:32-63"
17 hw_chip_id = "config:32-63"
18 offset = "config:32-63"
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | ipmi.rst | 7 The Intelligent Platform Management Interface, or IPMI, is a
12 standardized database for field-replaceable units (FRUs) and a watchdog
15 To use this, you need an interface to an IPMI controller in your
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
37 from userland, you need to select 'Device interface for IPMI' if you
40 The driver interface depends on your hardware. If your system
42 and just work. If you have a board with a standard interface (These
50 these enabled and let the drivers auto-detect what is present.
[all …]
|
| /kernel/linux/linux-6.6/drivers/char/ipmi/ |
| D | ipmi_si_hardcode.c | 1 // SPDX-License-Identifier: GPL-2.0+
34 module_param_string(type, si_type_str, MAX_SI_TYPE_STR, 0);
35 MODULE_PARM_DESC(type,
36 …type of each interface, each interface separated by commas. The types are 'kcs', 'smic', and 'bt'…
39 …"Sets the memory address of each interface, the addresses separated by commas. Only use if an int…
42 …"Sets the port address of each interface, the addresses separated by commas. Only use if an inter…
45 …"Sets the interrupt of each interface, the addresses separated by commas. Only use if an interfac…
48 …ytes between the start address and each successive register used by the interface. For instance, …
51 …s should generally be 1, 2, 4, or 8 for an 8-bit, 16-bit, 32-bit, or 64-bit register. Use this if…
54 …r, in bits. For instance, if the data is read from a 32-bit word and the IPMI data is in bit 8-15…
[all …]
|
| /kernel/linux/linux-5.10/net/batman-adv/ |
| D | tvlv.c | 1 // SPDX-License-Identifier: GPL-2.0
2 /* Copyright (C) 2007-2020 B.A.T.M.A.N. contributors:
34 * batadv_tvlv_handler_release() - release tvlv handler from lists and queue for
47 * batadv_tvlv_handler_put() - decrement the tvlv container refcounter and
56 kref_put(&tvlv_handler->refcount, batadv_tvlv_handler_release); in batadv_tvlv_handler_put()
60 * batadv_tvlv_handler_get() - retrieve tvlv handler from the tvlv handler list
61 * based on the provided type and version (both need to match)
62 * @bat_priv: the bat priv with all the soft interface information
63 * @type: tvlv handler type to look for
69 batadv_tvlv_handler_get(struct batadv_priv *bat_priv, u8 type, u8 version) in batadv_tvlv_handler_get() argument
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | ipmi.rst | 7 The Intelligent Platform Management Interface, or IPMI, is a
12 standardized database for field-replaceable units (FRUs) and a watchdog
15 To use this, you need an interface to an IPMI controller in your
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
37 from userland, you need to select 'Device interface for IPMI' if you
40 The driver interface depends on your hardware. If your system
42 and just work. If you have a board with a standard interface (These
50 these enabled and let the drivers auto-detect what is present.
[all …]
|
| /kernel/linux/linux-6.6/drivers/usb/serial/ |
| D | usb-serial.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2009 - 2013 Johan Hovold (jhovold@gmail.com)
6 * Copyright (C) 1999 - 2012 Greg Kroah-Hartman (greg@kroah.com)
13 * See Documentation/usb/usb-serial.rst for more information on using this
39 #define DRIVER_AUTHOR "Greg Kroah-Hartman <gregkh@linuxfoundation.org>"
71 serial = port->serial; in usb_serial_port_get_by_minor()
72 mutex_lock(&serial->disc_mutex); in usb_serial_port_get_by_minor()
73 if (serial->disconnected) { in usb_serial_port_get_by_minor()
74 mutex_unlock(&serial->disc_mutex); in usb_serial_port_get_by_minor()
77 kref_get(&serial->kref); in usb_serial_port_get_by_minor()
[all …]
|