| /linux/Documentation/devicetree/bindings/clock/ |
| H A 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 …]
|
| /linux/arch/arm/boot/dts/st/ |
| H A D | stm32mp15-scmi.dtsi | 1 // 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 D | sys-t.rst | 1 .. 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/include/linux/ |
| H A D | pnp.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2008 Hewlett-Packard Development Company, L.P.
15 #include <linux/device-id/pnp.h>
46 if (res && !(res->flags & IORESOURCE_DISABLED)) in pnp_resource_enabled()
53 if (res->start == 0 && res->end == 0) in pnp_resource_len()
65 return res->start; in pnp_port_start()
75 return res->end; in pnp_port_end()
85 return res->flags; in pnp_port_flags()
111 return res->start; in pnp_mem_start()
121 return res->end; in pnp_mem_end()
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | batadv_packet.h | 1 /* SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) */
16 * batadv_tp_is_error() - Check throughput meter return code for error
24 * enum batadv_packettype - types for batman-adv encapsulated packets
41 /* 0x00 - 0x3f: local packets or special rules for handling */
48 /* 0x40 - 0x7f: unicast */
56 /* 0x80 - 0xff: reserved */
60 * enum batadv_subtype - packet subtype for unicast4addr
77 * enum batadv_iv_flags - flags used in B.A.T.M.A.N. IV OGM packets
91 * enum batadv_icmp_packettype - ICMP message types
109 * enum batadv_mcast_flags - flags for multicast capabilities and settings
[all …]
|
| /linux/Documentation/devicetree/bindings/arm/keystone/ |
| H A 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.
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/Documentation/ABI/testing/ |
| H A D | configfs-stp-policy-p_sys-t | 1 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 D | sysfs-driver-typec-displayport | 20 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/net/netfilter/ipvs/ |
| H A D | ip_vs_conn.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
6 * high-performance and highly available server based on a
14 * with changes/fixes from Julian Anastasov, Lars Marowsky-Bree, Horms
64 * - hash (add conn) and unhash (del conn) are safe for RCU readers walking
67 * - rehash (fill cport) hashes the conn to new bucket or even new table,
71 * - hash table resize works like rehash but always rehashes into new table
72 * - bit lock on bucket serializes all operations that modify the chain
73 * - on resize, bucket from the old table is locked before bucket from the
75 * - cp->lock protects conn fields like cp->flags, cp->dest
79 * conn_tab_lock - Lock conn_tab buckets for conn hash/unhash, not for rehash
[all …]
|
| /linux/Documentation/devicetree/bindings/soc/ti/ |
| H A 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 …]
|
| /linux/drivers/net/ethernet/intel/ice/ |
| H A D | ice_parser.h | 1 /* 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/hsr/ |
| H A D | Kconfig | 1 # 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 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>
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 D | Kconfig | 1 # 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/net/sunrpc/ |
| H A D | svc.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * High-level RPC service routines
49 unsigned int *pool_to; /* maps pool id to node */
50 unsigned int *to_pool; /* maps node to pool id */
60 * only so that writing a previously-valid value still succeeds.
75 * sunrpc_get_pool_mode - get the current pool_mode for the host
112 m->to_pool = kcalloc(maxpools, sizeof(unsigned int), GFP_KERNEL); in svc_pool_map_alloc_arrays()
113 if (!m->to_pool) in svc_pool_map_alloc_arrays()
115 m->pool_to = kcalloc(maxpools, sizeof(unsigned int), GFP_KERNEL); in svc_pool_map_alloc_arrays()
116 if (!m->pool_to) in svc_pool_map_alloc_arrays()
[all …]
|
| /linux/arch/arm64/boot/dts/arm/ |
| H A D | juno-scmi.dtsi | 3 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/drivers/clk/imx/ |
| H A D | clk-scu.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright 2018-2021 NXP
7 #include <dt-bindings/firmware/imx/rsrc.h>
8 #include <linux/arm-smccc.h>
10 #include <linux/clk-provider.h>
20 #include "clk-scu.h"
38 struct list_head node; member
44 * struct clk_scu - Description of one SCU clock
62 * struct clk_gpr_scu - Description of one SCU GPR clock
78 * struct imx_sc_msg_req_set_clock_rate - clock set rate protocol
[all …]
|
| /linux/Documentation/devicetree/bindings/net/pse-pd/ |
| H A D | realtek,pse-mcu-gen1.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/pse-pd/realtek,pse-mcu-gen1.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jonas Jelonek <jelonek.jonas@gmail.com>
15 this MCU - over I2C/SMBus or UART - using a small message-based protocol;
17 directly. For example, on the Zyxel GS1900-10HP the SoC reaches the MCU
18 over UART, and the MCU manages the on-board PSE chip.
21 firmware and its host protocol, which are stable across boards. The
22 microcontroller silicon is a general-purpose part that varies, and the
[all …]
|
| /linux/Documentation/devicetree/bindings/openrisc/opencores/ |
| H A D | or1ksim.txt | 6 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/i2c/ |
| H A D | summary.rst | 6 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/virt/hyperv/ |
| H A D | vpci.rst | 1 .. 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/Documentation/networking/ |
| H A 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 …]
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-intro.rst | 1 .. 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 D | client-identifier.rst | 1 .. 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 …]
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | driver.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * System Control and Management Interface (SCMI) Message Protocol driver
5 * SCMI Message Protocol is used between the System Control Processor(SCP)
7 * provides a mechanism for inter-processor communication between SCP's
14 * Copyright (C) 2018-2025 ARM Ltd.
26 #include <linux/io-64-nonatomic-hi-lo.h>
50 #define SCMI_VENDOR_MODULE_ALIAS_FMT "scmi-protocol-0x%02x-%s"
66 * struct scmi_xfers_info - Structure to manage transfer information
74 * a number of xfers equal to the maximum allowed in-flight
77 * currently in-flight messages.
[all …]
|