| /Zephyr-Core-3.6.0/tests/bluetooth/controller/ctrl_tx_queue/src/ |
| D | main.c | 45 * (1) Enqueue ctrl nodes.
46 * Dequeue and verify order of the ctrl nodes from (1).
57 /* Enqueue ctrl nodes */ in ZTEST()
62 /* Dequeue ctrl nodes */ in ZTEST()
74 * (1) Enqueue data nodes.
75 * Dequeue and verify order of the data nodes from (1).
82 struct node_tx nodes[SIZE] = { 0 }; in ZTEST() local
86 /* Enqueue data nodes */ in ZTEST()
88 ull_tx_q_enqueue_data(&tx_q, &nodes[i]); in ZTEST()
91 /* Dequeue data nodes */ in ZTEST()
[all …]
|
| /Zephyr-Core-3.6.0/doc/_extensions/zephyr/ |
| D | manifest_projects_table.py | 32 from docutils import nodes
70 def run(self) -> List[nodes.Element]:
86 table = nodes.table()
88 tgroup = nodes.tgroup(cols=2)
89 tgroup += nodes.colspec(colwidth=1)
90 tgroup += nodes.colspec(colwidth=1)
93 thead = nodes.thead()
96 row = nodes.row()
99 entry = nodes.entry()
100 entry += nodes.paragraph(text="Project")
[all …]
|
| D | domain.py | 52 from docutils import nodes
53 from docutils.nodes import Node
61 from sphinx.util.nodes import NodeMatcher, make_refnode
71 class CodeSampleNode(nodes.Element):
75 class RelatedCodeSamplesNode(nodes.Element):
89 Transforms a `CodeSampleNode` into a `nodes.section` named after the code sample name.
91 Moves all sibling nodes that are after the `CodeSampleNode` in the documement under this new
101 new_section = nodes.section(ids=[node["id"]])
102 new_section += nodes.title(text=node["name"])
104 # Move the sibling nodes under the new section
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_cli.rst | 7 sending BLOBs of any size to any number of Target nodes, in both Push BLOB Transfer Mode and Pull
66 Target nodes having the BLOB Transfer Server model subscribe to this group address.
69 BLOB Transfer Client sends each message to all Target nodes at the same time. However, sending
73 losing Target nodes. Using group addresses for BLOB transfers will generally only pay off if the
74 list of Target nodes is extensive, and the effectiveness of each addressing strategy will vary
88 * All Target nodes have responded.
89 * A node has been removed from the list of Target nodes.
98 procedure populates the transfer capabilities from all Target nodes with the most liberal set of
99 parameters that allows all Target nodes to participate in the transfer. Any Target nodes that fail
102 Target nodes are prioritized according to their order in the list of Target nodes. If a Target node
[all …]
|
| D | dfu.rst | 31 The Bluetooth Mesh DFU subsystem defines three different roles the mesh nodes have to assume in the
37 Target nodes, and they will all be updated concurrently.
42 nodes as the Distributor. The Distributor does not select the parameters of the transfer, but
43 relies on an Initiator to give it a list of Target nodes and transfer parameters. The Distributor
47 image to the Target nodes.
53 Target nodes and their firmware, and will control (and initiate) all firmware updates. The
58 :alt: Graphic overview of the DFU roles mesh nodes can have during the process of image
92 Before starting the Distribution stage, the Initiator may optionally check if Target nodes can
93 accept the new firmware. Nodes that do not respond, or respond that they can't receive the new
97 Before the firmware image can be distributed, the Initiator transfers the list of Target nodes
[all …]
|
| /Zephyr-Core-3.6.0/tests/unit/rbtree/ |
| D | main.c | 18 static struct rbnode nodes[MAX_NODES]; variable
23 /* Array of nodes dumped via rb_walk */
48 return (int)(n - &nodes[0]); in node_index()
107 /* Can't have adjacent red nodes */ in check_rbnode()
113 /* All leaf nodes must be at the same black height */ in check_rbnode()
150 /* Make sure all found nodes are in-order and marked in the tree */ in _check_tree()
164 /* Make sure all tree bits properly reflect the set of nodes we found */ in _check_tree()
167 _CHECK(get_node_mask(i) == rb_contains(&test_rbtree, &nodes[i])); in _check_tree()
205 (void)memset(nodes, 0, sizeof(nodes)); in test_tree()
213 rb_insert(&test_rbtree, &nodes[node]); in test_tree()
[all …]
|
| /Zephyr-Core-3.6.0/doc/build/dts/api/ |
| D | api.rst | 36 identifiers for other devicetree nodes using :c:func:`DT_PATH`,
68 devicetree specification, these macros can be used even for nodes without
85 devicetree specification, these macros can be used even for nodes without
99 some of these macros can be used even for nodes without matching bindings. This
121 exists, how many nodes of a certain type exist, whether a node has certain
134 nodes. Dependency tracking relies on a binary "depends on" relation between
135 devicetree nodes, which is defined as the `transitive closure
140 - a node directly depends on any nodes its properties refer to by phandle
143 - a parent node inherits all dependencies from its child nodes
145 A *dependency ordering* of a devicetree is a list of its nodes, where each node
[all …]
|
| /Zephyr-Core-3.6.0/scripts/dts/python-devicetree/src/devicetree/ |
| D | grutils.py | 13 Represent a directed graph with edtlib Node objects as nodes.
15 This is used to determine order dependencies among nodes in a
39 The nodes are added to the graph if necessary.
49 Return the set of nodes calculated to be roots (i.e., those
70 # of the graph: i.e., the sets of nodes that form a minimal
85 … raise Exception('TARJAN: No roots found in graph with {} nodes'.format(len(self.__nodes)))
130 connected components (which can be single nodes). Appearance
142 """Get the nodes that 'node' directly depends on."""
146 """Get the nodes that directly depend on 'node'."""
150 # This sort key ensures that sibling nodes with the same name will
|
| /Zephyr-Core-3.6.0/scripts/pylint/checkers/ |
| D | argparse-checker.py | 9 from astroid import nodes
29 def visit_call(self, node: nodes.Call) -> None:
30 if isinstance(node.func, astroid.nodes.node_classes.Attribute) and \
37 if not isinstance(keyword.value, astroid.nodes.node_classes.Const):
|
| /Zephyr-Core-3.6.0/include/zephyr/bluetooth/mesh/ |
| D | blob_cli.h | 105 /** Linked list of Target nodes. Each node should point to @ref
122 /** Additional response time for the Target nodes, in 10-second increments.
124 * The extra time can be used to give the Target nodes more time to respond
195 * for the given list of Target nodes. All compatible Target nodes have
209 * the Client until all Target nodes have been lost.
221 * Called when the transfer is suspended due to response timeout from all Target nodes.
255 * Called when all Target nodes have responded or the procedure timed-out.
268 /** If @ref blob_cli_broadcast_ctx::acked is true, called after all Target nodes
279 /** If true, non-responsive Target nodes won't be dropped after transfer has timed out. */
320 /** @brief Retrieve transfer capabilities for a list of Target nodes.
[all …]
|
| /Zephyr-Core-3.6.0/doc/_extensions/zephyr/kconfig/ |
| D | __init__.py | 39 from docutils import nodes
49 from sphinx.util.nodes import make_refnode
120 class KconfigSearchNode(nodes.Element):
126 def kconfig_search_visit_html(self, node: nodes.Node) -> None:
128 raise nodes.SkipNode
131 def kconfig_search_visit_latex(self, node: nodes.Node) -> None:
133 raise nodes.SkipNode
162 class _FindKconfigSearchDirectiveVisitor(nodes.NodeVisitor):
167 def unknown_visit(self, node: nodes.Node) -> None:
203 contnode: nodes.Element,
[all …]
|
| /Zephyr-Core-3.6.0/tests/benchmarks/data_structure_perf/rbtree_perf/src/ |
| D | rbtree_perf.c | 21 static struct rbnode nodes[TREE_SIZE]; variable
53 * -# Define some arrays of rbtree nodes.And initialize
55 * -# Then inserting some nodes into the rbtree.
56 * -# Check if the inserted nodes are contained in the
60 * - The inserted nodes are contained in the
112 rb_insert(tree, &nodes[i]); in init_tree()
165 * -# Initialize the rbtree and insert some nodes on it.
202 * the node nodes[TREE_SIZE/2] will be removed and inserted, in ZTEST()
206 test = &nodes[TREE_SIZE/2]; in ZTEST()
|
| /Zephyr-Core-3.6.0/doc/kernel/data_structures/ |
| D | rbtree.rst | 18 Unlike a list, where position is explicit, the ordering of nodes
25 not allowed, nodes within a tree must have a single fixed order for
28 As with the slist and dlist containers, nodes within an rbtree are
36 Nodes can be inserted into a tree with :c:func:`rb_insert` and removed
37 with :c:func:`rb_remove`. Access to the "first" and "last" nodes within a
80 nodes on any path to the root must be the same, and that no more than
81 that number of "extra" red nodes may be present). This rule is
91 nodes can be added underneath the rightmost node without
96 Typical implementations effect this by simply swapping the nodes
|
| /Zephyr-Core-3.6.0/dts/bindings/gpio/ |
| D | ambiq,gpio.yaml | 5 Ambiq GPIO provides the GPIO pin mapping for GPIO child nodes.
13 devicetree and some child nodes which are compatible with "ambiq,gpio-bank"
17 gpio child nodes:
74 child nodes. Each of them covers 32 pins (the default value of "ngpios"
75 property is 32). The "reg" property of child nodes defines the register
|
| D | nxp,imx-rgpio.yaml | 23 pinctrl nodes to use for the gpio port when CONFIG_PINCTRL=y. Note that
24 the order of the nodes matters. The first node for gpio1 will be used
|
| D | nxp,imx-gpio.yaml | 23 pinctrl nodes to use for the gpio port when CONFIG_PINCTRL=y. Note that
24 the order of the nodes matters. The first node for gpio1 will be used
|
| D | nordic,nrf-gpio-forwarder.yaml | 49 Please note that the GPIO flags provided for child nodes of the forwarder
55 Child nodes for the forwarder can be defined independently by multiple DTS
56 files. They are merged into a single node with multiple child nodes when
58 to happen, names of the child nodes must be unique in the scope of a single
|
| /Zephyr-Core-3.6.0/tests/bluetooth/controller/ctrl_api/src/ |
| D | main.c | 203 struct node_tx nodes[SIZE] = { 0 }; in ZTEST() local
210 /* Enqueue data nodes */ in ZTEST()
212 ull_tx_q_enqueue_data(&conn.tx_q, &nodes[i]); in ZTEST()
215 /* Dequeue data nodes */ in ZTEST()
218 zassert_equal_ptr(node, &nodes[i], NULL); in ZTEST()
235 /* Enqueue data nodes */ in ZTEST()
237 ull_tx_q_enqueue_data(&conn.tx_q, &nodes[i]); in ZTEST()
247 /* Dequeue data nodes */ in ZTEST()
250 zassert_equal_ptr(node, &nodes[i], NULL); in ZTEST()
268 /* Enqueue data nodes */ in ZTEST()
[all …]
|
| /Zephyr-Core-3.6.0/dts/bindings/reserved-memory/ |
| D | memory-region.yaml | 4 # Memory region nodes may be referenced by other device nodes
|
| /Zephyr-Core-3.6.0/doc/build/dts/ |
| D | bindings-intro.rst | 10 Devicetree nodes are matched to bindings using their :ref:`compatible
52 The build system uses bindings both to validate devicetree nodes and to convert
75 Other ways nodes are matched to bindings
94 Nodes without compatible properties can be matched to bindings associated with
95 their parent nodes. These are called "child bindings". If a node describes
97 account when matching nodes to bindings. (See :ref:`dt-bindings-on-bus` for
125 subdirectories, when matching nodes to bindings. A file is considered YAML if
|
| D | intro-syntax-structure.rst | 39 Nodes section in Syntax and structure
42 Like any tree data structure, a devicetree has a hierarchy of *nodes*.
43 The above tree has three nodes:
51 Nodes can be assigned *node labels*, which are unique shorthands that refer to argument
56 Devicetree nodes have *paths* identifying their locations in the tree. Like
66 Devicetree nodes can also have *properties*. Properties are name/value pairs.
79 In practice, devicetree nodes usually correspond to some hardware, and the node
88 Nodes corresponding to the I2C bus controller and each I2C peripheral would be
90 I2C peripheral nodes would be children of the bus controller node.
242 ``devicetree.h`` to find nodes with relevant compatibles, in order to
[all …]
|
| /Zephyr-Core-3.6.0/dts/bindings/i2c/ |
| D | infineon,cat1-i2c.yaml | 30 The pinctrl nodes need to be configured as open-drain and
59 We expect that the phandles will reference pinctrl nodes. These
60 nodes will have a nodelabel that matches the Infineon SoC Pinctrl
|
| /Zephyr-Core-3.6.0/dts/bindings/pinctrl/ |
| D | infineon,cat1-pinctrl.yaml | 33 Nodes, which can be found via MPN dtsi.
48 Refer to psoc6_02.124-bga.dtsi for the list of all pre-defined pin control nodes.
50 NOTE1 Pre-defined pin control nodes use macro DT_CAT1_PINMUX to
63 NOTE2 Pre-defined pin control nodes do not have bias pin configuration.
84 An example of the usage of pre-defined pin control nodes in your board's DTS file:
|
| /Zephyr-Core-3.6.0/dts/bindings/serial/ |
| D | cypress,psoc6-uart.yaml | 27 phandles will reference pinctrl nodes. These nodes will have a
|
| /Zephyr-Core-3.6.0/dts/bindings/spi/ |
| D | cypress,psoc6-spi.yaml | 27 expect that the phandles will reference pinctrl nodes. These
28 nodes will have a nodelabel that matches the Cypress SoC HAL defines
|
