sub\-node (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...23

/linux/net/tipc/
H A D	name_table.c	4 * 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 …]
H A D	subscr.c	4 * Copyright (c) 2000-2017, Ericsson AB 5 * Copyright (c) 2005-2007, 2010-2013, Wind River Systems 6 * Copyright (c) 2020-2021, Red Hat Inc 42 static void tipc_sub_send_event(struct tipc_subscription sub, in tipc_sub_send_event() argument 46 struct tipc_subscr s = &sub->evt.s; in tipc_sub_send_event() 47 struct tipc_event *evt = &sub->evt; in tipc_sub_send_event() 49 if (sub->inactive) in tipc_sub_send_event() 53 tipc_evt_write(evt, found_lower, p->sr.lower); in tipc_sub_send_event() 54 tipc_evt_write(evt, found_upper, p->sr.upper); in tipc_sub_send_event() 55 tipc_evt_write(evt, port.ref, p->sk.ref); in tipc_sub_send_event() [all …]
/linux/drivers/misc/vmw_vmci/
H A D	vmci_event.c	1 // 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 …]
/linux/Documentation/devicetree/bindings/remoteproc/
H A D	ti,omap-remoteproc.yaml	1 # 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 …]
H A D	ti,davinci-rproc.txt	4 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that 5 is used to offload some of the processor-intensive tasks or algorithms, for 8 The processor cores in the sub-system usually contain additional sub-modules 13 DSP Device Node: 15 Each DSP Core sub-system is represented as a single DT node. 18 -------------------- 21 - compatible: Should be one of the following, 22 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs 24 - reg: Should contain an entry for each value in 'reg-names'. 27 the parent node's '#address-cells' and '#size-cells' values. [all …]
H A D	ti,k3-dsp-rproc.yaml	`1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-ds [all...]`
/linux/Documentation/admin-guide/media/
H A D	fimc.rst	1 .. 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 …]
/linux/Documentation/devicetree/bindings/mailbox/
H A D	ti,omap-mailbox.yaml	1 # 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 …]
/linux/Documentation/userspace-api/media/v4l/
H A D	open.rst	1 .. 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 …]
/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A D	raideng.txt	3 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 …]
H A D	srio-rmu.txt	`1 Message unit node: 4 this node is required. For devices with RMAN this node should NOT exist. The 5 node is composed of three types of sub-nodes ("fsl-srio-msg-unit", 6 "fsl-srio-dbell-unit" and "fsl-srio-port-write-unit"). 10 - compatible 13 Definition: Must include "fsl,srio-rmu-vX.Y", "fsl,srio-rmu". 18 - reg 20 Value type: <prop-encoded-array> 25 - fsl,liodn 26 Usage: optional-but-recommended (for devices with PAMU) [all …]`
/linux/Documentation/devicetree/bindings/regulator/
H A D	isl9305.txt	5 - 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 …]
H A D	88pm800.txt	`4 - compatible: "marvell,88pm800" 5 - reg: I2C slave address 6 - regulators: A node that houses a sub-node for each regulator within the 7 device. Each sub-node is identified using the node's name (or the deprecated 8 regulator-compatible property if present), with valid values listed below. 9 The content of each sub-node is defined by the standard binding for 25 regulator-min-microvolt = <600000>; 26 regulator-max-microvolt = <3950000>; 27 regulator-boot-on; 28 regulator-always-on; [all …]`
H A D	pv88090.txt	4 - compatible: "pvs,pv88090". 5 - reg: I2C slave address, usually 0x48. 6 - interrupts: the interrupt outputs of the controller 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 listed below. The content of each sub-node is defined by the 14 - Any optional property defined in regulator.txt 21 interrupt-parent = <&gpio>; 26 regulator-name = "buck1"; 27 regulator-min-microvolt = < 600000>; [all …]
H A D	pv88080.txt	4 - compatible: Must be one of the following, depending on the 6 - "pvs,pv88080" (DEPRECATED) 8 - "pvs,pv88080-aa" for PV88080 AA or AB silicon 9 - "pvs,pv88080-ba" for PV88080 BA or BB silicon 11 - reg: I2C slave address, usually 0x49 12 - interrupts: the interrupt outputs of the controller 13 - regulators: A node that houses a sub-node for each regulator within the 14 device. Each sub-node is identified using the node's name, with valid 15 values listed below. The content of each sub-node is defined by the 20 - Any optional property defined in regulator.txt [all …]
H A D	max8907.txt	`4 - compatible: "maxim,max8907" 5 - reg: I2C slave address 6 - interrupts: The interrupt output of the controller 7 - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC. 8 - in-v1-supply: The input supply for SD1. 9 - in-v2-supply: The input supply for SD2. 10 - in-v3-supply: The input supply for SD3. 11 - in1-supply: The input supply for LDO1. 13 - in20-supply: The input supply for LDO20. 14 - regulators: A node that houses a sub-node for each regulator within the [all …]`
/linux/include/media/
H A D	v4l2-event.h	1 /* SPDX-License-Identifier: GPL-2.0-only / 3 v4l2-event.h 7 * Copyright (C) 2009--2010 Nokia Corporation. 25 * struct v4l2_kevent - Internal kernel event struct. 26 * @list: List node for the v4l2_fh->available list. 39 * struct v4l2_subscribed_event_ops - Subscribed event operations. 54 * struct v4l2_subscribed_event - Internal struct representing a subscribed 57 * @list: List node for the v4l2_fh->subscribed list. 60 * @flags: Copy of v4l2_event_subscription->flags. 62 * @node: List node that hooks into the object's event list [all …]
/linux/Documentation/devicetree/bindings/sound/
H A D	cs35l35.txt	5 - compatible : "cirrus,cs35l35" 7 - reg : the I2C address of the device for I2C 9 - VA-supply, VP-supply : power supplies for the device, 13 - interrupts : IRQ line info CS35L35. 14 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt 17 - cirrus,boost-ind-nanohenry: Inductor value for boost converter. The value is 21 - reset-gpios : gpio used to reset the amplifier 23 - cirrus,stereo-config : Boolean to determine if there are 2 AMPs for a 26 - cirrus,audio-channel : Set Location of Audio Signal on Serial Port 30 - cirrus,advisory-channel : Set Location of Advisory Signal on Serial Port [all …]
/linux/drivers/net/pse-pd/
H A D	pd692x0.c	1 // SPDX-License-Identifier: GPL-2.0-only 15 #include <linux/pse-pd/pse.h> 49 u8 sub[3]; 118 /* Template list of communication messages. The non-null bytes defined here 127 .sub = {0x07, 0x55, 0x00}, 133 .sub = {0x07, 0xd0, 0x4e}, 139 .sub 48 u8 sub[3]; global() member 824 struct device_node node; global() member 833 struct device_node node; pd692x0_of_get_ports_manager() local 876 struct device_node managers_node, node; pd692x0_of_get_managers() local 939 pd692x0_register_manager_regulator(struct device * dev,char * reg_name,struct device_node * node) pd692x0_register_manager_regulator() argument [all...]
/linux/Documentation/driver-api/media/
H A D	v4l2-subdev.rst	1 .. SPDX-License-Identifier: GPL-2.0 3 V4L2 sub-devices 4 ---------------- 6 Many drivers need to communicate with sub-devices. These devices can do all 8 encoding or decoding. For webcams common sub-devices are sensors and camera 12 driver with a consistent interface to these sub-devices the 13 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created. 15 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct 16 can be stand-alone for simple sub-devices or it might be embedded in a larger 18 low-level device struct (e.g. ``i2c_client``) that contains the device data as [all …]
/linux/drivers/gpu/drm/xe/
H A D	xe_mem_pool.c	1 // SPDX-License-Identifier: MIT 19 * struct xe_mem_pool - DRM MM pool for sub-allocating memory from a BO on an 22 * The XE memory pool is a DRM MM manager that provides sub-allocation of memory 38 /** @bo: Active pool BO (GGTT-pinned, CPU-mapped). / 50 static struct xe_mem_pool node_to_pool(struct xe_mem_pool_node *node) in node_to_pool() argument 52 return container_of(node->sa_node.mm, struct xe_mem_pool, base); in node_to_pool() 57 return pool->bo->tile; in pool_to_tile() 64 if (pool->is_iomem) in fini_pool_action() 65 kvfree(pool->cpu_addr); in fini_pool_action() 67 drm_mm_takedown(&pool->base); in fini_pool_action() [all …]
/linux/fs/xfs/scrub/
H A D	bitmap.c	1 // SPDX-License-Identifier: GPL-2.0-or-later 3 * Copyright (C) 2018-2023 Oracle. All Rights Reserved. 36 #define START(node) ((node)->bn_start) argument 37 #define LAST(node) ((node)->bn_last) argument 41 * forward-declare them anyway for clarity. 44 xbitmap64_tree_insert(struct xbitmap64_node node, struct rb_root_cached root); 47 xbitmap64_tree_remove(struct xbitmap64_node node, struct rb_root_cached root); 54 xbitmap64_tree_iter_next(struct xbitmap64_node *node, uint64_t start, 63 for ((bn) = rb_entry_safe(rb_first(&(bitmap)->xb_root.rb_root), \ in INTERVAL_TREE_DEFINE() 66 (bn) = rb_entry_safe(rb_next(&(bn)->bn_rbnode), \ [all …]
/linux/Documentation/devicetree/bindings/pci/
H A D	ralink,rt3883-pci.txt	3 1) Main node 7 - compatible: must be "ralink,rt3883-pci" 9 - reg: specifies the physical base address of the controller and 12 - #address-cells: specifies the number of cells needed to encode an 15 - #size-cells: specifies the number of cells used to represent the size 18 - ranges: specifies the translation between child address space and parent 23 - status: indicates the operational status of the device. 28 The main node must have two child nodes which describes the built-in 35 - interrupt-controller: identifies the node as an interrupt controller 37 - #address-cells: specifies the number of cells needed to encode an [all …]
/linux/Documentation/userspace-api/media/
H A D	glossary.rst	1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later 39 Device Node 40 A character device node in the file system used to control and 58 Field-programmable Gate Array 63 See https://en.wikipedia.org/wiki/Field-programmable_gate_array. 72 together make a larger user-facing functional peripheral. For 80 Inter-Integrated Circuit 82 A multi-master, multi-slave, packet switched, single-ended, 84 like sub-device hardware components. 86 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf. [all …]
/linux/Documentation/devicetree/bindings/leds/
H A D	leds-ns2.txt	1 Binding for dual-GPIO LED found on Network Space v2 (and parents). 4 - compatible: "lacie,ns2-leds". 6 Each LED is represented as a sub-node of the ns2-leds device. 8 Required sub-node properties: 9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification. 10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification. 11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and 12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations 15 Optional sub-node properties: 16 - label: Name for this LED. If omitted, the label is taken from the node name. [all …]

12 3 4 5 6 7 8 9 10 >>...23