Searched refs:subsystems (Results 1 – 25 of 54) sorted by relevance
123
| /Zephyr-Core-3.7.0/doc/services/serialization/ |
| D | index.rst | 6 Zephyr has support for several data serialization subsystems. These can be used to encode/decode
|
| /Zephyr-Core-3.7.0/doc/kernel/services/threads/ |
| D | nothread.rst | 38 * Pre ``main()`` drivers and subsystems initialization e.g. :c:macro:`SYS_INIT`.
42 * Specifically identified drivers in certain subsystems, listed below.
76 The sections below list driver and functional subsystems that are
81 Some existing drivers within the listed subsystems do not work when
|
| /Zephyr-Core-3.7.0/subsys/timing/ |
| D | Kconfig | 18 To be selected by kernel and other subsystems which need
|
| /Zephyr-Core-3.7.0/modules/hal_nordic/nrfs/backends/ |
| D | Kconfig | 15 This should be higher than priority of other drivers/subsystems
|
| /Zephyr-Core-3.7.0/tests/boards/espressif_esp32/rtc_clk/ |
| D | README.rst | 10 Espressif SOCs have 3 main clock subsystems: CPU, RTC_FAST and RTC_SLOW. Each of these subsystems h…
|
| /Zephyr-Core-3.7.0/lib/os/zvfs/ |
| D | Kconfig | 13 and more. It is designed to be used by all Zephyr subsystems that need to work with files.
|
| /Zephyr-Core-3.7.0/subsys/emul/ |
| D | Kconfig | 14 of various subsystems. For example, it is possible to write an
|
| /Zephyr-Core-3.7.0/scripts/build/ |
| D | gen_kobject_list.py | 128 subsystems = [ variable
406 elif name in subsystems:
910 for subsystem in subsystems:
937 for subsystem in subsystems:
958 for subsystem in subsystems:
986 subsystems.extend(subsys_list["__subsystem"])
|
| /Zephyr-Core-3.7.0/doc/build/kconfig/ |
| D | index.rst | 6 The Zephyr kernel and subsystems can be configured at build time to adapt them
|
| /Zephyr-Core-3.7.0/doc/services/ |
| D | notify.rst | 14 This API is intended to be embedded within specific subsystems such as
|
| /Zephyr-Core-3.7.0/doc/develop/toolchains/ |
| D | arm_compiler.rst | 50 Some Zephyr subsystems or modules may also contain C or assembly code
|
| /Zephyr-Core-3.7.0/modules/segger/ |
| D | Kconfig | 18 Selection of this option enables use of RTT for various subsystems.
|
| /Zephyr-Core-3.7.0/doc/kernel/usermode/ |
| D | kernelobjects.rst | 12 set of subsystems
14 The set of known kernel objects and driver subsystems is defined in
238 When implementing new kernel features or driver subsystems, it may be necessary
240 for creating core kernel objects and new driver subsystems.
257 new subsystem to the :py:data:`subsystems` list.
|
| /Zephyr-Core-3.7.0/doc/services/file_system/ |
| D | index.rst | 51 VFS usage are provided as important functionalities in samples for different subsystems.
|
| /Zephyr-Core-3.7.0/doc/project/ |
| D | project_roles.rst | 13 Architecture, code subsystems, etc.). Maintainers shall also serve as the
23 particular code base areas or subsystems.
121 * Right to set the overall architecture of the relevant subsystems or areas
123 * Right to make decisions in the relevant subsystems or areas of involvement,
175 * Solicit approvals from maintainers of the subsystems affected
357 enough, in which case approvals by other affected subsystems
|
| /Zephyr-Core-3.7.0/boards/qemu/cortex_a53/doc/ |
| D | index.rst | 100 Although this board only supports a single UART, so subsystems like logging
|
| /Zephyr-Core-3.7.0/doc/develop/languages/c/ |
| D | minimal_libc.rst | 8 needs of Zephyr and its subsystems, primarily in the areas of string
|
| /Zephyr-Core-3.7.0/doc/build/dts/ |
| D | zephyr-user-node.rst | 15 used in the upstream Zephyr source code for device drivers, subsystems, etc.
|
| /Zephyr-Core-3.7.0/doc/contribute/ |
| D | proposals_and_rfcs.rst | 40 - Addition of new boards, SoCs or drivers to existing subsystems
|
| /Zephyr-Core-3.7.0/samples/ |
| D | sample_definition_and_criteria.rst | 10 more features, subsystems, or modules. This includes kernel services, drivers, protocols, etc.
|
| /Zephyr-Core-3.7.0/lib/os/ |
| D | Kconfig | 112 Enable the sys_reboot() API. Enabling this can drag in other subsystems
|
| /Zephyr-Core-3.7.0/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 117 subsystems, so timing requirements should generally be kept fairly liberal to
|
| /Zephyr-Core-3.7.0/boards/snps/emsdp/doc/ |
| D | index.rst | 10 for rapid software development on ARC EM processor-based subsystems. It is intended
11 to accelerate software development and debug of ARC EM processors and subsystems for
|
| /Zephyr-Core-3.7.0/doc/services/pm/ |
| D | device.rst | 24 device drivers, subsystems, and applications. While device drivers
29 Each layer—device drivers, subsystems, and applications—can operate
55 Coordination between device drivers, subsystems, and applications is
|
| /Zephyr-Core-3.7.0/doc/hardware/emulator/ |
| D | bus_emulators.rst | 13 various subsystems. For example, it is possible to write an emulator
|
123
