Skip to content

Commit 681e1d4

Browse files
nashifcarlescufi
authored andcommitted
doc: clarify what a subsystem is
Clarify what a subsystem is, this has been missing the docs. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
1 parent 99adbad commit 681e1d4

File tree

2 files changed

+12
-0
lines changed

2 files changed

+12
-0
lines changed

doc/glossary.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -140,6 +140,10 @@ Glossary of Terms
140140
A number of different :term:`SoCs <SoC>` that share similar characteristics and
141141
features, and that the vendor typically names and markets together.
142142

143+
subsystem
144+
A subsystem refers to a logically distinct part of the operating system
145+
that handles specific functionality or provides certain services.
146+
143147
system power state
144148
System power states describe the power consumption of the system as a
145149
whole. System power states are represented by :c:enum:`pm_state`.

doc/introduction/index.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,14 @@ The Zephyr kernel supports multiple architectures, including:
2323

2424
The full list of supported boards based on these architectures can be found :ref:`here <boards>`.
2525

26+
In the context of the Zephyr OS, a :term:`subsystem` refers to a logically distinct
27+
part of the operating system that handles specific functionality or provides
28+
certain services. Subsystems can include components such as networking,
29+
file systems, device driver classes, power management, and communication protocols,
30+
among others. Each subsystem is designed to be modular and can be configured,
31+
customized, and extended to meet the requirements of different embedded
32+
applications.
33+
2634
Licensing
2735
*********
2836

0 commit comments

Comments
 (0)