Home
last modified time | relevance | path

Searched refs:which (Results 1 – 25 of 1077) sorted by relevance

12345678910>>...44

/Zephyr-Core-3.5.0/samples/tfm_integration/tfm_psa_test/
DREADME.rst71 [Check 1] Call get API for UID 6 which is not set
72 [Check 2] Call get_info API for UID 6 which is not set
73 [Check 3] Call remove API for UID 6 which is not set
74 [Check 4] Call get API for UID 6 which is removed
75 [Check 5] Call get_info API for UID 6 which is removed
76 [Check 6] Call remove API for UID 6 which is removed
83 [Check 1] Call get API for UID 6 which is not set
84 [Check 2] Call get_info API for UID 6 which is not set
85 [Check 3] Call remove API for UID 6 which is not set
86 [Check 4] Call get API for UID 6 which is removed
[all …]
/Zephyr-Core-3.5.0/samples/kernel/condition_variables/simple/
DREADME.rst78 [thread zephyr_app_main] done is 0 which is < 20 so waiting on cond
141 [thread zephyr_app_main] done is 1 which is < 20 so waiting on cond
144 [thread zephyr_app_main] done is 2 which is < 20 so waiting on cond
147 [thread zephyr_app_main] done is 3 which is < 20 so waiting on cond
150 [thread zephyr_app_main] done is 4 which is < 20 so waiting on cond
153 [thread zephyr_app_main] done is 5 which is < 20 so waiting on cond
156 [thread zephyr_app_main] done is 6 which is < 20 so waiting on cond
159 [thread zephyr_app_main] done is 7 which is < 20 so waiting on cond
162 [thread zephyr_app_main] done is 8 which is < 20 so waiting on cond
165 [thread zephyr_app_main] done is 9 which is < 20 so waiting on cond
[all …]
/Zephyr-Core-3.5.0/drivers/interrupt_controller/
DKconfig.cavs24 int "Parent interrupt number to which CAVS_0 maps"
28 int "Parent interrupt number to which CAVS_1 maps"
32 int "Parent interrupt number to which CAVS_2 maps"
36 int "Parent interrupt number to which CAVS_3 maps"
/Zephyr-Core-3.5.0/doc/services/device_mgmt/
Dmcumgr_handlers.rst9 MCUmgr functions by having group handlers which identify a group of functions relating to a
10 specific management area, which is addressed with a 16-bit identification value,
12 corresponding group ID values. The group ID is included in SMP headers to identify which
13 group a command belongs to, there is also an 8-bit command ID which identifies the function of
42 The purpose of the header file is to provide defines which can be used by the MCUmgr handler
51 responses (which have unique error codes per group as opposed to the legacy SMP version 1 error
55 :c:enum:`MGMT_GROUP_ID_PERUSER`, which is the start group ID for user-defined groups, note that
62 The purpose of the header file is to provide defines which can be used by the MCUmgr handler
70 This sets up a single event which application (or module) code can register for to receive a
71 callback when the function handler is executed, which allows the flow of the handler to be
[all …]
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/ll/conn/
DREADME.txt1 Zephyr test application which uses the simulated boards test hooks.
5 testcases which are compiled with it.
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/audio/
DREADME.txt1 Zephyr test application which uses the simulated boards test hooks.
5 testcases which are compiled with it.
/Zephyr-Core-3.5.0/boards/posix/native_sim/
DKconfig22 code which was meant for the native_posix board and checks for the macro
23 CONFIG_BOARD_NATIVE_POSIX, or requires other kconfig options which depend on it.
35 interact with some other driver/device which runs at real time.
45 Transitional option which allows applications which targeted native_posix
DKconfig.board8 Will produce a console Linux process which can be executed natively
16 Will produce a console Linux process which can be executed natively
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/
Dl2cap.rst6 L2CAP layer enables connection-oriented channels which can be enable with the
11 Channels instances are represented by the :c:struct:`bt_l2cap_chan` struct which
15 In addition to that it also contains the ``recv`` callback which is called
29 the :c:struct:`bt_l2cap_server` struct which informs what ``psm`` it should
31 ``accept`` which is called to authorize incoming connection requests and
Dgatt.rst11 which takes the :c:struct:`bt_gatt_service` struct that provides the list of
45 Each attribute contain a ``uuid``, which describes their type, a ``read``
68 :c:func:`bt_gatt_discover` API which takes the
69 :c:struct:`bt_gatt_discover_params` struct which describes the type of
71 field only attributes which matches will be discovered, in contrast setting it
77 Read procedures are supported by :c:func:`bt_gatt_read` API which takes the
89 :c:func:`bt_gatt_subscribe` API which takes
/Zephyr-Core-3.5.0/drivers/serial/
DKconfig.sifive29 Port 0 RX Threshold at which the RX FIFO interrupt triggers.
36 Port 0 TX Threshold at which the TX FIFO interrupt triggers.
52 Port 1 RX Threshold at which the RX FIFO interrupt triggers.
59 Port 1 TX Threshold at which the TX FIFO interrupt triggers.
/Zephyr-Core-3.5.0/scripts/west_commands/
DREADME.txt1 This directory contains implementations for west commands which are
6 extensions in upstream west. For example, any commands which operate
22 an upstream pull request, and pull requests which break the tests
/Zephyr-Core-3.5.0/boards/posix/nrf_bsim/
DKconfig5 # The following file is normally parsed only for the ARM architecture, which is
7 # the simulated nrf5x_bsim boards, which use the POSIX architecture, the file
15 # which use BabbleSim. When that happens, we can move this to a common
DKconfig.board16 Will produce a console Linux process which can be executed natively.
32 Will produce a console Linux process which can be executed natively.
48 Will produce a console Linux process which can be executed natively.
/Zephyr-Core-3.5.0/tests/subsys/openthread/
DCMakeLists.txt1 # Boilerplate code, which pulls in the Zephyr build system.
15 # the boilerplate code, which defines the target.
/Zephyr-Core-3.5.0/include/zephyr/arch/riscv/
Dcsr.h180 #define INSERT_FIELD(val, which, fieldval) \ argument
182 ((val) & ~(which)) | ((fieldval) * ((which) & ~((which)-1))) \
/Zephyr-Core-3.5.0/drivers/rtc/
DKconfig24 This is an option which enables driver support for RTC alarms.
29 This is an option which enables driver support for the RTC
35 This is an option which enables driver support for RTC clock
/Zephyr-Core-3.5.0/soc/x86/apollo_lake/doc/
Dsupported_features.txt19 configuration. The UARTs are fed a master clock which is fed into a PLL which
22 which is:
33 the ``PCP`` to ``0x3d090240``, i.e., ``n = 288``, ``m = 15625``, which
/Zephyr-Core-3.5.0/subsys/bluetooth/controller/coex/
Dreadme.rst8 …er. Chips such as nordic nRF9160 provide a 1-wire co-existence interface, which allows the Bluetoo…
12 …interface, the coexistence ticker utilizes a single pin called BLE_GRANT, which active level (high…
22 …such as 1 for the nRF9160). state the implementation starts a ticker job, which in predefined inte…
/Zephyr-Core-3.5.0/cmake/toolchain/llvm/
Dgeneric.cmake3 # Purpose of the generic.cmake is to define a generic C compiler which can be
4 # used for devicetree pre-processing and other pre-processing tasks which must
/Zephyr-Core-3.5.0/drivers/watchdog/
DKconfig.xlnx21 API which allows determining whether the WDT initiated the last
23 which already implements this API.
/Zephyr-Core-3.5.0/drivers/counter/
DKconfig.nrfx12 # Internal flag which detects if PPI wrap feature is enabled for any instance
21 # Internal flag which detects if fixed top feature is enabled for any instance
/Zephyr-Core-3.5.0/samples/net/cellular_modem/
DREADME.rst9 This sample consists of a simple application which powers on
12 which is a publicly hosted server which runs the Python
/Zephyr-Core-3.5.0/samples/net/sockets/can/
DREADME.rst15 * Setup function which creates a CAN socket, binds it to a CAN network
18 * Receive function which starts to listen the CAN socket and prints
20 * Send function which starts to send raw CAN frames to the bus.
/Zephyr-Core-3.5.0/boards/posix/native_posix/
DKconfig.board8 Will produce a console Linux process which can be executed natively
20 Will produce a console Linux process which can be executed natively

12345678910>>...44