Searched refs:subsystems (Results 1 – 25 of 41) sorted by relevance
12
| /Zephyr-Core-3.4.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.4.0/subsys/timing/ |
| D | Kconfig | 18 To be selected by kernel and other subsystems which need
|
| /Zephyr-Core-3.4.0/subsys/emul/ |
| D | Kconfig | 14 of various subsystems. For example, it is possible to write an
|
| /Zephyr-Core-3.4.0/scripts/build/ |
| D | gen_kobject_list.py | 128 subsystems = [ variable
402 elif name in subsystems:
901 for subsystem in subsystems:
928 for subsystem in subsystems:
949 for subsystem in subsystems:
977 subsystems.extend(subsys_list["__subsystem"])
|
| /Zephyr-Core-3.4.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.4.0/doc/services/ |
| D | notify.rst | 14 This API is intended to be embedded within specific subsystems such as
|
| /Zephyr-Core-3.4.0/modules/segger/ |
| D | Kconfig | 17 Selection of this option enables use of RTT for various subsystems.
|
| /Zephyr-Core-3.4.0/doc/develop/toolchains/ |
| D | arm_compiler.rst | 50 Some Zephyr subsystems or modules may also contain C or assembly code
|
| /Zephyr-Core-3.4.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.4.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.
109 * Right to set the overall architecture of the relevant subsystems or areas
111 * Right to make decisions in the relevant subsystems or areas of involvement,
158 * Solicit approvals from maintainers of the subsystems affected
|
| /Zephyr-Core-3.4.0/doc/services/file_system/ |
| D | index.rst | 51 VFS usage are provided as important functionalities in samples for different subsystems.
|
| /Zephyr-Core-3.4.0/doc/contribute/ |
| D | proposals_and_rfcs.rst | 40 - Addition of new boards, SoCs or drivers to existing subsystems
|
| /Zephyr-Core-3.4.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.4.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.4.0/samples/ |
| D | sample_definition_and_criteria.rst | 10 more features, subsystems, or modules. This includes kernel services, drivers, protocols, etc.
|
| /Zephyr-Core-3.4.0/boards/arc/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.4.0/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 117 subsystems, so timing requirements should generally be kept fairly liberal to
|
| /Zephyr-Core-3.4.0/lib/os/ |
| D | Kconfig | 165 Enable the sys_reboot() API. Enabling this can drag in other subsystems
|
| /Zephyr-Core-3.4.0/doc/introduction/ |
| D | index.rst | 175 subsystems and networking.
|
| /Zephyr-Core-3.4.0/doc/hardware/emulator/ |
| D | index.rst | 13 various subsystems. For example, it is possible to write an emulator
|
| /Zephyr-Core-3.4.0/doc/connectivity/usb/device/ |
| D | usb_device.rst | 73 The CDC ACM class is used as backend for different subsystems in Zephyr.
160 backend for other subsystems by setting :ref:`devicetree-chosen-nodes`
|
| /Zephyr-Core-3.4.0/doc/kernel/services/timing/ |
| D | clocks.rst | 265 timeouts. But for many subsystems with simple needs, this may be
342 But some care is still required for subsystems that use it. Note that
|
| /Zephyr-Core-3.4.0/boards/arm/s32z270dc2_r52/support/ |
| D | startup.cmm | 122 ; RTU subsystems out of reset logic
|
| /Zephyr-Core-3.4.0/drivers/console/ |
| D | Kconfig | 7 # Setting shared by different subsystems
|
| /Zephyr-Core-3.4.0/doc/connectivity/networking/api/ |
| D | sockets.rst | 21 Zephyr subsystems.
|
12
