Searched +full:protocol +full:- +full:id (Results 1 – 25 of 245) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/firmware/ |
| D | arm,scmi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/firmware/arm,scmi.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: System Control and Management Interface (SCMI) Message Protocol
11 - Sudeep Holla <sudeep.holla@arm.com>
26 - $ref: /schemas/firmware/nxp,imx95-scmi.yaml
34 - description: SCMI compliant firmware with mailbox transport
36 - const: arm,scmi
37 - description: SCMI compliant firmware with ARM SMC/HVC transport
[all …]
|
| D | nxp,imx95-scmi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/firmware/nxp,imx95-scmi.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Peng Fan <peng.fan@nxp.com>
14 protocol@81:
15 $ref: '/schemas/firmware/arm,scmi.yaml#/$defs/protocol-node'
22 protocol@84:
23 $ref: '/schemas/firmware/arm,scmi.yaml#/$defs/protocol-node'
30 nxp,ctrl-ids:
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | ti,sci-clk.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/ti,sci-clk.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI clock controller
10 - Nishanth Menon <nm@ti.com>
17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This clock controller node uses the TI SCI protocol to perform various clock
21 node must be a child node of the associated TI-SCI system controller node.
25 pattern: "^clock-controller$"
[all …]
|
| /Documentation/devicetree/bindings/reset/ |
| D | ti,sci-reset.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reset/ti,sci-reset.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI reset controller
10 - Nishanth Menon <nm@ti.com>
17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This reset controller node uses the TI SCI protocol to perform the reset
21 node of the associated TI-SCI system controller node.
25 pattern: "^reset-controller$"
[all …]
|
| /Documentation/networking/ |
| D | phonet.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Linux Phonet protocol family
9 ------------
11 Phonet is a packet protocol used by Nokia cellular modems for both IPC
19 - USB with the CDC Phonet interface,
20 - infrared,
21 - Bluetooth,
22 - an RS232 serial port (with a dedicated "FBUS" line discipline),
23 - the SSI bus with some TI OMAP processors.
27 --------------
[all …]
|
| D | vxlan.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 The VXLAN protocol is a tunnelling protocol designed to solve the
12 number of vendors. The protocol runs over UDP using a single
20 use of statically-configured forwarding entries.
29 # ip link add vxlan0 type vxlan id 42 group 239.1.1.1 dev eth1 dstport 4789
34 the IANA-assigned value of 4789. The Linux implementation of VXLAN
35 pre-dates the IANA's selection of a standard destination port number
36 and uses the Linux-selected value by default to maintain backwards
45 # ip -d link show vxlan0
62 The following NIC features may indicate support for UDP tunnel-related
[all …]
|
| D | bridge.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 The IEEE 802.1Q-2022 (Bridges and Bridged Networks) standard defines the
23 .. kernel-doc:: net/bridge/br_private.h
33 -------------------------
35 .. kernel-doc:: include/uapi/linux/if_link.h
39 ------------------------------
41 .. kernel-doc:: include/uapi/linux/if_link.h
45 ------------
53 The STP (Spanning Tree Protocol) implementation in the Linux bridge driver
58 STP is a Layer 2 protocol that operates at the Data Link Layer of the OSI
[all …]
|
| D | iso15765-2.rst | 1 .. SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause)
4 ISO 15765-2 (ISO-TP)
10 ISO 15765-2, also known as ISO-TP, is a transport protocol specifically defined
12 industry, for example as the transport protocol for UDSonCAN (ISO 14229-3) or
13 emission-related diagnostic services (ISO 15031-5).
15 ISO-TP can be used both on CAN CC (aka Classical CAN) and CAN FD (CAN with
21 -------------------
23 * ISO 15765-2:2024 : Road vehicles - Diagnostic communication over Controller
24 Area Network (DoCAN). Part 2: Transport protocol and network layer services.
27 ----------
[all …]
|
| D | ppp_generic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 The generic PPP driver in linux-2.4 provides an implementation of the
43 ---------------
54 flow-control reasons. In this case, start_xmit() should return 0
60 * ioctl() provides an interface which can be used by a user-space
62 procedure will be called when a user-space program does an ioctl
90 (e.g. an ioctl) to transmit this back to user-space, as user-space
94 interface to which this channel is connected, or -1 if the channel
99 expected to have some way for a user-level process to control it
104 Generally a user-level process will initialize the underlying
[all …]
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| ST-Ericsson AB 2010
17 CAIF is a MUX protocol used by ST-Ericsson cellular modems for
22 ST-Ericsson modems support a number of transports between modem
32 * CAIF Core Protocol Implementation
39 ! +------+ +------+
40 ! +------+! +------+!
42 +-------> !interf!+ ! API !+ <- CAIF Client APIs
43 ! +------+ +------!
45 ! +-----------+
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | sci-pm-domain.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/ti/sci-pm-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI generic power domain
10 - Nishanth Menon <nm@ti.com>
13 - $ref: /schemas/power/power-domain.yaml#
20 through a protocol called TI System Control Interface (TI-SCI protocol).
22 This PM domain node represents the global PM domain managed by the TI-SCI
23 controller. Since this relies on the TI SCI protocol to communicate with
[all …]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/arm,mhuv2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tushar Khandelwal <tushar.khandelwal@arm.com>
11 - Viresh Kumar <viresh.kumar@linaro.org>
15 between 1 and 124 channel windows (each 32-bit wide) to provide unidirectional
33 - Data-transfer: Each transfer is made of one or more words, using one or more
36 - Doorbell: Each transfer is made up of single bit flag, using any one of the
38 and the entire window shall be used in doorbell protocol. Optionally, data
[all …]
|
| D | qcom-ipcc.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mailbox/qcom-ipcc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Technologies, Inc. Inter-Processor Communication Controller
10 - Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
13 The Inter-Processor Communication Controller (IPCC) is a centralized hardware
14 to route interrupts across various subsystems. It involves a three-level
15 addressing scheme called protocol, client and signal. For example, consider an
18 a case, the client would be Modem (client-id is 2) and the signal would be
[all …]
|
| /Documentation/admin-guide/ |
| D | pnp.rst | 10 --------
18 ------------------
26 - id - displays a list of support EISA IDs
27 - options - displays possible resource configurations
28 - resources - displays currently allocated resources and allows resource changes
46 <depnum> - the configuration number
47 <mode> - static or dynamic
75 - Notice the string "DISABLED". This means the device is not active.
80 Dependent: 01 - Priority acceptable
81 port 0x3f0-0x3f0, align 0x7, size 0x6, 16-bit address decoding
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid-multitouch | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
5 quirks actually in place to handle the device's protocol.
7 MT_QUIRKS_* in hid-multitouch.c).
9 the protocol to handle the device.
|
| D | configfs-usb-gadget-midi2 | 1 What: /config/usb-gadget/gadget/functions/midi2.name
13 What: /config/usb-gadget/gadget/functions/midi2.name/ep.number
23 protocol_caps MIDI protocol capabilities (1, 2 or 3 for both)
24 protocol Default MIDI protocol (1 or 2)
26 product_id Product ID string
27 manufacturer Manufacture ID (24 bit)
28 family Device family ID (16 bit)
29 model Device model ID (16 bit)
33 What: /config/usb-gadget/gadget/functions/midi2.name/ep.number/block.number
45 first_group The first UMP Group number (0-15)
[all …]
|
| /Documentation/driver-api/i3c/ |
| D | protocol.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 I3C protocol
14 This document is just a brief introduction to the I3C protocol and the concepts
17 https://resources.mipi.org/mipi-i3c-v1-download).
22 The I3C (pronounced 'eye-three-see') is a MIPI standardized protocol designed
25 while remaining power-efficient.
42 I3C is a multi-master protocol, so there might be several masters on a bus,
51 In addition to these per-device addresses, the protocol defines a broadcast
61 The I3C protocol defines a mechanism to automatically discover devices present
70 * BCR: Bus Characteristic Register. This 8-bit register describes the device bus
[all …]
|
| /Documentation/arch/x86/ |
| D | boot.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 The Linux/x86 Boot Protocol
12 real-mode DOS as a mainstream operating system.
14 Currently, the following versions of the Linux/x86 boot protocol exist.
20 Protocol 2.00 (Kernel 1.3.73) Added bzImage and initrd support, as
26 Protocol 2.01 (Kernel 1.3.76) Added a heap overrun warning.
28 Protocol 2.02 (Kernel 2.4.0-test3-pre3) New command line protocol.
31 safe for systems which use the EBDA from SMM or 32-bit
35 Protocol 2.03 (Kernel 2.4.18-pre1) Explicitly makes the highest possible
38 Protocol 2.04 (Kernel 2.6.14) Extend the syssize field to four bytes.
[all …]
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,k3-sci-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/keystone/ti,k3-sci-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Common K3 TI-SCI
10 - Nishanth Menon <nm@ti.com>
14 that is responsible for managing various SoC-level resources like clocks,
16 through the TI-SCI protocol.
19 controller node or an interrupt-controller node should define a common set
21 over the TI-SCI protocol. The following are some of the common properties
[all …]
|
| /Documentation/input/ |
| D | multi-touch-protocol.rst | 4 Multi-touch (MT) Protocol
7 :Copyright: |copy| 2009-2010 Henrik Rydberg <rydberg@euromail.se>
11 ------------
13 In order to utilize the full power of the new multi-touch and multi-user
16 document describes the multi-touch (MT) protocol which allows kernel
19 The protocol is divided into two types, depending on the capabilities of the
20 hardware. For devices handling anonymous contacts (type A), the protocol
22 devices capable of tracking identifiable contacts (type B), the protocol
26 MT protocol type A is obsolete, all kernel drivers have been
29 Protocol Usage
[all …]
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | switch-driver.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 [dpaa2-eth] [dpaa2-eth] [ dpaa2-switch ]
30 | ---------- | [DPMAC] [DPMAC]
31 ------------------------------- | |
38 The dpaa2-switch driver probes on DPSW devices found on the fsl-mc bus. These
40 file - DataPath Layout (DPL) - or at runtime using the DPAA2 object APIs
43 At the moment, the dpaa2-switch driver imposes the following restrictions on
70 Besides the configuration of the actual DPSW object, the dpaa2-switch driver
73 * 1 DPMCP - A Management Command Portal object is needed for any interraction
76 * 1 DPBP - A Buffer Pool is used for seeding buffers intended for the Rx path
[all …]
|
| /Documentation/admin-guide/blockdev/ |
| D | paride.rst | 5 PARIDE v1.03 (c) 1997-8 Grant Guenther <grant@torque.net>
12 to personal computers, many external devices such as portable hard-disk,
13 CD-ROM, LS-120 and tape drives use the parallel port to connect to their
14 host computer. While some devices (notably scanners) use ad-hoc methods
17 a parallel-port adapter chip added in. Some of the original parallel port
19 (The Iomega PPA-3 adapter used in the ZIP drives is an example of this
22 and the communication protocol provides operations for reading and writing
27 which is then connected to a floppy-tape mechanism. The vast majority
30 were to open up a parallel port CD-ROM drive, for instance, one would
31 find a standard ATAPI CD-ROM drive, a power supply, and a single adapter
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra30-mc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra30-mc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dmitry Osipenko <digetx@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
12 - Thierry Reding <thierry.reding@gmail.com>
22 Protocol Arbiter, which manage a related pool of memory devices. A system
23 may have a single Protocol Arbiter or multiple Protocol Arbiters.
26 Domains and Protocol Arbiters. In the simplest version of the system, the
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | fsl,scu-pd.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/fsl,scu-pd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: i.MX SCU Client Device Node - Power Domain Based on SCU Message Protocol
10 - Dong Aisheng <aisheng.dong@nxp.com>
13 Client nodes are maintained as children of the relevant IMX-SCU device node.
14 Power domain bindings based on SCU Message Protocol
17 - $ref: power-domain.yaml#
22 - enum:
[all …]
|
| /Documentation/networking/dsa/ |
| D | dsa.rst | 22 An Ethernet switch typically comprises multiple front-panel ports and one
27 gateways, or even top-of-rack switches. This host Ethernet controller will
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
46 - what port is this frame coming from
47 - what was the reason why this frame got forwarded
48 - how to send CPU originated traffic to specific ports
52 on Port-based VLAN IDs).
57 - the "cpu" port is the Ethernet switch facing side of the management
61 - the "dsa" port(s) are just conduits between two or more switches, and as such
[all …]
|
12345678910