Searched refs:identify (Results 1 – 25 of 56) sorted by relevance
123
/Zephyr-latest/doc/develop/sca/ |
D | sparse.rst | 14 ``__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/ |
D | 007_ext-source.md | 28 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/ |
D | index.rst | 15 This section aims to identify and assess which Zephyr project components are impacted
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | regulators.rst | 11 The ``*-supply`` devicetree properties are used to identify the regulator(s)
|
/Zephyr-latest/samples/sensor/icm42605/ |
D | README.rst | 20 overlay must be provided to identify the SPI bus and GPIO used to
|
/Zephyr-latest/doc/project/ |
D | modifying_contributions.rst | 53 as *stale*. Read about how to identify pull requests as stale in 63 shall identify in the commit message(s) the original source the
|
D | issues.rst | 24 To identify the commit causing the regression, several methods could be used,
|
D | documentation.rst | 47 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/ |
D | README.rst | 22 overlay must be provided to identify the I2C bus and GPIO used to
|
/Zephyr-latest/samples/net/cellular_modem/ |
D | README.rst | 19 This sample uses the devicetree alias ``modem`` to identify
|
/Zephyr-latest/samples/sensor/6dof_motion_drdy/ |
D | README.rst | 19 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/ |
D | Kconfig | 53 The application can use Report ID to identify data fields
|
/Zephyr-latest/samples/sensor/grow_r502a/ |
D | README.rst | 26 overlay must be provided to identify the UART bus and the GPIO
|
/Zephyr-latest/samples/sensor/isl29035/ |
D | README.rst | 24 identify the interrupt signal.
|
/Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
D | README.txt | 19 second EEPROM just to identify the bus.
|
/Zephyr-latest/cmake/ |
D | target_toolchain_flags.cmake | 1 # Uniquely identify the toolchain wrt. its capabilities.
|
/Zephyr-latest/samples/sensor/tdk_apex/ |
D | README.rst | 37 overlay must be provided to identify the TDK sensor, the SPI or I2C bus interface and the interrupt
|
/Zephyr-latest/doc/develop/toolchains/ |
D | custom_cmake.rst | 49 Some custom compilers identify themselves as the compiler on which they are
|
/Zephyr-latest/doc/develop/optimizations/ |
D | tools.rst | 30 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/ |
D | README.rst | 33 is it! Now reveal your device token. The token will be used to identify your
|
/Zephyr-latest/subsys/settings/ |
D | Kconfig | 104 Magic 32-bit word for to identify valid settings area
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | mcumgr_handlers.rst | 9 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/ |
D | cfg.c | 853 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/ |
D | controller.rst | 60 CAN uses so-called identifiers to identify the frame instead of addresses to 61 identify a node.
|
/Zephyr-latest/doc/kernel/object_cores/ |
D | index.rst | 6 Object cores are a kernel debugging tool that can be used to both identify and
|
123