Home
last modified time | relevance | path

Searched full:relationship (Results 1 – 23 of 23) sorted by relevance

/Zephyr-Core-3.4.0/scripts/west_commands/zspdx/
Ddatatypes.py130 # RelationshipData contains the pre-analysis data about a relationship between
132 # Relationship after we have organized the SPDX Package and File data.
137 # for the "owner" element (e.g., the left side of the Relationship),
150 # for the "other" element (e.g., the right side of the Relationship),
163 # text string with Relationship type
167 # Relationship contains the post-analysis, processed data about a relationship
168 # in a form suitable for creating the actual SPDX Relationship in a particular
170 class Relationship: class
172 super(Relationship, self).__init__()
174 # SPDX ID for left side of relationship
[all …]
Dwalker.py12 …Document, File, PackageConfig, Package, RelationshipDataElementType, RelationshipData, Relationship
98 # walk through pending relationship data and create relationships
154 # the DESCRIBES relationship for the build document will be
186 # create DESCRIBES relationship data
213 # create DESCRIBES relationship data
241 # create DESCRIBES relationship data
333 # create pending relationship data entry
345 log.dbg(f" - add pending source file and relationship for {src.path}")
359 # create relationship data
385 # create relationship data
[all …]
Dwriter.py11 # Output tag-value SPDX 2.2 content for the given Relationship object.
14 # 2) rln: Relationship object being described
16 f.write(f"Relationship: {rln.refA} {rln.rlnType} {rln.refB}\n")
/Zephyr-Core-3.4.0/drivers/timer/
DKconfig.cavs8 # symbiotic relationship between these two projects, that from
/Zephyr-Core-3.4.0/doc/kernel/usermode/
Dmpu_userspace.rst7 set of stacks. These stacks exist in a 1:1 relationship with each thread stack
/Zephyr-Core-3.4.0/dts/bindings/timer/
Dnuclei,systimer.yaml38 The relationship with the frequency division ratio is as
/Zephyr-Core-3.4.0/tests/subsys/pm/power_mgmt_multicore/src/
Dmain.c19 * to use. They have no relationship with any platform.
/Zephyr-Core-3.4.0/drivers/interrupt_controller/
Dintc_miwu.c21 * This driver uses device tree files to present the relationship between
24 * 1. npcxn-miwus-wui-map.dtsi: it presents relationship between wake-up inputs
26 * 2. npcxn-miwus-int-map.dtsi: it presents relationship between MIWU group
/Zephyr-Core-3.4.0/tests/bsim/bluetooth/host/att/read_fill_buf/testlib/
Dsecurity.c28 /* Mutex operations establish a happens-before relationship. This in security_changed()
/Zephyr-Core-3.4.0/doc/services/storage/flash_map/
Dflash_map.rst48 Relationship with Devicetree
/Zephyr-Core-3.4.0/arch/x86/core/ia32/
Dirq_manage.c87 * This routine assumes that the relationship between interrupt priority and
/Zephyr-Core-3.4.0/doc/services/pm/
Ddevice.rst90 Each :c:enum:`pm_device_action` have a direct an unambiguous relationship with
/Zephyr-Core-3.4.0/doc/build/dts/
Dphandles.rst66 devicetree specification to capture the relationship between the two nodes.
/Zephyr-Core-3.4.0/scripts/pylib/twister/twisterlib/
Denvironment.py256 "are treated as a logical 'or' relationship")
584 "are treated as a logical 'or' relationship.")
/Zephyr-Core-3.4.0/doc/connectivity/bluetooth/
Dbluetooth-arch.rst314 To achieve a secure relationship between two Bluetooth devices a process
/Zephyr-Core-3.4.0/dts/arm/nuvoton/npcx/
Dnpcx-miwus-wui-map.dtsi502 /* Pseudo MIWU device to present no mapping relationship */
/Zephyr-Core-3.4.0/doc/hardware/pinctrl/
Dindex.rst423 It is worth to note that the only relationship between a device and its
/Zephyr-Core-3.4.0/doc/build/kconfig/
Dtips.rst515 relationship between the symbols harder to understand, even if code never looks
/Zephyr-Core-3.4.0/include/zephyr/
Ddevice.h395 * relationship to this node. The individual sets are extracted with
/Zephyr-Core-3.4.0/include/zephyr/sys/
Dtime_units.h130 * the same mathematical relationship, each expressed with and in z_tmcvt()
/Zephyr-Core-3.4.0/subsys/bluetooth/host/
Dgatt.c1000 * For clients with a trusted relationship, the characteristic value in remove_cf_cfg()
1002 * trusted relationship the characteristic value shall be set to the in remove_cf_cfg()
1168 * shall not change if the server has a trusted relationship with any
/Zephyr-Core-3.4.0/include/zephyr/net/
Dnet_if.h467 * Because of the strong relationship between a device driver and such
/Zephyr-Core-3.4.0/doc/develop/west/
Dmanifest.rst42 project repositories. This relationship is shown using dotted line arrows in the