/linux/Documentation/devicetree/bindings/firmware/ |
H A 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> 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 39 - const: arm,scmi-smc [all …]
|
H A 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 …]
|
H A D | arm,scpi.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 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/drivers/firmware/arm_scmi/ |
H A 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 …]
|
/linux/Documentation/devicetree/bindings/soc/samsung/ |
H A 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 …]
|
/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/Documentation/devicetree/bindings/reset/ |
H A 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 …]
|
/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 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 …]
|
/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. 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 …]
|
/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/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 …]
|
/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 */ 338 u16 offset; /* 10 bit protocol offset */ [all …]
|
/linux/net/netfilter/ipvs/ |
H A D | Kconfig | 1 # 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/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/drivers/net/wireguard/ |
H A D | allowedips.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. 23 static void copy_and_assign_cidr(struct allowedips_node *node, const u8 *src, in copy_and_assign_cidr() argument 26 node->cidr = cidr; in copy_and_assign_cidr() 27 node->bit_at_a = cidr / 8U; in copy_and_assign_cidr() 29 node->bit_at_a ^= (bits / 8U - 1U) % 8U; in copy_and_assign_cidr() 31 node->bit_at_b = 7U - (cidr % 8U); in copy_and_assign_cidr() 32 node->bitlen = bits; in copy_and_assign_cidr() 33 memcpy(node->bits, src, bits / 8U); in copy_and_assign_cidr() 36 static inline u8 choose(struct allowedips_node *node, const u8 *key) in choose() argument [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/net/sunrpc/ |
H A D | svc.c | 1 // 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/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/drivers/net/hamradio/ |
H A D | Kconfig | 1 # 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 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/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/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 …]
|