Searched refs:within (Results 26 – 50 of 234) sorted by relevance
12345678910
| /Zephyr-latest/ |
| D | LICENSE | 64 subsequently incorporated within the Work.
84 or a Contribution incorporated within the Work constitutes direct
109 within such NOTICE file, excluding those notices that do not
111 of the following places: within a NOTICE text file distributed
112 as part of the Derivative Works; within the Source form or
114 within a display generated by the Derivative Works, if and
118 notices within Derivative Works that You distribute, alongside
187 identification within third-party archives.
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_2.rst | 28 call, within module that gathers the statistics.
119 | "fields" | this is map of entries within groups that consists of pairs where the |
141 calls, within module that gathers the statistics; this means that this command
|
| /Zephyr-latest/boards/shields/seeed_xiao_round_display/doc/ |
| D | index.rst | 12 within its compact size, perfect for interactive displays in smart home,
|
| /Zephyr-latest/samples/subsys/fs/fatfs_fstab/ |
| D | README.rst | 18 and afterwards run the generated executable file within the build folder.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.arm_arch | 26 the workaround for the erratum within the timer driver.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/smp/ |
| D | Kconfig | 19 the one that encapsulates everything within response.
74 be expected to be decoded within different command groups.
130 be encoded within different comm&& groups.
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | dlist.rst | 18 list (typically embedded within the struct to be tracked, as described
38 being inspected within the code block, a "CONTAINER" style that
68 within the list to be avoided. Exactly the same operations are run,
|
| /Zephyr-latest/doc/contribute/style/ |
| D | cmake.rst | 15 within a CMake file.
73 - **Use Lowercase for Local Variables**: For local variables within CMake
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | regulators.rst | 20 controlled within the driver for the corresponding node, e.g. a sensor.
|
| D | fuel_gauge.rst | 32 Many fuel gauges embedded within battery packs expose a register address that when written to with a
|
| /Zephyr-latest/doc/services/storage/fcb/ |
| D | fcb.rst | 19 Entries in the flash contain the length of the entry, the data within
55 :c:func:`flash_area_read`. You can tell when all data from within a sector
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 81 Some existing drivers within the listed subsystems do not work when
82 threading is disabled, but are within scope based on their subsystem, or
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister_statuses.rst | 195 out of a given Twister run. Thus, any Case within it should also have such a status.
200 terminal Case statuses can be within such a Suite.
211 Whole suite was not run, but only built. It requires than all Cases within were not run.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/fs_mgmt/ |
| D | Kconfig | 45 size/offset within CBOR frame with file chunk.
51 size/offset within CBOR frame with file chunk.
60 Maximal byte length of encoded offset/size, within transferred
63 as it selects sizes of fields within headers.
|
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 65 within the package. That information can be used to convert packet to fully
70 where pointers to non read-only strings are located within the package. Optionally,
126 location within the package. Updating address argument must happen just before string
152 | String location | Indexes of words within the package where read-only strings are located |
157 | Appended | 1 byte: Index within the package to the location of associated argument |
|
| D | notify.rst | 14 This API is intended to be embedded within specific subsystems such as
|
| /Zephyr-latest/drivers/sensor/ti/ina23x/ |
| D | Kconfig | 35 This is the actual shunt voltage measured which is scaled within the
|
| /Zephyr-latest/drivers/sensor/ti/tmag5170/ |
| D | Kconfig | 37 bool "Process trigger within interrupt context"
|
| /Zephyr-latest/boards/nordic/nrf54l20pdk/ |
| D | nrf54l20pdk_nrf54l20-common.dtsi | 33 * PWM signal can be exposed on GPIO pin only within same domain.
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 21 into detail on how Kconfig is used within the Zephyr project, and have some
|
| /Zephyr-latest/tests/drivers/regulator/voltage/boards/ |
| D | mimxrt685_evk_mimxrt685s_cm33.overlay | 41 * a voltage within given tolerance
|
| /Zephyr-latest/doc/project/ |
| D | working_groups.rst | 30 - The structure of each working group within the Zephyr Project should be
82 - Decisions made within a working group are non-binding and are only considered
84 - Lacking any objections from the TSC within 1 week after the communication or
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/cis/ |
| D | Kconfig | 56 unreserved scanning so that the create connection can succeed within
|
| /Zephyr-latest/boards/nordic/nrf54l15dk/ |
| D | nrf54l15dk_common.dtsi | 33 * PWM signal can be exposed on GPIO pin only within same domain.
|
| /Zephyr-latest/tests/benchmarks/posix/threads/ |
| D | README.rst | 7 This benchmark creates and joins as many threads as possible within a configurable time window.
|
12345678910
