Searched refs:these (Results 26 – 50 of 642) sorted by relevance
12345678910>>...26
| /Zephyr-latest/dts/arm/raspberrypi/rpi_pico/ |
| D | m33.dtsi | 10 * 'socket' within the SoC. Within the datasheet these are core 0 and core 1.
|
| /Zephyr-latest/include/zephyr/linker/ |
| D | rel-sections.ld | 6 * Specify these here so they are not considered orphan sections.
|
| /Zephyr-latest/soc/st/stm32/stm32wb0x/ |
| D | ram_sections.ld | 7 /** Refer to `soc.c` for more information about these areas. */
|
| /Zephyr-latest/tests/drivers/gpio/gpio_basic_api/boards/ |
| D | intel_adl_crb.overlay | 8 * BIOS settings to mark these two pins as GPIO
|
| /Zephyr-latest/samples/subsys/sensing/simple/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/tests/lib/devicetree/api_ext/ |
| D | app.overlay | 10 * with real-world devicetree nodes, to allow these tests to run on
67 /* there should only be one of these */
|
| /Zephyr-latest/doc/build/dts/api/ |
| D | api.rst | 7 based. Use of these macros has no impact on scheduling. They can be used from
10 Some of these -- the ones beginning with ``DT_INST_`` -- require a special
11 macro named ``DT_DRV_COMPAT`` to be defined before they can be used; these are
56 Property values can be read using these macros even if the node is disabled,
66 Use these APIs instead of :ref:`devicetree-property-access` to access the
68 devicetree specification, these macros can be used even for nodes without
83 Use these APIs instead of :ref:`devicetree-property-access` to access the
85 devicetree specification, these macros can be used even for nodes without
95 Use these APIs instead of :ref:`devicetree-property-access` to access the
99 some of these macros can be used even for nodes without matching bindings. This
[all …]
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.esp32 | 15 numbers: noise from these radios are used to feed entropy in this
|
| /Zephyr-latest/doc/develop/west/ |
| D | moving-to-west.rst | 6 To convert a "pre-west" Zephyr setup on your computer to west, follow these
55 information on these repositories.)
|
| /Zephyr-latest/soc/silabs/silabs_siwx91x/ |
| D | Kconfig.defconfig | 19 # prevent proper use of the system with these threads.
|
| /Zephyr-latest/drivers/bluetooth/ |
| D | Kconfig | 10 # Controller support is an HCI driver in itself, so these HCI driver
|
| /Zephyr-latest/samples/subsys/bindesc/read_bindesc/ |
| D | README.rst | 15 Follow these steps to build the ``read_bindesc`` sample application:
|
| /Zephyr-latest/samples/drivers/mbox_data/ |
| D | sysbuild.cmake | 23 # For these NXP boards the main core application is dependent on
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | ps2.rst | 15 with a PS/2 connector, Zephyr provides these PS/2 driver APIs.
|
| /Zephyr-latest/tests/drivers/mbox/mbox_data/ |
| D | sysbuild.cmake | 23 # For these NXP boards the main core application is dependent on
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 10 Two of these DSPs are in the market already, implemented via the
13 these devices, though more exist:
26 series in concept (with the notable difference that these are all
32 DRAM area, a convention it inherits from SOF (these devices have
86 these platforms. Users with access to hardware-level debug and trace
112 # Grab source (these are small)
|
| /Zephyr-latest/arch/arm64/core/ |
| D | CMakeLists.txt | 22 # simple numeric comparison because these values may be
54 # emitting these instructions for better context switching performance.
|
| /Zephyr-latest/drivers/sensor/ti/tmp1075/ |
| D | Kconfig | 22 see TMP1075 spec sheet for more information on how these work.
|
| /Zephyr-latest/boards/shields/nrf7002ek/boards/ |
| D | nrf9160dk_nrf9160_ns.overlay | 14 /* Typically we use GPIO extender to resolve these conflicts but the
|
| D | nrf5340dk_nrf5340_cpuapp.overlay | 7 * same pins as bucken and iovdd-ctrl, we need these pins to be controlled by
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | triggers.rst | 7 generated events. Typically sensors allow setting up these events to cause
|
| /Zephyr-latest/tests/drivers/uart/uart_elementary/ |
| D | README.txt | 5 Hardware setup required for these tests:
|
| /Zephyr-latest/subsys/fb/ |
| D | README_fonts.txt | 6 To reproduce the font bitmaps use these commands:
|
| /Zephyr-latest/tests/subsys/emul/ |
| D | app.overlay | 9 * with real-world devicetree nodes, to allow these tests to run on
|
| /Zephyr-latest/samples/net/dsa/ |
| D | README.rst | 25 Follow these steps to build the DSA sample application:
|
12345678910>>...26
