Home
last modified time | relevance | path

Searched full:look (Results 1 – 25 of 242) sorted by relevance

12345678910

/Zephyr-Core-3.5.0/modules/trusted-firmware-m/
DKconfig.tfm.partitions16 to be passed to the TF-M build system. Look at 'config_default.cmake'
27 to be passed to the TF-M build system. Look at 'config_default.cmake'
38 to be passed to the TF-M build system. Look at 'config_default.cmake'
50 to be passed to the TF-M build system. Look at 'config_default.cmake'
61 to be passed to the TF-M build system. Look at 'config_default.cmake'
73 to be passed to the TF-M build system. Look at 'config_default.cmake'
/Zephyr-Core-3.5.0/include/zephyr/sys/
Dsys_io.h94 * @param port the port address from where to look for the bit
104 * @param port the port address from where to look for the bit
115 * @param port the port address from where to look for the bit
128 * @param port the port address from where to look for the bit
141 * @param port the port address from where to look for the bit
244 * @param addr the memory address from where to look for the bit
254 * @param addr the memory address from where to look for the bits
264 * @param addr the memory address from where to look for the bits
274 * @param addr the memory address from where to look for the bit
285 * @param addr the memory address from where to look for the bit
[all …]
/Zephyr-Core-3.5.0/scripts/kconfig/
Dkconfigfunctions.py57 to an EDT node. If it finds an EDT node, it will look to see if that node
197 This function takes a 'node' and will look to see if that 'node' has a
225 This function takes a 'node' and will look to see if that 'node' has a
252 to an EDT node. If it finds an EDT node, it will look to see if that
276 to an EDT node. If it finds an EDT node, it will look to see if that node
315 finds an EDT node, it will look to see if that node has a register at the
341 finds an EDT node, it will look to see if that node has a register at the
429 finds an EDT node, it will look to see if that node has a boolean property
441 If it finds an EDT node, it will look to see if that node has a boolean
483 finds an EDT node, it will look to see if that node has a property
[all …]
/Zephyr-Core-3.5.0/doc/build/dts/
Dtroubleshooting.rst68 linker error. Look for this number in the list of nodes at the top of
91 Now look for this node in :file:`<build>/zephyr/zephyr.dts`, which is the final
138 - Look in :zephyr_file:`drivers` for the appropriate subdirectory that
140 - Look inside that directory for relevant files until you figure out what the
146 example, if your node's compatible is ``vnd,foo-device``, look for a file with this
171 Then you would look inside of :zephyr_file:`drivers/i2c` for the driver file
259 Look at the preprocessor output
351 source file, ``compatible`` should look like ``"vnd,some-device"`` --
/Zephyr-Core-3.5.0/.github/workflows/
Dgreet_first_time_contributor.yml34 …Please take a look at [our commit message guidelines](https://docs.zephyrproject.org/latest/contri…
57 Thank you for your valuable input, and we look forward to seeing more of your
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dzperf.rst37 For TCP testing, the command line would look like this:
51 For TCP the zperf command would look like this:
/Zephyr-Core-3.5.0/doc/services/device_mgmt/
Dmcumgr_handlers.rst44 file would look similar to:
64 file would look similar to:
83 look similar to:
104 to the functionality of the handler being implemented. An example file would look similar to:
114 source files if the Kconfig options are enabled. An example file would look similar to:
/Zephyr-Core-3.5.0/drivers/memc/
Dmemc_nxp_s32_qspi.h13 * @brief Build a QSPI Look-up Table (LUT) sequence entry.
/Zephyr-Core-3.5.0/dts/bindings/i3c/
Di3c-controller.yaml30 and there are I2C devices attached to the bus, look at the Legacy
/Zephyr-Core-3.5.0/dts/bindings/arm/
Datmel,sam-ssc.yaml29 For example dmas for TX, RX would look like
/Zephyr-Core-3.5.0/dts/bindings/pinctrl/
Dsnps,emsdp-pinctrl.yaml11 For example, setting PmodA to SPI would look like this:
Dsifive,pinctrl.yaml15 For example, setting pins 16 and 17 both to IOF0 would look like this:
Dquicklogic,eos-s3-pinctrl.yaml11 For example, setting pins 44 and 45 for use as UART would look like this:
/Zephyr-Core-3.5.0/drivers/watchdog/
Dwdt_iwdg_stm32.h17 * an appropriate reference manual and look for chapter called:
Dwdt_wwdg_stm32.h18 * an appropriate reference manual and look for chapter called:
/Zephyr-Core-3.5.0/dts/bindings/bluetooth/
Dzephyr,bt-hci-spi-slave.yaml8 A node defined via devicetree overlay should look like this:
/Zephyr-Core-3.5.0/dts/bindings/spi/
Datmel,sam-spi.yaml35 For example dmas for TX and RX may look like
/Zephyr-Core-3.5.0/samples/boards/bbc_microbit/pong/
DREADME.rst18 When multi-player mode has been selected the game will try to look for
/Zephyr-Core-3.5.0/scripts/west_commands/zspdx/
Dcmakecache.py17 # walk through and look for non-comment, non-empty lines
/Zephyr-Core-3.5.0/snippets/cdc-acm-console/
DREADME.rst28 device node with driver support. This should look roughly like this in
/Zephyr-Core-3.5.0/dts/bindings/i2c/
Dst,stm32-i2c-v2.yaml37 The resulting table entries should look like <periph_clock
Dnordic,nrf-twi.yaml30 2. Open your SoC's .dtsi file and look for a node definition that
/Zephyr-Core-3.5.0/samples/net/cellular_modem/
DREADME.rst13 script found in the server folder. DNS is used to look
/Zephyr-Core-3.5.0/doc/hardware/arch/
Drisc-v.rst27 kconfig. Look at :file:`arch/riscv/Kconfig.isa` for more information.
/Zephyr-Core-3.5.0/subsys/bluetooth/host/
Dconn_internal.h288 /* Look up an existing sco connection by BT address */
291 /* Look up an existing connection by BT address */
299 /* Look up an existing connection */
332 /* Look up a connection state. For BT_ADDR_LE_ANY, returns the first connection

12345678910