Searched full:simplified (Results 1 – 25 of 39) sorted by relevance
12
23 among other things defines simplified UART interface
28 by the firmware through a simplified API similar to a "normal"
22 bool "Simplified debug tracing of events"
11 like in the following simplified example:
28 Here is a simplified view of the process:
12 This driver offers a simplified operation in order to integrate with Zephyr
33 * Add extension macro for simplified creation of
82 can be simplified.
9 This sample application performs a simplified network layer forwarding function
34 happens during the execution step. The below picture presents a simplified overview of the
553 Zephyr also has defined extensions to FFF for simplified declarations of fake functions.
169 936 - Simplified Chinese (DBCS)
179 * x2APIC mode is greatly simplified: one write, no delivery status. in z_loapic_ipi()
36 * implement a simplified masking architecture. Xtensa INTENABLE
91 written to flash has to have proper header prepended. The process is simplified
26 :alt: A simplified view of how Connection Manager integrates with Zephyr and the application.29 A simplified view of how Connection Manager integrates with Zephyr and the application.
52 See :ref:`here <conn_mgr_integration_diagram_simple>` for a simplified version.
326 * The code below can be simplified after updating TF-M version used in Zephyr to 1.5.0 in otPlatCryptoAesEncrypt()
273 simplified version of that potential operation chain.
57 * x86: Optimized and simplified IRQ and exception stubs.
140 * IPSP net-app support: a simplified networking API reducing duplication
198 * Simplified dummy thread implementation and properly name idle threads714 * The documentation on driver-specific APIs has been simplified.
529 * REMARK: This routine could be simplified if the settings_handler names
992 simpified||simplified
555 provides a simplified overview of how ``group-filter`` interacts with the917 This section provides a simplified description of how the ``manifest:
