Searched +full:port +full:- +full:specific (Results 1 – 25 of 280) sorted by relevance
12345678910>>...12
| /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 …]
|
| /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 …]
|
| /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 …]
|
| /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 …]
|
| D | mport_cdev.rst | 17 for user-space applications. Most of RapidIO operations are supported through
22 to unique port ID assigned to each local mport device.
24 Using available set of ioctl commands user-space applications can perform
27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET)
33 - Set RapidIO Component Tag for mport devices (RIO_MPORT_MAINT_COMPTAG_SET)
34 - Query logical index of mport devices (RIO_MPORT_MAINT_PORT_IDX_GET)
35 - Query capabilities and RapidIO link configuration of mport devices
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl,fman-port.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/fsl,fman-port.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale Frame Manager Port Device
10 - Frank Li <Frank.Li@nxp.com>
21 - fsl,fman-v2-port-oh
22 - fsl,fman-v2-port-rx
23 - fsl,fman-v2-port-tx
24 - fsl,fman-v3-port-oh
[all …]
|
| /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 …]
|
| /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 …]
|
| /Documentation/arch/arm/samsung/ |
| D | overview.rst | 6 ------------
15 - S3C64XX: S3C6400 and S3C6410
16 - S5PC110 / S5PV210
20 -------------
26 - S5PC110 specific default configuration
28 - S5PV210 specific default configuration
32 ------
35 several platform directories and then the machine specific directories
38 plat-samsung provides the base for all the implementations, and is the
40 specific information. It contains the base clock, GPIO and device definitions
[all …]
|
| /Documentation/networking/devlink/ |
| D | prestera.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 Driver-specific Traps
13 .. list-table:: List of Driver-specific Traps Registered by ``prestera``
16 * - Name
17 - Type
18 - Description
19 .. list-table:: List of Driver-specific Traps Registered by ``prestera``
22 * - Name
23 - Type
24 - Description
[all …]
|
| D | index.rst | 5 related to any device class, such as chip-wide/switch-ASIC-wide configuration.
8 -------
13 in devlink core, but don't allow registration of most sub-objects once
26 ----------------
28 Some objects, like linecards or port functions, could have another
32 - Lock ordering should be maintained. If driver needs to take instance
36 - Driver should use object-specific helpers to setup the
39 - ``devl_nested_devlink_set()`` - called to setup devlink -> nested
41 - ``devl_port_fn_devlink_set()`` - called to setup port function ->
43 - ``devlink_linecard_nested_dl_set()`` - called to setup linecard ->
[all …]
|
| D | netdevsim.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 .. list-table:: Generic parameters implemented
15 * - Name
16 - Mode
17 * - ``max_macs``
18 - driverinit
20 The ``netdevsim`` driver also implements the following driver-specific
23 .. list-table:: Driver-specific parameters implemented
26 * - Name
27 - Type
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-rdma_cm | 4 Description: Interface is used to configure RDMA-cable HCAs in respect to
5 RDMA-CM attributes.
9 # mount -t configfs none /config/
11 In order to set parameters related to a specific HCA, a directory
13 mkdir -p /config/rdma_cm/<hca>
16 What: /config/rdma_cm/<hca>/ports/<port-num>/default_roce_mode
19 Description: RDMA-CM based connections from HCA <hca> at port <port-num>
24 What: /config/rdma_cm/<hca>/ports/<port-num>/default_roce_tos
27 Description: RDMA-CM QPs from HCA <hca> at port <port-num>
30 The possible RoCE TOS values are 0-255.
|
| /Documentation/devicetree/bindings/ata/ |
| D | sata-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/ata/sata-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
18 The SATA controller-specific device tree bindings are responsible for
28 "#address-cells":
31 "#size-cells":
34 dma-coherent: true
37 "^sata-port@[0-9a-e]$":
[all …]
|
| D | pata-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/ata/pata-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
18 The PATA (IDE) controller-specific device tree bindings are responsible for
28 "#address-cells":
31 "#size-cells":
35 "^ide-port@[0-1]$":
38 ID number 0 and the slave drive will have ID number 1. The PATA port
[all …]
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | xlnx,video.txt | 2 -------------------------------
5 ---------------
9 and IP core specific documentation, xlnx,v-*.txt, in this directory. The DT
15 - compatible: Must be "xlnx,video".
17 - dmas, dma-names: List of one DMA specifier and identifier string (as defined
18 in Documentation/devicetree/bindings/dma/dma.txt) per port. Each port
19 requires a DMA channel with the identifier string set to "port" followed by
20 the port index.
22 - ports: Video port, using the DT bindings defined in ../video-interfaces.txt.
24 Required port properties:
[all …]
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | snps,dw-mipi-dsi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/snps,dw-mipi-dsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Philippe CORNU <philippe.cornu@foss.st.com>
15 by itself but is meant to be referenced by platform-specific device tree
23 - $ref: ../dsi-controller.yaml#
31 clock-names: true
36 reset-names:
43 port@0:
[all …]
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | dsa-port.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/dsa/dsa-port.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic DSA Switch Port
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Vladimir Oltean <olteanv@gmail.com>
15 A DSA switch port is a component of a switch that manages one MAC, and can
16 pass Ethernet frames. It can act as a stanadard Ethernet switch port, or have
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
23 - compatible
[all …]
|
| /Documentation/admin-guide/perf/ |
| D | dwc_pcie_pmu.rst | 9 Port in a Vendor-Specific Extended Capability named RAS D.E.S (Debug, Error
17 - one 64-bit counter for Time Based Analysis (RX/TX data throughput and
18 time spent in each low-power LTSSM state) and
19 - one 32-bit counter for Event Counting (error and non-error events for
25 -------------------
28 throughput and time spent in each low-power LTSSM state by the controller.
31 - Group#0: Percentage of time the controller stays in LTSSM states.
32 - Group#1: Amount of data processed (Units of 16 bytes).
35 -------------------
37 Using this feature you can obtain Error and Non-Error information in
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | trigger-source.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/leds/trigger-source.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
15 may be e.g. a USB port or an Ethernet device.
18 '#trigger-source-cells':
21 trigger sources (e.g. a specific USB port).
|
| /Documentation/devicetree/bindings/media/ |
| D | allwinner,sun8i-a83t-mipi-csi2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/allwinner,sun8i-a83t-mipi-csi2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Allwinner A83T MIPI CSI-2
10 - Paul Kocialkowski <paul.kocialkowski@bootlin.com>
14 const: allwinner,sun8i-a83t-mipi-csi2
24 - description: Bus Clock
25 - description: Module Clock
26 - description: MIPI-specific Clock
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | imx-audmux.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/imx-audmux.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Oleksij Rempel <o.rempel@pengutronix.de>
15 - items:
16 - enum:
17 - fsl,imx27-audmux
18 - const: fsl,imx21-audmux
19 - items:
[all …]
|
| /Documentation/arch/arm/nwfpe/ |
| D | nwfpe.rst | 21 contain all operating system specific code in one module (fpmodule.*).
22 All the other files contain emulator specific code. This should allow
23 others to port the emulator to NetBSD for instance relatively easily.
26 John Hauser. SoftFloat is a software implementation of floating-point
27 that conforms to the IEC/IEEE Standard for Binary Floating-point
32 double precision and extended double precision formats. The port of
34 port of SoftFloat version 1 by Neil Carson for NetBSD/arm32.
46 which instruction contains the bug. Small programs illustrating a specific
50 -------------
57 -------------------------------------------------------------------------------
[all …]
|
| /Documentation/devicetree/bindings/display/ |
| D | amlogic,meson-g12a-dw-mipi-dsi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/display/amlogic,meson-g12a-dw-mipi-dsi.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Amlogic specific extensions to the Synopsys Designware MIPI DSI Host Controller
11 - Neil Armstrong <neil.armstrong@linaro.org>
15 - A Synopsys DesignWare MIPI DSI Host Controller IP
16 - A TOP control block controlling the Clocks & Resets of the IP
19 - $ref: dsi-controller.yaml#
24 - amlogic,meson-g12a-dw-mipi-dsi
[all …]
|
12345678910>>...12