Searched full:subsystem (Results 1 – 25 of 359) sorted by relevance
12345678910>>...15
| /Zephyr-Core-3.4.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.4.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.4.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.4.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.
|
| /Zephyr-Core-3.4.0/subsys/canbus/ |
| D | Kconfig | 1 # CAN bus subsystem configuration options
6 menu "Controller Area Network (CAN) bus subsystem"
|
| /Zephyr-Core-3.4.0/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig | 6 menu "Host command handler subsystem"
9 bool "Support Embedded Controller host command handler subsystem"
78 bool "Initialize the host command subsystem automacitlly"
81 Automatically initialize the host command subsystem with the chosen backend.
|
| /Zephyr-Core-3.4.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
74 * Initializes an SD device to use with the subsystem. After this call,
|
| /Zephyr-Core-3.4.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.4.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.4.0/drivers/disk/ |
| D | Kconfig.mmc | 26 bool "MMC access via SD subsystem"
31 Enable MMC access via SD subsystem.
|
| D | Kconfig.sdmmc | 30 bool "SDMMC access via SD subsystem"
35 Enable SDMMC access via SD subsystem.
|
| /Zephyr-Core-3.4.0/doc/services/device_mgmt/ |
| D | ec_host_cmd.rst | 9 communicate with a target embedded controller (EC). The EC Host command subsystem implements the
11 protocol interface supports multiple versions, but this subsystem implementation only support
16 The Host Command subsystem contains a few components:
52 initializes the host command subsystem by calling :c:func:`ec_host_cmd_init`:
|
| /Zephyr-Core-3.4.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.4.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.4.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.4.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.4.0/subsys/console/ |
| D | Kconfig | 5 bool "Console subsystem/support routines"
7 Console subsystem and helper functions
|
| /Zephyr-Core-3.4.0/samples/subsys/sip_svc/ |
| D | README.rst | 9 This sample demonstrates the usage of SiP SVC subsystem.This sample
16 * SiP SVC subsystem relies on the firmware running in EL3 layer to be in compatible
17 with protocol defined inside the SiP SVC subsystem used by the project.
|
| /Zephyr-Core-3.4.0/doc/kernel/drivers/ |
| D | index.rst | 33 interrupt management subsystem.
36 hardware clock subsystem.
39 system console subsystem.
42 for the random number generator subsystem.
113 The ``api`` struct maps generic subsystem APIs to the device-specific
121 Most drivers will be implementing a device-independent subsystem API.
125 A subsystem API definition typically looks like this:
153 A driver implementing a particular subsystem will define the real implementation
188 Some devices can be cast as an instance of a driver subsystem such as GPIO,
190 standard API. These devices combine subsystem operations with
[all …]
|
| /Zephyr-Core-3.4.0/subsys/dsp/ |
| D | Kconfig | 5 bool "DSP subsystem"
7 Include the DSP (Digital Signal Processing) subsystem as a part of the
|
| /Zephyr-Core-3.4.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
|
| /Zephyr-Core-3.4.0/include/zephyr/timing/ |
| D | timing.h | 50 * @brief Initialize the timing subsystem.
52 * Perform the necessary steps to initialize the timing subsystem.
59 * Signal to the timing subsystem that timing information
67 * Signal to the timing subsystem that timing information
|
| /Zephyr-Core-3.4.0/doc/services/ |
| D | notify.rst | 16 transactions. The subsystem wrappers are responsible for extracting
31 from a user mode thread the subsystem or driver should provide a syscall
|
| /Zephyr-Core-3.4.0/include/zephyr/net/ |
| D | net_config.h | 2 * @brief Routines for network subsystem initialization.
38 * @brief Application needs IPv6 subsystem configured and initialized.
44 * @brief Application needs IPv4 subsystem configured and initialized.
|
12345678910>>...15
