Home
last modified time | relevance | path

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

12345678910>>...41

/kernel/linux/linux-5.10/net/tipc/
Dsubscr.c4 * Copyright (c) 2000-2017, Ericsson AB
5 * Copyright (c) 2005-2007, 2010-2013, Wind River Systems
41 static void tipc_sub_send_event(struct tipc_subscription *sub, in tipc_sub_send_event() argument
43 u32 event, u32 port, u32 node) in tipc_sub_send_event() argument
45 struct tipc_event *evt = &sub->evt; in tipc_sub_send_event()
47 if (sub->inactive) in tipc_sub_send_event()
53 tipc_evt_write(evt, port.node, node); in tipc_sub_send_event()
54 tipc_topsrv_queue_evt(sub->net, sub->conid, event, evt); in tipc_sub_send_event()
58 * tipc_sub_check_overlap - test for subscription overlap with the
66 if (found_lower < seq->lower) in tipc_sub_check_overlap()
[all …]
Dname_table.c4 * Copyright (c) 2000-2006, 2014-2018, Ericsson AB
5 * Copyright (c) 2004-2008, 2010-2014, Wind River Systems
47 #include "node.h"
51 * struct service_range - container for all bindings of a service range
55 * @max: largest 'upper' in this node subtree
56 * @local_publ: list of identical publications made from this node
58 * @all_publ: all publications identical to this one, whatever node and scope
59 * Used by round-robin lookup algorithm
71 * struct tipc_service - container for all published instances of a service type
90 #define service_range_upper(sr) ((sr)->upper)
[all …]
/kernel/linux/linux-5.10/drivers/misc/vmw_vmci/
Dvmci_event.c1 // SPDX-License-Identifier: GPL-2.0-only
27 struct list_head node; /* on one of subscriber lists */ member
50 list_for_each_entry_safe(cur, p2, &subscriber_array[e], node) { in vmci_event_exit()
58 list_del(&cur->node); in vmci_event_exit()
73 list_for_each_entry(cur, &subscriber_array[e], node) { in event_find()
74 if (cur->id == sub_id) in event_find()
91 subscriber_list = &subscriber_array[event_msg->event_data.event]; in event_deliver()
92 list_for_each_entry_rcu(cur, subscriber_list, node) { in event_deliver()
93 cur->callback(cur->id, &event_msg->event_data, in event_deliver()
94 cur->callback_data); in event_deliver()
[all …]
/kernel/linux/linux-6.6/drivers/misc/vmw_vmci/
Dvmci_event.c1 // SPDX-License-Identifier: GPL-2.0-only
28 struct list_head node; /* on one of subscriber lists */ member
51 list_for_each_entry_safe(cur, p2, &subscriber_array[e], node) { in vmci_event_exit()
59 list_del(&cur->node); in vmci_event_exit()
74 list_for_each_entry(cur, &subscriber_array[e], node) { in event_find()
75 if (cur->id == sub_id) in event_find()
94 sanitized_event = array_index_nospec(event_msg->event_data.event, max_vmci_event); in event_deliver()
96 list_for_each_entry_rcu(cur, subscriber_list, node) { in event_deliver()
97 cur->callback(cur->id, &event_msg->event_data, in event_deliver()
98 cur->callback_data); in event_deliver()
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/
Dti,omap-remoteproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
Dti,davinci-rproc.txt4 Binding status: Unstable - Subject to changes for DT representation of clocks
7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 is used to offload some of the processor-intensive tasks or algorithms, for
11 The processor cores in the sub-system usually contain additional sub-modules
16 DSP Device Node:
18 Each DSP Core sub-system is represented as a single DT node.
21 --------------------
24 - compatible: Should be one of the following,
25 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
27 - reg: Should contain an entry for each value in 'reg-names'.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/
Dti,omap-remoteproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
Dti,davinci-rproc.txt4 Binding status: Unstable - Subject to changes for DT representation of clocks
7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 is used to offload some of the processor-intensive tasks or algorithms, for
11 The processor cores in the sub-system usually contain additional sub-modules
16 DSP Device Node:
18 Each DSP Core sub-system is represented as a single DT node.
21 --------------------
24 - compatible: Should be one of the following,
25 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
27 - reg: Should contain an entry for each value in 'reg-names'.
[all …]
/kernel/linux/linux-6.6/net/tipc/
Dname_table.c4 * Copyright (c) 2000-2006, 2014-2018, Ericsson AB
5 * Copyright (c) 2004-2008, 2010-2014, Wind River Systems
6 * Copyright (c) 2020-2021, Red Hat Inc
48 #include "node.h"
52 * struct service_range - container for all bindings of a service range
56 * @max: largest 'upper' in this node subtree
57 * @local_publ: list of identical publications made from this node
59 * @all_publ: all publications identical to this one, whatever node and scope
60 * Used by round-robin lookup algorithm
72 * struct tipc_service - container for all published instances of a service type
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/media/
Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/media/
Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/samsung/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dst,stm32-sai.txt4 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-5.10/Documentation/devicetree/bindings/mailbox/
Domap-mailbox.txt25 routed to different processor sub-systems on DRA7xx as they are routed through
32 Mailbox Device Node:
34 A Mailbox device node is used to represent a Mailbox IP instance/cluster within
35 a SoC. The sub-mailboxes are represented as child nodes of this parent node.
38 --------------------
39 - compatible: Should be one of the following,
40 "ti,omap2-mailbox" for OMAP2420, OMAP2430 SoCs
41 "ti,omap3-mailbox" for OMAP3430, OMAP3630 SoCs
42 "ti,omap4-mailbox" for OMAP44xx, OMAP54xx, AM33xx,
44 "ti,am654-mailbox" for K3 AM65x and J721E SoCs
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/dma/
Dadi,axi-dmac.txt1 Analog Devices AXI-DMAC DMA controller
4 - compatible: Must be "adi,axi-dmac-1.00.a".
5 - reg: Specification for the controllers memory mapped register map.
6 - interrupts: Specification for the controllers interrupt.
7 - clocks: Phandle and specifier to the controllers AXI interface clock
8 - #dma-cells: Must be 1.
10 Required sub-nodes:
11 - adi,channels: This sub-node must contain a sub-node for each DMA channel. For
12 the channel sub-nodes the following bindings apply. They must match the
15 Required properties for adi,channels sub-node:
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Dadi,axi-dmac.txt1 Analog Devices AXI-DMAC DMA controller
4 - compatible: Must be "adi,axi-dmac-1.00.a".
5 - reg: Specification for the controllers memory mapped register map.
6 - interrupts: Specification for the controllers interrupt.
7 - clocks: Phandle and specifier to the controllers AXI interface clock
8 - #dma-cells: Must be 1.
10 Required sub-nodes:
11 - adi,channels: This sub-node must contain a sub-node for each DMA channel. For
12 the channel sub-nodes the following bindings apply. They must match the
15 Required properties for adi,channels sub-node:
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mailbox/
Dti,omap-mailbox.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
35 lines can also be routed to different processor sub-systems on DRA7xx as they
48 A Mailbox device node is used to represent a Mailbox IP instance/cluster
49 within a SoC. The sub-mailboxes (actual communication channels) are
50 represented as child nodes of this parent node.
56 "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
[all …]
/kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/
Dopen.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dopen.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/
Disl9305.txt5 - compatible: "isil,isl9305" or "isil,isl9305h"
6 - reg: I2C slave address, usually 0x68.
7 - regulators: A node that houses a sub-node for each regulator within the
8 device. Each sub-node is identified using the node's name, with valid
9 values being "dcd1", "dcd2", "ldo1" and "ldo2". The content of each sub-node
11 - VINDCD1-supply: A phandle to a regulator node supplying VINDCD1.
12 VINDCD2-supply: A phandle to a regulator node supplying VINDCD2.
13 VINLDO1-supply: A phandle to a regulator node supplying VINLDO1.
14 VINLDO2-supply: A phandle to a regulator node supplying VINLDO2.
17 - Per-regulator optional properties are defined in regulator.txt
[all …]
Dtps65132-regulator.txt4 - compatible: "ti,tps65132"
5 - reg: I2C slave address
8 Device supports two regulators OUTP and OUTN. A sub node within the
9 device node describe the properties of these regulators. The sub-node
11 -For regulator outp, the sub node name should be "outp".
12 -For regulator outn, the sub node name should be "outn".
14 -enable-gpios:(active high, output) Regulators are controlled by the input pins.
17 -active-discharge-gpios: (active high, output) Some configurations use delay mechanisms
20 the delay mechanism. Requires specification of ti,active-discharge-time-us
21 -ti,active-discharge-time-us: how long the active discharge gpio should be
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Disl9305.txt5 - compatible: "isil,isl9305" or "isil,isl9305h"
6 - reg: I2C slave address, usually 0x68.
7 - regulators: A node that houses a sub-node for each regulator within the
8 device. Each sub-node is identified using the node's name, with valid
9 values being "dcd1", "dcd2", "ldo1" and "ldo2". The content of each sub-node
11 - VINDCD1-supply: A phandle to a regulator node supplying VINDCD1.
12 VINDCD2-supply: A phandle to a regulator node supplying VINDCD2.
13 VINLDO1-supply: A phandle to a regulator node supplying VINLDO1.
14 VINLDO2-supply: A phandle to a regulator node supplying VINLDO2.
17 - Per-regulator optional properties are defined in regulator.txt
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/
Dphy-cadence-sierra.txt2 -----------------------
5 - compatible: Must be "cdns,sierra-phy-t0" for Sierra in Cadence platform
6 Must be "ti,sierra-phy-t0" for Sierra in TI's J721E SoC.
7 - resets: Must contain an entry for each in reset-names.
9 - reset-names: Must include "sierra_reset" and "sierra_apb".
13 - reg: register range for the PHY.
14 - #address-cells: Must be 1
15 - #size-cells: Must be 0
18 - clocks: Must contain an entry in clock-names.
19 See ../clocks/clock-bindings.txt for details.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/powerpc/fsl/
Draideng.txt3 RAID Engine nodes are defined to describe on-chip RAID accelerators. Each RAID
4 Engine should have a separate node.
11 - compatible: Should contain "fsl,raideng-v1.0" as the value
15 - reg: offset and length of the register set for the device
16 - ranges: standard ranges property specifying the translation
22 compatible = "fsl,raideng-v1.0";
23 #address-cells = <1>;
24 #size-cells = <1>;
30 There must be a sub-node for each job queue present in RAID Engine
31 This node must be a sub-node of the main RAID Engine node
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/
Draideng.txt3 RAID Engine nodes are defined to describe on-chip RAID accelerators. Each RAID
4 Engine should have a separate node.
11 - compatible: Should contain "fsl,raideng-v1.0" as the value
15 - reg: offset and length of the register set for the device
16 - ranges: standard ranges property specifying the translation
22 compatible = "fsl,raideng-v1.0";
23 #address-cells = <1>;
24 #size-cells = <1>;
30 There must be a sub-node for each job queue present in RAID Engine
31 This node must be a sub-node of the main RAID Engine node
[all …]
/kernel/linux/linux-5.10/include/media/
Dv4l2-fwnode.h1 /* SPDX-License-Identifier: GPL-2.0-only */
8 * Copyright (C) 2012 - 2013 Samsung Electronics Co., Ltd.
22 #include <media/v4l2-mediabus.h>
31 * struct v4l2_fwnode_bus_mipi_csi2 - MIPI CSI-2 bus data structure
48 * struct v4l2_fwnode_bus_parallel - parallel data bus data structure
60 * struct v4l2_fwnode_bus_mipi_csi1 - CSI-1/CCP2 data bus structure
62 * false - not inverted, true - inverted
63 * @strobe: false - data/clock, true - data/strobe
78 * struct v4l2_fwnode_endpoint - the endpoint data structure
112 * V4L2_FWNODE_PROPERTY_UNSET - identify a non initialized property
[all …]

12345678910>>...41