Home
last modified time | relevance | path

Searched +full:interface +full:- +full:type (Results 1 – 25 of 1058) sorted by relevance

12345678910>>...43

/linux-6.14.4/drivers/usb/typec/ucsi/
DKconfig1 # 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 …]
/linux-6.14.4/Documentation/networking/
Dnet_failover.rst1 .. 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 …]
Dstatistics.rst1 .. 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 …]
/linux-6.14.4/Documentation/networking/dsa/
Dconfiguration.rst1 .. 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 conduit interface.
37 The user interfaces depend on the conduit 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 user interface is brought up, the conduit interface is
44 - when the conduit interface is brought down, all DSA user interfaces are
50 the conduit interface
[all …]
Db53.rst1 .. SPDX-License-Identifier: GPL-2.0
20 The switch is, if possible, configured to enable a Broadcom specific 4-bytes
22 CPU interface, conversely, the CPU network interface should insert a similar
29 The interface names and example network configuration are used according the
30 configuration described in the :ref:`dsa-config-showcases`.
33 ----------------------------------
38 See :ref:`dsa-tagged-configuration`.
41 -------------------------------------
48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`.
54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
[all …]
/linux-6.14.4/Documentation/userspace-api/media/dvb/
Dca_high_level.rst1 .. 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/display/panel/
Dpanel-mipi-dbi-spi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-mipi-dbi-spi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Noralf Trønnes <[email protected]>
16 The MIPI Alliance Standard for Display Bus Interface defines the electrical
19 for type 1 which has full frame memory. There are 3 interface types in the
20 standard and type C is the serial interface.
22 The standard defines the following interface signals for type C:
23 - Power:
[all …]
/linux-6.14.4/drivers/greybus/
Dinterface.c1 // 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 …]
/linux-6.14.4/Documentation/devicetree/bindings/arm/
Darm,cci-400.yaml1 # 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 <[email protected]>
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 …]
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-event_source-devices-hv_gpci3 Contact: Linux on PowerPC Developer List <linuxppc-[email protected]>
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 …]
/linux-6.14.4/Documentation/driver-api/
Dipmi.rst7 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 …]
/linux-6.14.4/include/uapi/linux/dvb/
Dca.h1 /* 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 …]
/linux-6.14.4/drivers/char/ipmi/
Dipmi_si_hardcode.c1 // 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 …]
/linux-6.14.4/Documentation/driver-api/thermal/
Dsysfs-api.rst17 This how-to focuses on enabling new thermal zone and cooling devices to
19 This solution is platform independent and any type of thermal zone devices
28 - `[0-*]` denotes any positive number starting from 0
29 - `[1-*]` denotes any positive number starting from 1
31 1. thermal sysfs driver interface functions
34 1.1 thermal zone device interface
35 ---------------------------------
40 thermal_zone_device_register_with_trips(const char *type,
48 This interface function adds a new thermal zone device (sensor) to the
49 /sys/class/thermal folder as `thermal_zone[0-*]`. It tries to bind all the
[all …]
/linux-6.14.4/net/batman-adv/
Dnetlink.c1 // SPDX-License-Identifier: GPL-2.0
41 #include "distributed-arp-table.h"
44 #include "hard-interface.h"
47 #include "network-coding.h"
49 #include "soft-interface.h"
51 #include "translation-table.h"
62 * enum batadv_genl_ops_flags - flags for genl_ops's internal_flags
66 * @BATADV_FLAG_NEED_MESH: request requires valid soft interface in
68 * saved in info->user_ptr[0]
73 * @BATADV_FLAG_NEED_HARDIF: request requires valid hard interface in
[all …]
Dtvlv.c1 // SPDX-License-Identifier: GPL-2.0
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
75 &bat_priv->tvlv.handler_list, list) { in batadv_tvlv_handler_get()
[all …]
/linux-6.14.4/drivers/net/ethernet/netronome/nfp/nfpcore/
Dnfp_cpp.h1 /* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
2 /* Copyright (C) 2015-2018 Netronome Systems, Inc. */
6 * Interface for low-level NFP CPP access.
22 dev_err(nfp_cpp_device(cpp)->parent, NFP_SUBSYS ": " fmt, ## args)
24 dev_warn(nfp_cpp_device(cpp)->parent, NFP_SUBSYS ": " fmt, ## args)
26 dev_info(nfp_cpp_device(cpp)->parent, NFP_SUBSYS ": " fmt, ## args)
28 dev_dbg(nfp_cpp_device(cpp)->parent, NFP_SUBSYS ": " fmt, ## args)
30 dev_printk(level, nfp_cpp_device(cpp)->parent, \
69 * NFP_CPP_ID() - pack target, token, and action into a CPP ID.
74 * Create a 32-bit CPP identifier representing the access to be made.
[all …]
/linux-6.14.4/drivers/usb/serial/
Dusb-serial.c1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2009 - 2013 Johan Hovold ([email protected])
6 * Copyright (C) 1999 - 2012 Greg Kroah-Hartman ([email protected])
13 * See Documentation/usb/usb-serial.rst for more information on using this
39 #define DRIVER_AUTHOR "Greg Kroah-Hartman <[email protected]>"
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 …]
/linux-6.14.4/drivers/pci/endpoint/functions/
Dpci-epf-ntb.c1 // SPDX-License-Identifier: GPL-2.0
3 * Endpoint Function Driver to implement Non-Transparent Bridge functionality
16 * +-------------+ +-------------+
20 * +------^------+ +------^------+
23 * +---------|-------------------------------------------------|---------+
24 * | +------v------+ +------v------+ |
28 * | | <-----------------------------------> | |
33 * | +-------------+ +-------------+ |
34 * +---------------------------------------------------------------------+
42 #include <linux/pci-epc.h>
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/media/
Dmicrochip,csi2dc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Eugen Hristev <[email protected]>
13 CSI2DC - Camera Serial Interface 2 Demux Controller
16 IDI interface or from a parallel bus interface.
17 It filters IDI packets based on their data type and virtual channel
19 clock domain towards a parallel interface that can be read by a sensor
21 IDI interface is Synopsys proprietary.
23 a parallel interface.
[all …]
/linux-6.14.4/Documentation/userspace-api/media/v4l/
Ddev-osd.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Video Output Overlay Interface
9 **Also known as On-Screen Display (OSD)**
13 this interface, which borrows structures and ioctls of the
14 :ref:`Video Overlay <overlay>` interface.
29 Devices supporting the *Video Output Overlay* interface set the
31 struct :c:type:`v4l2_capability` returned by the
38 Contrary to the *Video Overlay* interface the framebuffer is normally
44 ``base`` field of struct :c:type:`v4l2_framebuffer`.
47 :c:type:`fb_fix_screeninfo`. The ``FBIOGET_FSCREENINFO``
[all …]
Dvidioc-querycap.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_QUERYCAP - Query device capabilities
29 Pointer to struct :c:type:`v4l2_capability`.
37 pointer to a struct :c:type:`v4l2_capability` which is
41 .. c:type:: v4l2_capability
47 .. flat-table:: struct v4l2_capability
48 :header-rows: 0
49 :stub-columns: 0
52 * - __u8
53 - ``driver``\ [16]
[all …]
Ddev-meta.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
6 Metadata Interface
9 Metadata refers to any non-image data that supplements video frames with
12 parameters for specifying how the device processes images. This interface is
16 The metadata interface is implemented on video device nodes. The device can be
23 Device nodes supporting the metadata capture interface set the
25 :c:type:`v4l2_capability` structure returned by the :c:func:`VIDIOC_QUERYCAP`
27 device nodes supporting metadata output interface set the
29 :c:type:`v4l2_capability` structure. That flag means the device can read
43 To use the :ref:`format` ioctls applications set the ``type`` field of the
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/dma/
Darm-pl08x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/arm-pl08x.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinod Koul <[email protected]>
13 - $ref: /schemas/arm/primecell.yaml#
14 - $ref: dma-controller.yaml#
22 - arm,pl080
23 - arm,pl081
25 - compatible
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/firmware/xilinx/
Dxlnx,zynqmp-firmware.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nava kishore Manne <[email protected]>
12 description: The zynqmp-firmware node describes the interface to platform
13 firmware. ZynqMP has an interface to communicate with secure firmware.
14 Firmware driver provides an interface to firmware APIs. Interface APIs
23 - description: For implementations complying for Zynq Ultrascale+ MPSoC.
24 const: xlnx,zynqmp-firmware
[all …]

12345678910>>...43