Home
last modified time | relevance | path

Searched full:identify (Results 1 – 25 of 128) sorted by relevance

123456

/Zephyr-Core-3.5.0/dts/bindings/sensor/
Daosong,dht.yaml31 Set to identify sensor as a DHT22/AM2303. Leave unset to identify
/Zephyr-Core-3.5.0/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-Core-3.5.0/.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-Core-3.5.0/subsys/usb/device_next/
Dusbd_class_api.h48 * the USB device core will identify proper class instance
51 * to identify the class, if more than one class instance is
81 * the USB device core will identify proper class instance
84 * to identify the class, if more than one class instance is
/Zephyr-Core-3.5.0/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
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
Dissues.rst24 To identify the commit causing the regression, several methods could be used,
/Zephyr-Core-3.5.0/lib/libc/newlib/include/
Dstdint.h25 * infrastructure should be used to identify it and provide an
/Zephyr-Core-3.5.0/dts/bindings/led/
Dpwm-leds.yaml27 application to identify this LED or to retrieve its number/index
Dgpio-leds.yaml47 application to identify this LED or to retrieve its number/index
/Zephyr-Core-3.5.0/dts/bindings/base/
Dpm.yaml10 Property to identify that a device can be used as wake up source.
/Zephyr-Core-3.5.0/doc/hardware/peripherals/
Dregulators.rst11 The ``*-supply`` devicetree properties are used to identify the regulator(s)
/Zephyr-Core-3.5.0/drivers/sensor/sx9500/
Dsx9500.h21 /* These are used both in the IRQ_SRC register, to identify which
/Zephyr-Core-3.5.0/samples/net/cellular_modem/
DREADME.rst19 This sample uses the devicetree alias modem to identify
/Zephyr-Core-3.5.0/dts/bindings/test/
Dvnd,pinctrl-test.yaml57 32-bit integer that is just used to identify the entry for testing
/Zephyr-Core-3.5.0/samples/tfm_integration/psa_crypto/src/
Dutil_app_cfg.h19 * firmware updates, since they can be used to identify to layout of the rest
Dpsa_attestation.h33 * data points used to uniquely identify this device to an external
/Zephyr-Core-3.5.0/subsys/usb/device/class/hid/
DKconfig53 The application can use Report ID to identify data fields
/Zephyr-Core-3.5.0/tests/drivers/i2c/i2c_target_api/
DREADME.txt19 second EEPROM just to identify the bus.
/Zephyr-Core-3.5.0/samples/sensor/dht/
DREADME.rst16 overlay must be provided to identify the sensor variant and the GPIO
/Zephyr-Core-3.5.0/samples/sensor/icm42605/
DREADME.rst18 overlay must be provided to identify the SPI bus and GPIO used to
/Zephyr-Core-3.5.0/soc/arm/microchip_mec/mec172x/
Ddevice_power.h32 * these can be dump on exit to identify which HW block is blocking.
/Zephyr-Core-3.5.0/cmake/
Dtarget_toolchain_flags.cmake1 # Uniquely identify the toolchain wrt. its capabilities.
/Zephyr-Core-3.5.0/samples/sensor/mpu6050/
DREADME.rst20 overlay must be provided to identify the I2C bus and GPIO used to
/Zephyr-Core-3.5.0/samples/sensor/grow_r502a/
DREADME.rst28 overlay must be provided to identify the UART bus and the GPIO

123456