Home
last modified time | relevance | path

Searched +full:protocol +full:- +full:node (Results 1 – 25 of 561) sorted by relevance

12345678910>>...23

/linux/Documentation/devicetree/bindings/clock/
H A Dti,sci-clk.yaml1 # 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 …]
/linux/Documentation/devicetree/bindings/reset/
H A Dti,sci-reset.yaml1 # 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 …]
/linux/arch/arm/boot/dts/st/
H A Dstm32mp15-scmi.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
3 * Copyright (C) STMicroelectronics 2022 - All Rights Reserved
7 #include <dt-bindings/regulator/st,stm32mp15-regulator.h>
12 compatible = "linaro,optee-tz";
14 interrupt-parent = <&intc>;
19 compatible = "linaro,scmi-optee";
20 #address-cells = <1>;
21 #size-cells = <0>;
22 linaro,optee-channel-id = <0>;
24 scmi_clk: protocol@14 {
[all …]
/linux/Documentation/trace/
H A Dsys-t.rst1 .. SPDX-License-Identifier: GPL-2.0
4 MIPI SyS-T over STP
7 The MIPI SyS-T protocol driver can be used with STM class devices to
11 In order to use the MIPI SyS-T protocol driver with your STM device,
14 Now, you can select which protocol driver you want to use when you create
17 # mkdir /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/
23 With Intel TH, therefore it can look like "0-sth:p_sys-t.my-policy".
25 If the protocol name is omitted, the STM class will chose whichever
26 protocol driver was loaded first.
30 # cat /config/stp-policy/dummy_stm.0:p_sys-t.my-policy/protocol
[all …]
/linux/Documentation/devicetree/bindings/arm/keystone/
H A Dti,k3-sci-common.yaml1 # 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.
18 Each specific device management node like a clock controller node, a reset
19 controller node or an interrupt-controller node should define a common set
[all …]
/linux/fs/ocfs2/dlm/
H A Ddlmdomain.c1 // SPDX-License-Identifier: GPL-2.0-or-later
34 * ocfs2 node maps are array of long int, which limits to send them freely
65 while (pages--) in dlm_free_pagevec()
95 * struct dlm_ctxt->spinlock
96 * struct dlm_lock_resource->spinlock
97 * struct dlm_ctxt->master_lock
98 * struct dlm_ctxt->ast_lock
99 * dlm_master_list_entry->spinlock
100 * dlm_lock->spinlock
109 * The supported protocol version for DLM communication. Running domains
[all …]
/linux/Documentation/ABI/testing/
H A Dconfigfs-stp-policy-p_sys-t1 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/uuid
6 Default value is randomly generated at the mkdir <node> time.
7 Data coming from trace sources that use this <node> will be
8 tagged with this UUID in the MIPI SyS-T packet stream, to
13 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/do_len
17 Include payload length in the MIPI SyS-T header, boolean.
18 If enabled, the SyS-T protocol encoder will include payload
20 if the underlying transport protocol supports marking message
23 What: /config/stp-policy/<device>:p_sys-t.<policy>/<node>/ts_interval
28 MIPI SyS-T packet metadata, if this many milliseconds have
[all …]
H A Dsysfs-driver-typec-displayport20 USB Type-C Standard. Functionally it equals to the situation
22 Documentation/ABI/testing/sysfs-bus-typec, and use file
29 VESA DisplayPort Alt Mode on USB Type-C Standard defines six
30 different pin assignments for USB Type-C connector that are
44 Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
47 USB SuperSpeed protocol. From user perspective pin assignments C
49 for carrying DisplayPort protocol (allowing higher resolutions).
55 VESA DisplayPort Alt Mode on USB Type-C Standard defines how
56 HotPlugDetect(HPD) shall be supported on the USB-C connector when
57 operating in DisplayPort Alt Mode. This is a read only node which
[all …]
/linux/drivers/net/ethernet/intel/ice/
H A Dice_parser.h1 /* SPDX-License-Identifier: GPL-2.0 */
37 u8 prio; /* 0-3: PG precedence within ALUs (3 highest) */
41 /* Next protocol Key builder */
159 u16 pg_rn; /* Parse Graph Root Node */
201 u16 node_id; /* Node ID of protocol in parse graph */
208 u32 next_proto; /* next Protocol value (must be last) */
226 u16 next_node; /* Parser Node ID for the next round */
228 bool is_pg; /* is protocol group */
229 u8 proto_id; /* protocol ID or proto group ID */
337 u16 offset; /* 10 bit protocol offset */
[all …]
/linux/net/netfilter/ipvs/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 IP Virtual Server support will let you build a high-performance
75 IP VS was compiled built-in.
77 comment "IPVS transport protocol load balancing support"
83 protocol. Say Y if unsure.
89 protocol. Say Y if unsure.
98 Security Payload) transport protocol. Say Y if unsure.
104 Header) transport protocol. Say Y if unsure.
111 protocol. Say Y if unsure.
116 tristate "round-robin scheduling"
[all …]
/linux/Documentation/devicetree/bindings/soc/ti/
H A Dsci-pm-domain.yaml1 # 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 …]
/linux/net/sunrpc/
H A Dsvc.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * High-level RPC service routines
47 SVC_POOL_AUTO = -1, /* choose one of the others */
51 SVC_POOL_PERNODE /* one pool per numa node */
65 unsigned int *pool_to; /* maps pool id to cpu or node */
66 unsigned int *to_pool; /* maps cpu or node to pool id */
92 err = -EINVAL; in __param_set_pool_mode()
97 if (m->count == 0) in __param_set_pool_mode()
98 m->mode = mode; in __param_set_pool_mode()
99 else if (mode != m->mode) in __param_set_pool_mode()
[all …]
/linux/net/hsr/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # IEC 62439-3 High-availability Seamless Redundancy
7 tristate "High-availability Seamless Redundancy (HSR & PRP)"
9 This enables IEC 62439 defined High-availability Seamless
10 Redundancy (HSR) and Parallel Redundancy Protocol (PRP).
13 DANH ("Doubly attached node implementing HSR") or DANP ("Doubly
14 attached node implementing PRP"). For this to work, your Linux box
17 For DANH, it must be connected as a node in a ring network together
20 ports), giving a redundant, instant fail-over network. Each HSR node
24 For DANP, it must be connected as a node connecting to two
[all …]
/linux/Documentation/devicetree/bindings/power/
H A Dfsl,scu-pd.yaml1 # 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>
12 description: i.MX SCU Client Device Node
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#
[all …]
/linux/drivers/ufs/core/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0+
5 # Copyright (C) 2011-2013 Samsung India Software Operations
12 bool "Universal Flash Storage BSG device node"
19 UFS Protocol Information Units (UPIUs).
20 UPIUs can not only be used as a transport layer for the SCSI protocol
22 This transport driver supports exchanging UFS protocol information units
26 Select this if you need a bsg device node for your UFS controller.
/linux/drivers/net/hamradio/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
7 KISS is a protocol used for the exchange of data between a computer
8 and a Terminal Node Controller (a small embedded system commonly
13 Although KISS is less advanced than the 6pack protocol, it has
24 6pack is a transmission protocol for the data exchange between your
25 PC and your TNC (the Terminal Node Controller acts as a kind of
27 microphone input and speaker output). This protocol can be used as
42 AX.25 is the protocol used for computer communication over amateur
56 and the AX25-HOWTO, available from
91 ser12 design in full-duplex mode. In addition, it allows the
[all …]
/linux/arch/arm64/boot/dts/arm/
H A Djuno-scmi.dtsi3 power-domains = <&scmi_devpd 8>;
7 power-domains = <&scmi_devpd 8>;
11 power-domains = <&scmi_devpd 8>;
15 power-domains = <&scmi_devpd 8>;
19 power-domains = <&scmi_devpd 8>;
23 power-domains = <&scmi_devpd 8>;
27 power-domains = <&scmi_devpd 8>;
31 power-domains = <&scmi_devpd 8>;
42 /delete-node/ scpi;
47 mbox-names = "tx", "rx";
[all …]
/linux/Documentation/devicetree/bindings/firmware/
H A Darm,scpi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: System Control and Power Interface (SCPI) Message Protocol
11 - Sudeep Holla <sudeep.holla@arm.com>
33 - const: arm,scpi # SCPI v1.0 and above
34 - const: arm,scpi-pre-1.0 # Unversioned SCPI before v1.0
35 - items:
36 - enum:
37 - amlogic,meson-gxbb-scpi
[all …]
/linux/Documentation/networking/
H A Diso15765-2.rst1 .. 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 …]
/linux/Documentation/virt/hyperv/
H A Dvpci.rst1 .. SPDX-License-Identifier: GPL-2.0
3 PCI pass-thru devices
5 In a Hyper-V guest VM, PCI pass-thru devices (also called
16 Hyper-V terminology for vPCI devices is "Discrete Device
17 Assignment" (DDA). Public documentation for Hyper-V DDA is
20 …tps://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-deploying-devi…
23 and for GPUs. A similar mechanism for NICs is called SR-IOV
25 driver to interact directly with the hardware. See Hyper-V
26 public documentation here: `SR-IOV`_
28 .. _SR-IOV: https://learn.microsoft.com/en-us/windows-hardware/drivers/network/overview-of-single-r…
[all …]
/linux/net/802/
H A Dgarp.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * IEEE 802.1D Generic Attribute Registration Protocol (GARP)
24 MODULE_DESCRIPTION("IEEE 802.1D Generic Attribute Registration Protocol (GARP)");
141 if (attr->type != type) in garp_attr_cmp()
142 return attr->type - type; in garp_attr_cmp()
143 if (attr->dlen != len) in garp_attr_cmp()
144 return attr->dlen - len; in garp_attr_cmp()
145 return memcmp(attr->data, data, len); in garp_attr_cmp()
151 struct rb_node *parent = app->gid.rb_node; in garp_attr_lookup()
156 attr = rb_entry(parent, struct garp_attr, node); in garp_attr_lookup()
[all …]
/linux/Documentation/i2c/
H A Dsummary.rst6 a protocol developed by Philips. It is a two-wire protocol with variable
14 The latest official I2C specification is the `"I²C-bus specification and user
15 manual" (UM10204) <https://www.nxp.com/docs/en/user-guide/UM10204.pdf>`_
18 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
28 implement all the common SMBus protocol semantics or messages.
36 .. kernel-figure:: i2c_bus.svg
41 A **controller** chip is a node that starts communications with targets. In the
50 A **target** chip is a node that responds to communications when addressed by a
59 video-related chips.
66 --------
[all …]
/linux/Documentation/devicetree/bindings/openrisc/opencores/
H A Dor1ksim.txt6 specification, however some aspects, such as the boot protocol have been defined
10 -------------------
11 - compatible: Must include "opencores,or1ksim"
14 ----------
15 A "cpus" node is required. Required properties:
16 - #address-cells: Must be 1.
17 - #size-cells: Must be 0.
18 A CPU sub-node is also required for at least CPU 0. Since the topology may
21 - compatible: Must be "opencores,or1200-rtlsvn481".
22 - reg: CPU number.
[all …]
/linux/Documentation/userspace-api/media/cec/
H A Dcec-intro.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _cec-intro:
9 Control protocol. This protocol allows different devices connected by an
10 HDMI cable to communicate. The protocol for CEC version 1.4 is defined
17 and is based on the ancient AV.link protocol used in old SCART
18 connectors. The protocol closely resembles a crazy Rube Goldberg
20 messages, especially those part of the HEAC protocol layered on top of
28 Drivers that support CEC will create a CEC device node (/dev/cecX) to
33 the `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_ package. It
36 - cec-ctl: the Swiss army knife of CEC. Allows you to configure, transmit
[all …]
/linux/Documentation/filesystems/nfs/
H A Dclient-identifier.rst1 .. SPDX-License-Identifier: GPL-2.0
7 This document explains how the NFSv4 protocol identifies client
19 ------------
21 The NFSv4 protocol uses "lease-based file locking". Leases help
34 the NFSv4 protocol allows the server to remove the client's open
48 ------------------------
54 - co_ownerid: An arbitrary but fixed string.
56 - boot verifier: A 64-bit incarnation verifier that enables a
72 - The "co_ownerid" string identifies the client during reboot
75 - The "co_ownerid" string helps servers distinguish the client
[all …]

12345678910>>...23