Home
last modified time | relevance | path

Searched full:correspond (Results 1 – 25 of 67) sorted by relevance

123

/Zephyr-Core-3.6.0/dts/bindings/dac/
Dmicrochip,mcp4728.yaml18 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.6.0/dts/bindings/gpio/
Dadafruit-feather-header.yaml16 through 5 correspond to A0 through A5, and parent pins 6 through 20
17 correspond as depicted below:
Ddigilent,pmod.yaml8 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.
Darduino-nano-header-r3.yaml16 through 13 correspond to D0 through D13, and parent pins 14 through 21
17 correspond to A0 through A7, as depicted below.
Dparticle-gen3-header.yaml17 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
Darduino-header-r3.yaml24 through 5 correspond to A0 through A5, and parent pins 6 through 21
25 correspond to D0 through D15, as depicted below:
Darduino-mkr-header.yaml18 through 14 correspond to D0 through D21, and parent pins 15 through 21
19 correspond to A0 through A6, as depicted below.
Dseeed-xiao-header.yaml20 through 10 correspond to D0 through D10, as depicted below:
Dxlnx,xps-gpio-1.00.a.yaml9 # Property names correspond to a subset of those generated by
/Zephyr-Core-3.6.0/subsys/bluetooth/audio/
Dcsip_crypto.h45 * 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.6.0/scripts/logging/dictionary/dictionary_parser/
D__init__.py18 # DB version 1 and 2 correspond to v1 parser
/Zephyr-Core-3.6.0/tests/cmake/snippets/src/
Dmain.c29 * 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.6.0/dts/bindings/adc/
Darduino,uno-adc.yaml12 pins 0 through 5 correspond to A0 through A5.
/Zephyr-Core-3.6.0/dts/bindings/spi/
Dxlnx,xps-spi-2.00.a.yaml10 # Property names correspond to a subset of those generated by
Dnxp,imx-flexspi.yaml70 The tuple fields correspond to the following register bitfields:
/Zephyr-Core-3.6.0/dts/bindings/rtc/
Dxlnx,xps-timer-1.00.a.yaml7 # Property names correspond to those used by Xilinx PetaLinux:
/Zephyr-Core-3.6.0/dts/bindings/rng/
Dst,stm32-rng.yaml33 The Health Register (health-test-config property) must correspond
/Zephyr-Core-3.6.0/subsys/usb/device/class/hid/
DKconfig55 This configuration value should correspond to the number of Input
/Zephyr-Core-3.6.0/subsys/mgmt/mcumgr/util/include/mgmt/mcumgr/util/
Dzcbor_bulk.h32 * @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.6.0/include/zephyr/arch/arc/v2/mpu/
Darc_core_mpu.h21 * An intent type (i.e. THREAD_STACK_GUARD) can correspond to a different set
/Zephyr-Core-3.6.0/drivers/ieee802154/
DKconfig.cc13xx_cc26xx79 shall correspond to a received signal power of at most 10 dB
/Zephyr-Core-3.6.0/include/zephyr/dt-bindings/pm/
Dimx_spc.h11 * as which peripherals to gate clocks to. Higher values correspond to more
/Zephyr-Core-3.6.0/subsys/net/ip/
Dnet_timeout.c113 /* There's more to do. We need to update timer_start to correspond to in net_timeout_evaluate()
/Zephyr-Core-3.6.0/include/zephyr/display/
Dmb_display.h76 * correspond to the columns of that row. The value 0 means the pixel is
/Zephyr-Core-3.6.0/include/zephyr/arch/x86/ia32/
Darch.h167 * vectors starting at 32 correspond to each priority level.
396 * correspond to any IRQ line (such as spurious vector or SW IRQ)

123