Home
last modified time | relevance | path

Searched full:concept (Results 1 – 25 of 58) sorted by relevance

123

/Zephyr-latest/tests/kernel/mem_slab/mslab_concept/
Dtestcase.yaml2 kernel.memory_slabs.concept:
/Zephyr-latest/tests/kernel/tickless/tickless_concept/
Dtestcase.yaml2 kernel.tickless.concept:
/Zephyr-latest/doc/hardware/peripherals/
Dflash.rst9 **Flash offset concept**
/Zephyr-latest/modules/trusted-firmware-m/psa/
DGNUARM.cmake8 # The INHERIT concept was introduced in
/Zephyr-latest/samples/subsys/llext/modules/
Dprj.conf6 # as-is even if Zephyr has a completely different concept for "modules".
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst35 * Mayfly concept based deferred ISR executions
136 - LLL is vendor ISR, ULL is Mayfly ISR concept, Host is kernel thread.
188 * Naming concept: lr _<...> => local request machine
194 * Naming concept: rr_<...> => remote request machine
200 * Naming concept: lp_<...> => local initiated procedure, rp_<...> => remote initiated procedure
/Zephyr-latest/samples/net/sockets/echo_service/
DREADME.rst14 The socket service is a concept where many blocking sockets can be listened by
/Zephyr-latest/soc/common/riscv-privileged/
Dvector.S49 * CLIC vectored mode has a similar concept to CLINT vectored mode,
/Zephyr-latest/include/zephyr/sensing/
Dsensing_datatypes.h43 * This concept is borrowed from CHRE:
/Zephyr-latest/doc/services/net_buf/
Dindex.rst14 Network buffers are a core concept of how the networking stack
/Zephyr-latest/doc/services/llext/
Dload.rst32 in languages such as C++ that provide the concept of object constructors. The
/Zephyr-latest/subsys/net/l2/ethernet/gptp/
DKconfig118 The port concept is the same thing as network interface.
/Zephyr-latest/include/zephyr/net/
Dnet_time.h34 * @brief Any occurrence of net_time_t specifies a concept of nanosecond
Dieee802154.h129 * concept in Linux and Zephyr's L3. It is not a concept from the IEEE 802.15.4
/Zephyr-latest/subsys/net/lib/ptp/
DKconfig86 The port concept is the same thing as network interface.
/Zephyr-latest/tests/drivers/can/host/
DREADME.rst32 around the concept of a configuration "context. The configuration context for this test suite can be
/Zephyr-latest/doc/build/dts/
Dphandles.rst6 The devicetree concept of a *phandle* is very similar to pointers in
192 enforced. To answer this question, we'll need to introduce a concept called
/Zephyr-latest/boards/mediatek/
Dindex.rst26 series in concept (with the notable difference that these are all
/Zephyr-latest/doc/
Dglossary.rst154 and :term:`CPU cluster`. Common uses of the variant concept include
/Zephyr-latest/doc/hardware/emulator/
Dbus_emulators.rst24 Concept section in External Bus and Bus Connected Peripherals Emulators
/Zephyr-latest/lib/posix/options/
Dsemaphore.c129 * Zephyr has no concept of process, so only thread shared in sem_init()
/Zephyr-latest/boards/renesas/ek_ra6m1/doc/
Dindex.rst12 and is supported by an open and flexible ecosystem concept—the Flexible Software
/Zephyr-latest/cmake/modules/
Dkernel.cmake90 # CMake's 'project' concept has proven to not be very useful for Zephyr
/Zephyr-latest/doc/services/sensing/
Dindex.rst215 This concept is referred from `CHRE Sensor API <https://github.com/zephyrproject-rtos/
/Zephyr-latest/boards/u-blox/ubx_evkannab1/doc/
Dindex.rst102 The reason for this is the u-blox module family concept where different

123