| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/firmware/ |
| D | arm,scmi.yaml | 1 # 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 Management Interface (SCMI) Message Protocol
11 - Sudeep Holla <sudeep.holla@arm.com>
31 - description: SCMI compliant firmware with mailbox transport
33 - const: arm,scmi
34 - description: SCMI compliant firmware with ARM SMC/HVC transport
36 - const: arm,scmi-smc
37 - description: SCMI compliant firmware with ARM SMC/HVC transport
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | arm,scmi.txt | 1 System Control and Management Interface (SCMI) Message Protocol
2 ----------------------------------------------------------
15 The scmi node with the following properties shall be under the /firmware/ node.
17 - compatible : shall be "arm,scmi" or "arm,scmi-smc" for smc/hvc transports
18 - mboxes: List of phandle and mailbox channel specifiers. It should contain
22 - shmem : List of phandle pointing to the shared memory(SHM) area as per
24 - #address-cells : should be '1' if the device has sub-nodes, maps to
25 protocol identifier for a given sub-node.
26 - #size-cells : should be '0' as 'reg' property doesn't have any size
28 - arm,smc-id : SMC id required when using smc or hvc transports
[all …]
|
| D | arm,scpi.txt | 1 System Control and Power Interface (SCPI) Message Protocol
2 ----------------------------------------------------------
10 - compatible : should be
12 * "arm,scpi-pre-1.0" : For implementations complying to all
14 - mboxes: List of phandle and mailbox channel specifiers
16 SCPI message protocol should be specified in any order
17 - shmem : List of phandle pointing to the shared memory(SHM) area between the
26 Clock bindings for the clocks based on SCPI Message Protocol
27 ------------------------------------------------------------
31 Container Node
[all …]
|
| /kernel/linux/linux-6.6/drivers/firmware/arm_scmi/ |
| D | bus.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * System Control and Management Interface (SCMI) Message Protocol bus layer
5 * Copyright (C) 2018-2021 ARM Ltd.
31 struct list_head node; member
38 * scmi_protocol_device_request - Helper to request a device
40 * @id_table: A protocol/name pair descriptor for the device to be created.
45 * The requested device name MUST NOT be already existent for any protocol;
59 pr_debug("Requesting SCMI device (%s) for protocol %x\n", in scmi_protocol_device_request()
60 id_table->name, id_table->protocol_id); in scmi_protocol_device_request()
65 id_table->name, id_table->protocol_id); in scmi_protocol_device_request()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/samsung/ |
| D | exynos-usi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/samsung/exynos-usi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sam Protsenko <semen.protsenko@linaro.org>
11 - Krzysztof Kozlowski <krzk@kernel.org>
14 USI IP-core provides selectable serial protocol (UART, SPI or High-Speed I2C).
15 USI shares almost all internal circuits within each protocol, so only one
16 protocol can be chosen at a time. USI is modeled as a node with zero or more
17 child nodes, each representing a serial sub-node device. The mode setting
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/reset/ |
| D | ti,sci-reset.txt | 1 Texas Instruments System Control Interface (TI-SCI) Reset Controller
8 through a protocol called TI System Control Interface (TI-SCI protocol).
12 TI-SCI Reset Controller Node
14 This reset controller node uses the TI SCI protocol to perform the reset
16 node of the associated TI-SCI system controller node.
19 --------------------
20 - compatible : Should be "ti,sci-reset"
21 - #reset-cells : Should be 2. Please see the reset consumer node below for
24 TI-SCI Reset Consumer Nodes
30 --------------------
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | st,stm32-sai.txt | 4 as I2S standards, LSB or MSB-justified, PCM/DSP, TDM, and AC'97.
5 The SAI contains two independent audio sub-blocks. Each sub-block has
9 - compatible: Should be "st,stm32f4-sai" or "st,stm32h7-sai"
10 - reg: Base address and size of SAI common register set.
11 - clocks: Must contain phandle and clock specifier pairs for each entry
12 in clock-names.
13 - clock-names: Must contain "pclk" "x8k" and "x11k"
15 Mandatory for "st,stm32h7-sai" compatible.
16 Not used for "st,stm32f4-sai" compatible.
19 - interrupts: cpu DAI interrupt line shared by SAI sub-blocks
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/st/ |
| D | stm32mp15-scmi.dtsi | 1 // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
3 * Copyright (C) STMicroelectronics 2022 - All Rights Reserved
10 compatible = "linaro,optee-tz";
15 compatible = "linaro,scmi-optee";
16 #address-cells = <1>;
17 #size-cells = <0>;
18 linaro,optee-channel-id = <0>;
20 scmi_clk: protocol@14 {
22 #clock-cells = <1>;
25 scmi_reset: protocol@16 {
[all …]
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| 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 …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | pnp.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2008 Hewlett-Packard Development Company, L.P.
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()
130 return res->flags; in pnp_mem_flags()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pnp.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Copyright (C) 2008 Hewlett-Packard Development Company, L.P.
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()
130 return res->flags; in pnp_mem_flags()
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | batadv_packet.h | 1 /* SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) */
2 /* Copyright (C) 2007-2020 B.A.T.M.A.N. contributors:
15 * batadv_tp_is_error() - Check throughput meter return code for error
23 * enum batadv_packettype - types for batman-adv encapsulated packets
39 /* 0x00 - 0x3f: local packets or special rules for handling */
45 /* 0x40 - 0x7f: unicast */
53 /* 0x80 - 0xff: reserved */
57 * enum batadv_subtype - packet subtype for unicast4addr
74 * enum batadv_iv_flags - flags used in B.A.T.M.A.N. IV OGM packets
88 * enum batadv_icmp_packettype - ICMP message types
[all …]
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | batadv_packet.h | 1 /* SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) */
15 * batadv_tp_is_error() - Check throughput meter return code for error
23 * enum batadv_packettype - types for batman-adv encapsulated packets
40 /* 0x00 - 0x3f: local packets or special rules for handling */
47 /* 0x40 - 0x7f: unicast */
55 /* 0x80 - 0xff: reserved */
59 * enum batadv_subtype - packet subtype for unicast4addr
76 * enum batadv_iv_flags - flags used in B.A.T.M.A.N. IV OGM packets
90 * enum batadv_icmp_packettype - ICMP message types
108 * enum batadv_mcast_flags - flags for multicast capabilities and settings
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | tipc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 TIPC (Transparent Inter Process Communication) is a protocol that is specially
11 designed for intra-cluster communication. It can be configured to transmit
14 than with any other known protocol, while maximal throughput is comparable to
18 -------------
20 - Cluster wide IPC service
32 - Service Addressing
38 - Service Tracking
45 i.e., subscribing for availability/non-availability of cluster nodes.
51 - Transmission Modes
[all …]
|
| /kernel/linux/linux-5.10/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 bindings
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 …]
|
| /kernel/linux/linux-6.6/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.
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 …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,scu.txt | 2 --------------------------------------------------------------------
4 The System Controller Firmware (SCFW) is a low-level system function
5 which runs on a dedicated Cortex-M core to provide power, clock, and
9 The AP communicates with the SC using a multi-ported MU module found
16 System Controller Device Node:
19 The scu node with the following properties shall be under the /firmware/ node.
22 -------------------
23 - compatible: should be "fsl,imx-scu".
24 - mbox-names: should include "tx0", "tx1", "tx2", "tx3",
27 - mboxes: List of phandle of 4 MU channels for tx, 4 MU channels for
[all …]
|
| /kernel/linux/linux-5.10/net/netfilter/ipvs/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 IP Virtual Server support will let you build a high-performance
74 if IP VS was compiled built-in.
76 comment "IPVS transport protocol load balancing support"
82 protocol. Say Y if unsure.
88 protocol. Say Y if unsure.
97 Security Payload) transport protocol. Say Y if unsure.
103 Header) transport protocol. Say Y if unsure.
110 protocol. Say Y if unsure.
115 tristate "round-robin scheduling"
[all …]
|
| /kernel/linux/linux-6.6/net/hsr/ |
| 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 …]
|
| /kernel/linux/linux-5.10/net/hsr/ |
| 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 …]
|