Home
last modified time | relevance | path

Searched refs:being (Results 276 – 300 of 357) sorted by relevance

1...<<1112131415

/Zephyr-latest/doc/kernel/services/smp/
Dsmp.rst328 resulting from the thread that is being switched out.
350 resulting from the thread that is being switched out in that thread's
/Zephyr-latest/doc/develop/test/
Dztest.rst285 * Test case function names should be unique within the section or component being
323 report them as being skipped. Because the test inventory and
/Zephyr-latest/doc/services/rtio/
Dindex.rst96 a cqe being pushed into the cq. The ordering of cqe may not be the same order of
/Zephyr-latest/doc/kernel/
Dtimeutil.rst144 <https://en.wikipedia.org/wiki/Coordinated_Universal_Time>`__ being the most
/Zephyr-latest/doc/kernel/services/
Dpolling.rst306 :c:func:`k_poll_signal_raise()`. But if the signal is being
/Zephyr-latest/boards/arm/v2m_musca_b1/doc/
Dindex.rst354 Applications must be converted to Intel's hex format before being flashed to a
/Zephyr-latest/doc/develop/west/
Dwest-apis.rst299 being read.
/Zephyr-latest/soc/intel/intel_adsp/ace/
Dace-link.ld585 * otherwise rimage will complain about the size being wrong (which
/Zephyr-latest/doc/connectivity/usb/device_next/
Dusb_device.rst279 Filling the TX FIFO does not mean that data is being sent to the host. And
/Zephyr-latest/doc/services/storage/settings/
Dindex.rst181 Currently settings doesn't provide scheme of being secure, and non-secure
/Zephyr-latest/doc/services/debugging/
Dcoredump.rst321 the target and is only being parsed by the target parser.
/Zephyr-latest/doc/hardware/peripherals/can/
Dcontroller.rst68 Nodes monitor the bus and notice when their transmission is being overridden and
/Zephyr-latest/doc/contribute/
Dguidelines.rst402 being changed. It can also identify the change's wider
798 such as not being able to use "View Changes" buttons except for the last
827 #. Make sure title of PR explains what is being fixed or added
/Zephyr-latest/boards/arm/v2m_musca_s1/doc/
Dindex.rst326 format before being flashed to a V2M Musca-S1. An optional bootloader can also
/Zephyr-latest/doc/hardware/peripherals/
Di3c.rst57 If this is being used, this struct needs to be initialized by calling
/Zephyr-latest/doc/develop/languages/cpp/
Dindex.rst143 because they end up being compiled in a surprisingly high number of other
/Zephyr-latest/doc/releases/
Drelease-notes-3.2.rst201 of :c:enumerator:`CAN_STATE_STOPPED` before being able to transmit and receive CAN frames.
749 * Enhanced the LPS22HH driver to support being on an I3C bus.
1437 * Issue with :c:func:`img_mgmt_dfu_stopped` being wrongly called on success
1767 - :github:`50196` - LSM6DSO interrupt handler not being called
1797 - :github:`50776` - CAN Drivers allow sending FD frames without device being set to FD mode
1823 * :github:`50654` - Some files are being ALWAYS built, without them being used
2001 * :github:`49410` - Bluetooth: Scan responses with info about periodic adv. sometimes stops being r…
2246 * :github:`47426` - ZTEST_USER tests being skipped on systems without userspace support
Drelease-notes-3.0.rst397 * Fixed DTM mode not being reset correctly with the HCI Reset command
801 * Support all syscalls being traced using the python syscall generator to
912 * :github:`42358` - net: lwm2m: client context accessed after being invalidated in lwm2m_rd_client_…
972 * :github:`41942` - k_delayable_work being used as k_work in work's handler
Drelease-notes-2.1.rst517 * :github:`20800` - Ready thread is not swapped in after being woken up in IRQ
598 * :github:`20299` - bluetooth: host: Connection not being unreferenced when using CCC match callback
738 * :github:`19284` - Service Changed indication not being sent in some cases
/Zephyr-latest/doc/services/tfm/
Doverview.rst31 build process makes a number of assumptions about how TF-M is being used, and
/Zephyr-latest/doc/connectivity/networking/api/
Dhttp_server.rst168 HTTPS services rely on TLS credentials being registered in the system.
Dnet_pkt.rst170 latter being the preferred way.
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst58 If TCP is being used, then these values need to be higher because we can queue the
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split617 When enabled, this could result in an SDU being fragmented into
1098 This will prolong the connection event to from being closed in cases
1331 been processed. The rationale for default behavior being that under
/Zephyr-latest/doc/develop/application/
Dindex.rst712 * If this is built normally without ``FILE_SUFFIX`` being defined for ``native_sim`` then
715 * If this is build normally without ``FILE_SUFFIX`` being defined for ``qemu_cortex_m3`` then
1041 support being unavailable, consult :ref:`your board's documentation <boards>`

1...<<1112131415