Searched refs:some (Results 126 – 150 of 591) sorted by relevance
12345678910>>...24
/Zephyr-latest/samples/drivers/display/ |
D | README.rst | 10 This sample will draw some basic rectangles onto the display.
|
/Zephyr-latest/doc/ |
D | LICENSING.rst | 9 are not covered by the `Apache 2.0 License`_. In some places
|
/Zephyr-latest/doc/services/ |
D | notify.rst | 9 often a good method, but some application architectures may be more
|
/Zephyr-latest/samples/drivers/misc/grove_display/ |
D | README.rst | 28 On some boards you will need to use 2 pull-up resistors (10k Ohm) between the
|
/Zephyr-latest/arch/posix/ |
D | CMakeLists.txt | 47 # some gcc versions fail to build without -fPIC 61 # which causes some issues with literal float comparisons. So we set it 83 # While doing the partial linking of the native library, some symbols will be missing
|
/Zephyr-latest/doc/contribute/ |
D | index.rst | 58 This page provides some simple guidelines for writing documentation using the reSTructuredText 87 As some functionality might only be made available with the help of executable code distributed
|
/Zephyr-latest/doc/hardware/porting/ |
D | arch.rst | 21 some are optional: 36 controller are tied to the architecture (some required, some optional). 38 * **Utility libraries**: some common kernel APIs rely on a 66 some architectures require a bit more work to be performed. 95 When a device wants to signal the processor that there is some work to be done 105 The kernel has to perform some work in addition to the work the handler itself 142 * Using some architecture defined mechanism, the parameter value is forced in 169 we strongly suggest that handlers at least print some debug information. The 235 when an object being operated on is unavailable, and some thread 331 ``struct k_thread`` and put it into an appropriate register (or some [all …]
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | ppp.rst | 17 cannot be transmitted over a modem line on their own, without some data link
|
/Zephyr-latest/doc/develop/west/ |
D | moving-to-west.rst | 46 workspace, and does some other setup. It will not change the contents of
|
D | index.rst | 15 Like ``git`` and ``docker``, the top-level ``west`` command takes some common
|
/Zephyr-latest/samples/subsys/dap/ |
D | README.rst | 34 Connect HIC to the target and try some pyOCD commands, for example:
|
/Zephyr-latest/samples/subsys/fs/fs_sample/boards/ |
D | nrf52840dk_nrf52840_ram_disk_region.overlay | 8 * of RAM there is. We need some for the Disk, so we need to
|
/Zephyr-latest/samples/fuel_gauge/max17048/ |
D | README.rst | 33 if you plug/unplug a charger it will take some time until it is actually detected by the chip. Don'…
|
/Zephyr-latest/doc/build/dts/api/ |
D | api.rst | 99 some of these macros can be used even for nodes without matching bindings. This 136 The ``devicetree.h`` API has some support for tracking dependencies between 216 and so on. There are some exceptions: :c:macro:`DT_ANY_INST_ON_BUS_STATUS_OKAY` 369 The following table documents some commonly used Zephyr-specific chosen nodes. 396 - Core-Coupled Memory node on some STM32 SoCs 407 - Data Tightly Coupled Memory node on some Arm SoCs 428 - Instruction Tightly Coupled Memory node on some Arm SoCs
|
/Zephyr-latest/subsys/logging/ |
D | Kconfig.misc | 23 Using VLA slightly decreases stack usage in some cases it may not be 46 be used when optimization is disabled because some compilers
|
/Zephyr-latest/drivers/serial/ |
D | Kconfig.nrfx_uart_instance | 62 that with higher speeds and/or high cpu load some data can be lost. 119 Amount of space dedicated for RX. It is divided into chunks with some
|
/Zephyr-latest/modules/cmsis-dsp/ |
D | Kconfig | 268 available on most Cortex-A and some Cortex-R processors. 275 available on most Cortex-A and some Cortex-R processors. 282 available on some Cortex-M processors.
|
/Zephyr-latest/drivers/sensor/nxp/fxas21002/ |
D | Kconfig | 22 The datasheet defines the value of the WHOAMI register, but some
|
/Zephyr-latest/samples/shields/npm1300_ek/doc/ |
D | index.rst | 43 the regulators embedded in the PMIC. Below you can find some command examples.
|
/Zephyr-latest/samples/drivers/watchdog/ |
D | README.rst | 12 A typical use case for a watchdog is that the board is restarted in case some piece of code
|
/Zephyr-latest/ |
D | CONTRIBUTING.rst | 17 * There are some imported or reused components of the Zephyr project that
|
/Zephyr-latest/lib/net_buf/ |
D | Kconfig | 57 some hardware IP with DMA that requires the buffers to be aligned
|
/Zephyr-latest/boards/nordic/thingy53/doc/ |
D | index.rst | 40 Thingy:53 does not have an on-board J-Link debug IC as some other nRF5
|
/Zephyr-latest/doc/kernel/usermode/ |
D | memory_domain.rst | 7 (Memory Protection Unit) hardware. We do support some architectures, such as x86, 92 architecture supports both operating modes. However, some architectures 155 Conceptually, a memory domain is a collection of some number of memory 161 mode. In some cases this may be unavoidable; for example some architectures do 191 that partitions be sized to some power of two, and aligned to their own 193 the size some multiple of the page size. 407 If the thread was already a member of some other domain (including the
|
/Zephyr-latest/samples/drivers/clock_control_xec/ |
D | README.rst | 11 hardware configuration and exercises some clock control
|
12345678910>>...24