Searched full:correspond (Results 1 – 25 of 68) sorted by relevance
123
| /Zephyr-Core-3.5.0/dts/bindings/dac/ |
| D | microchip,mcp4728.yaml | 18 Note: array entries correspond to the successive channels
30 Note: array entries correspond to the successive channels
40 Note: array entries correspond to the successive channels
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/audio/ |
| D | csip_crypto.h | 45 * If the pairing was performed on LE, the 64 LSBs of K correspond to the 64
48 * Part H, Section 2.1 in [2]), and the 64 MSBs of K correspond to the 64 MSBs
72 * If the pairing was performed on LE, the 64 LSBs of K correspond to the 64
75 * Part H, Section 2.1 in [2]), and the 64 MSBs of K correspond to the 64 MSBs
|
| /Zephyr-Core-3.5.0/dts/bindings/gpio/ |
| D | adafruit-feather-header.yaml | 16 through 5 correspond to A0 through A5, and parent pins 6 through 20
17 correspond as depicted below:
|
| D | digilent,pmod.yaml | 8 through 3 correspond to IO1 through IO4, and parent pins 4 through 7
9 correspond to IO5 through IO8, as depicted below for a 12-pin connector.
|
| D | arduino-nano-header-r3.yaml | 16 through 13 correspond to D0 through D13, and parent pins 14 through 21
17 correspond to A0 through A7, as depicted below.
|
| D | particle-gen3-header.yaml | 17 0 through 8 correspond to the pins on the 12-pin header, starting
18 from the bottom; and pins 9 through 21 correspond to pins on the
|
| D | arduino-header-r3.yaml | 24 through 5 correspond to A0 through A5, and parent pins 6 through 21
25 correspond to D0 through D15, as depicted below:
|
| D | arduino-mkr-header.yaml | 18 through 14 correspond to D0 through D21, and parent pins 15 through 21
19 correspond to A0 through A6, as depicted below.
|
| D | seeed-xiao-header.yaml | 20 through 10 correspond to D0 through D10, as depicted below:
|
| D | xlnx,xps-gpio-1.00.a.yaml | 9 # Property names correspond to a subset of those generated by
|
| /Zephyr-Core-3.5.0/scripts/logging/dictionary/dictionary_parser/ |
| D | __init__.py | 18 # DB version 1 and 2 correspond to v1 parser
|
| /Zephyr-Core-3.5.0/tests/cmake/snippets/src/ |
| D | main.c | 29 * correspond to the initial values set by `prj.conf`. in ZTEST()
37 * config values correspond to the values set by the `foo` in ZTEST()
46 * config values correspond to the values set by the `bar` in ZTEST()
|
| /Zephyr-Core-3.5.0/dts/bindings/spi/ |
| D | xlnx,xps-spi-2.00.a.yaml | 10 # Property names correspond to a subset of those generated by
|
| D | nxp,imx-flexspi.yaml | 70 The tuple fields correspond to the following register bitfields:
|
| /Zephyr-Core-3.5.0/dts/bindings/adc/ |
| D | arduino,uno-adc.yaml | 12 pins 0 through 5 correspond to A0 through A5.
|
| /Zephyr-Core-3.5.0/dts/bindings/rng/ |
| D | st,stm32-rng.yaml | 33 The Health Register (health-test-config property) must correspond
|
| /Zephyr-Core-3.5.0/dts/bindings/rtc/ |
| D | xlnx,xps-timer-1.00.a.yaml | 7 # Property names correspond to those used by Xilinx PetaLinux:
|
| /Zephyr-Core-3.5.0/subsys/mgmt/mcumgr/util/include/mgmt/mcumgr/util/ |
| D | zcbor_bulk.h | 32 * @param vp non-NULL pointer for result of decoding; should correspond
59 * @param vp non-NULL pointer for result of decoding; should correspond
|
| /Zephyr-Core-3.5.0/subsys/usb/device/class/hid/ |
| D | Kconfig | 55 This configuration value should correspond to the number of Input
|
| /Zephyr-Core-3.5.0/include/zephyr/arch/arc/v2/mpu/ |
| D | arc_core_mpu.h | 21 * An intent type (i.e. THREAD_STACK_GUARD) can correspond to a different set
|
| /Zephyr-Core-3.5.0/drivers/ieee802154/ |
| D | Kconfig.cc13xx_cc26xx | 79 shall correspond to a received signal power of at most 10 dB
|
| /Zephyr-Core-3.5.0/include/zephyr/dt-bindings/pm/ |
| D | imx_spc.h | 11 * as which peripherals to gate clocks to. Higher values correspond to more
|
| /Zephyr-Core-3.5.0/subsys/net/ip/ |
| D | net_timeout.c | 113 /* There's more to do. We need to update timer_start to correspond to in net_timeout_evaluate()
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | access.rst | 201 and is mandatory for all mesh devices. A model may extend and/or correspond to one
203 or correspond to another model by calling :c:func:`bt_mesh_model_correspond`.
|
| /Zephyr-Core-3.5.0/include/zephyr/display/ |
| D | mb_display.h | 76 * correspond to the columns of that row. The value 0 means the pixel is
|
123
