Home
last modified time | relevance | path

Searched refs:identify (Results 1 – 25 of 56) sorted by relevance

123

/Zephyr-latest/doc/develop/sca/
Dsparse.rst14 ``__cache`` used to identify pointers from the cached address range on the
15 Xtensa architecture. This helps identify cases where cached and uncached
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D007_ext-source.md28 for the foreseeable future. Please use GitHub IDs to identify them. You can
29 choose to identify a single maintainer only or add collaborators as well
/Zephyr-latest/doc/security/standards/
Dindex.rst15 This section aims to identify and assess which Zephyr project components are impacted
/Zephyr-latest/doc/hardware/peripherals/
Dregulators.rst11 The ``*-supply`` devicetree properties are used to identify the regulator(s)
/Zephyr-latest/samples/sensor/icm42605/
DREADME.rst20 overlay must be provided to identify the SPI bus and GPIO used to
/Zephyr-latest/doc/project/
Dmodifying_contributions.rst53 as *stale*. Read about how to identify pull requests as stale in
63 shall identify in the commit message(s) the original source the
Dissues.rst24 To identify the commit causing the regression, several methods could be used,
Ddocumentation.rst47 reports and using their name and identifier is the best way to identify them
53 documentation in its own module and identify it uniquely when parsing test data
/Zephyr-latest/samples/sensor/mpu6050/
DREADME.rst22 overlay must be provided to identify the I2C bus and GPIO used to
/Zephyr-latest/samples/net/cellular_modem/
DREADME.rst19 This sample uses the devicetree alias ``modem`` to identify
/Zephyr-latest/samples/sensor/6dof_motion_drdy/
DREADME.rst19 overlay must be provided to identify the 6-axis motion sensor, the SPI or I2C bus interface and the…
/Zephyr-latest/subsys/usb/device/class/hid/
DKconfig53 The application can use Report ID to identify data fields
/Zephyr-latest/samples/sensor/grow_r502a/
DREADME.rst26 overlay must be provided to identify the UART bus and the GPIO
/Zephyr-latest/samples/sensor/isl29035/
DREADME.rst24 identify the interrupt signal.
/Zephyr-latest/tests/drivers/i2c/i2c_target_api/
DREADME.txt19 second EEPROM just to identify the bus.
/Zephyr-latest/cmake/
Dtarget_toolchain_flags.cmake1 # Uniquely identify the toolchain wrt. its capabilities.
/Zephyr-latest/samples/sensor/tdk_apex/
DREADME.rst37 overlay must be provided to identify the TDK sensor, the SPI or I2C bus interface and the interrupt
/Zephyr-latest/doc/develop/toolchains/
Dcustom_cmake.rst49 Some custom compilers identify themselves as the compiler on which they are
/Zephyr-latest/doc/develop/optimizations/
Dtools.rst30 of the function for the given symbol nor identify where it comes from.
37 to get the name of the function, but it was unable to identify where it comes from.
/Zephyr-latest/samples/net/cloud/tagoio_http_post/
DREADME.rst33 is it! Now reveal your device token. The token will be used to identify your
/Zephyr-latest/subsys/settings/
DKconfig104 Magic 32-bit word for to identify valid settings area
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_handlers.rst9 MCUmgr functions by having group handlers which identify a group of functions relating to a
12 corresponding group ID values. The group ID is included in SMP headers to identify which
/Zephyr-latest/subsys/bluetooth/mesh/shell/
Dcfg.c853 uint8_t status, identify; in cmd_node_id() local
865 &identify); in cmd_node_id()
880 new_identify, &status, &identify); in cmd_node_id()
890 shell_print(sh, "Node Identify Get/Set successful with identify 0x%02x", identify); in cmd_node_id()
/Zephyr-latest/doc/hardware/peripherals/can/
Dcontroller.rst60 CAN uses so-called identifiers to identify the frame instead of addresses to
61 identify a node.
/Zephyr-latest/doc/kernel/object_cores/
Dindex.rst6 Object cores are a kernel debugging tool that can be used to both identify and

123