Searched full:subsystem (Results 1 – 25 of 410) sorted by relevance
12345678910>>...17
| /Zephyr-Core-3.5.0/tests/subsys/sd/sdmmc/ |
| D | README.txt | 1 SDMMC Subsystem Test
4 This test is designed to verify the SD subsystem stack implementation,
6 subsystem. Due to the differences between underlying SD host controller drivers,
13 test the initialization flow of the SDMMC subsystem to verify that the stack
16 * IOCTL test: verify the SD subsystem correctly implements IOCTL calls required
20 block reads. Ensure the subsystem will reject reads beyond the end of
24 block writes. Ensure the subsystem will reject writes beyond the end of
|
| /Zephyr-Core-3.5.0/tests/subsys/sd/mmc/ |
| D | README.txt | 1 MMC Subsystem Test
6 subsystem. Due to the differences between underlying SD host controller drivers,
13 test the initialization flow of the MMC subsystem to verify that the stack
16 * IOCTL test: verify the SD subsystem correctly implements IOCTL calls required
20 block reads. Ensure the subsystem will reject reads beyond the end of
24 block writes. Ensure the subsystem will reject writes beyond the end of
|
| /Zephyr-Core-3.5.0/doc/services/sensing/ |
| D | index.rst | 3 Sensing Subsystem
13 Sensing Subsystem is a high level sensor framework inside the OS user
17 Key concepts in Sensing Subsystem include physical sensor and virtual sensor objects,
24 The sensing subsystem relies on Zephyr sensor device APIs (existing version or update in future)
27 Use of the sensing subsystem is optional. Applications that only need to access simple sensors
30 Since the sensing subsystem is separated from device driver layer or
37 The sensing subsystem is decoupled with any sensor expose/transfer
45 Sensing subsystem can help build a unified Zephyr sensing architecture for
48 The diagram below illustrates how the Sensing Subsystem integrates with up-layer frameworks.
57 * Reusable and configurable standalone subsystem.
[all …]
|
| /Zephyr-Core-3.5.0/subsys/input/ |
| D | Kconfig | 7 Include input subsystem and drivers in the system config.
16 int "Input subsystem and drivers init priority"
19 Input subsystem and drivers initialization priority.
81 Enable the input shell, for interacting with the input subsystem
|
| /Zephyr-Core-3.5.0/tests/bluetooth/df/common/src/ |
| D | bt_common.c | 21 /* Initialize bluetooth subsystem */ in ut_bt_setup()
23 zassert_equal(err, 0, "Bluetooth subsystem initialization failed"); in ut_bt_setup()
33 zassert_equal(err, 0, "Bluetooth subsystem de-initialization failed"); in ut_bt_teardown()
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | ieee802154.rst | 46 Gives an introduction and overview over the whole IEEE 802.15.4 subsystem and
57 This is the main subsystem-specific API of interest to IEEE 802.15.4
58 **application developers** as it allows to configure the IEEE 802.15.4 subsystem
61 Zephyr's generic subsystem-independent documentation. Look out for
85 therefore of interest to IEEE 802.15.4 **subsystem contributors** only.
94 API is of interest to OpenThread L2 **subsystem contributors** only.
96 The OpenThread API is part of the :ref:`thread_protocol_interface` subsystem and
|
| /Zephyr-Core-3.5.0/dts/bindings/sensor/ |
| D | zephyr,sensing.yaml | 5 description: Sensing Subsystem
9 # To add sensor subsystem related common feature
|
| /Zephyr-Core-3.5.0/samples/subsys/sensing/ |
| D | sensing.rst | 1 .. _sensing-subsystem-samples:
3 Sensing Subsystem Samples
|
| /Zephyr-Core-3.5.0/subsys/canbus/ |
| D | Kconfig | 1 # CAN bus subsystem configuration options
6 menu "Controller Area Network (CAN) bus subsystem"
|
| /Zephyr-Core-3.5.0/subsys/sensing/sensor/phy_3d_sensor/ |
| D | Kconfig | 5 bool "sensing subsystem physical 3d sensors(accel, gyro, mag)"
9 Enable sensing subsystem physical 3d sensors(accel, gyro, mag).
|
| /Zephyr-Core-3.5.0/include/zephyr/sensing/ |
| D | sensing.h | 12 * @defgroup sensing_api Sensing Subsystem API
25 * @brief Sensing Subsystem API
77 * @brief Sensing subsystem sensor state.
86 * @brief Sensing subsystem sensor config attribute
98 * @brief Define Sensing subsystem sensor handle
142 * @brief Sensing subsystem event callback list
150 * @brief Sensing subsystem sensor configure, including interval, sensitivity, latency
231 * @brief Set current config items to Sensing subsystem.
246 * @brief Get current config items from Sensing subsystem.
|
| /Zephyr-Core-3.5.0/include/zephyr/sd/ |
| D | sd.h | 9 * @brief Public API for SD subsystem
24 * @brief card status. Used interally by subsystem.
33 * @brief card type. Used interally by subsystem.
46 * This structure is used by the subsystem to track an individual SD
75 * Initializes an SD device to use with the subsystem. After this call,
|
| /Zephyr-Core-3.5.0/subsys/debug/coredump/ |
| D | Kconfig | 17 bool "Use Logging subsystem for coredump"
20 Core dump is done via logging subsystem.
39 bool "Backend subsystem for coredump defined out of tree"
|
| /Zephyr-Core-3.5.0/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig | 6 menu "Host command handler subsystem"
9 bool "Support Embedded Controller host command handler subsystem"
80 bool "Initialize the host command subsystem automacitlly"
83 Automatically initialize the host command subsystem with the chosen backend.
|
| /Zephyr-Core-3.5.0/drivers/disk/ |
| D | Kconfig.mmc | 26 bool "MMC access via SD subsystem"
31 Enable MMC access via SD subsystem.
|
| /Zephyr-Core-3.5.0/doc/services/pm/ |
| D | system.rst | 8 Subsystem can put an idle system in one of the supported power states, based
37 The power management subsystem contains a set of states based on
47 The power management subsystem supports the following power management policies:
52 The policy manager is responsible for informing the power subsystem which
91 The power management subsystem allows different Zephyr components and
|
| D | device.rst | 11 advantage of the device power management subsystem.
47 subsystem will suspend devices before changing state. The subsystem takes care
84 The power management subsystem defines device states in
87 state is tracked by the subsystem, it is the responsibility of each device driver
120 This is entirely done by the power management subsystem. Instead, drivers are
134 driver-specific state which is required by the power management subsystem.
193 subsystem can suspend devices, as described in :ref:`pm-device-system-pm`. This
245 subsystem ensures that a domain is resumed before and suspended after devices
|
| /Zephyr-Core-3.5.0/subsys/sensing/ |
| D | Kconfig | 5 bool "Sensing Subsystem"
9 Enable Sensing Subsystem.
|
| /Zephyr-Core-3.5.0/doc/connectivity/usb/pd/ |
| D | ucds.rst | 55 A user defined structure is defined and later registered with the subsystem and can
64 These callbacks are used by the subsystem to set or get application specific data:
72 This callback is used by the subsystem to query if a certain action can be taken:
80 This callback is used by the subsystem to notify the application of an event:
104 Start the USB-C subsystem:
145 A user defined structure is defined and later registered with the subsystem and can
154 These callbacks are used by the subsystem to set or get application specific data:
162 This callback is used by the subsystem to query if a certain action can be taken:
170 This callback is used by the subsystem to notify the application of an event:
194 Start the USB-C subsystem:
|
| /Zephyr-Core-3.5.0/doc/develop/getting_started/ |
| D | installation_win.rst | 8 Windows 10 WSL (Windows Subsystem for Linux)
21 #. `Install the Windows Subsystem for Linux (WSL)`_.
35 .. _Install the Windows Subsystem for Linux (WSL): https://msdn.microsoft.com/en-us/commandline/wsl…
|
| /Zephyr-Core-3.5.0/subsys/settings/ |
| D | Kconfig | 7 The settings subsystem allows its users to serialize and
40 Storage back-end to be used by the settings subsystem.
100 int "Number of flash areas used by the settings subsystem"
108 hex "FCB magic for the settings subsystem"
|
| /Zephyr-Core-3.5.0/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig | 6 # subsystem and provides Kconfig options to control aspects of
19 Stack size of the MCUmgr for transport subsystem work queue.
25 Scheduling priority of the MCUmgr transport subsystem work queue.
|
| /Zephyr-Core-3.5.0/doc/services/retention/ |
| D | blinfo.rst | 6 The bootloader information (abbreviated to blinfo) subsystem is an extension of
15 To use the bootloader information subsystem, a retention area needs to be
71 using retention/blinfo subsystem
77 bootloader information subsystem to function:
84 The following include is needed to use the bootloader information subsystem:
|
| /Zephyr-Core-3.5.0/doc/services/storage/disk/ |
| D | access.rst | 26 SD Memory Card subsystem
30 subsystem. This subsystem can be used transparently via the disk driver API,
31 but also supports direct block level access to cards. The SDMMC subsystem
72 MMC in zephyr is implemented using the SD subsystem because the MMC bus
|
| /Zephyr-Core-3.5.0/subsys/console/ |
| D | Kconfig | 5 bool "Console subsystem/support routines"
7 Console subsystem and helper functions
|
12345678910>>...17
