Searched refs:above (Results 301 – 325 of 381) sorted by relevance
1...<<111213141516
/Zephyr-latest/doc/hardware/arch/ |
D | arm_cortex_m.rst | 255 One exception to the above rules is when Zephyr applications support Zero Latency Interrupts 320 As described above, in Mainline Cortex-M applications, the Zephyr kernel reserves 449 The above MPU regions are defined in :file:`arch/arm/core/mpu/arm_mpu_regions.c`.
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 390 You need to change text in square brackets (``[like this]``) above to 745 it after completing the steps above on scan service website. Any issues 871 and use the same process described above to work on this new topic branch. 917 to fix the issues and amend your commits by rebasing as described above.
|
D | bin_blobs.rst | 122 fits in one of the above types.
|
/Zephyr-latest/doc/security/ |
D | sensor-threat.rst | 334 In addition to the above, network connected devices generally will need 338 requirements described above.
|
/Zephyr-latest/doc/develop/test/ |
D | ztest.rst | 148 In this example, the above tests should be marked as failed and skipped respectively. Instead, 239 In the command line above ``tests/foo/bar`` is the path to your test application and
|
/Zephyr-latest/boards/ti/cc3235sf_launchxl/doc/ |
D | index.rst | 161 Once the above prerequisites are met, applications for the ``_cc3235sf_launchxl``
|
/Zephyr-latest/cmake/modules/ |
D | yaml.cmake | 22 # All of above can be combined, for example like:
|
D | dts.cmake | 99 # Variables set by this module and not mentioned above are for internal
|
D | kconfig.cmake | 280 # assigned above.
|
/Zephyr-latest/subsys/bluetooth/mesh/ |
D | Kconfig | 665 segments of a segmented message is above this threshold, the stack 706 size of segments in a segmented message is above the 970 possible and will be clamped to the max possible if set above. 998 possible and will be clamped to the max possible if set above. 1569 In order to fulfill the above requirement, even if the node might
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | index.rst | 164 Although the diagram above may appear to suggest that both **Ready** and 454 The following code has the same effect as the code segment above.
|
D | workqueue.rst | 447 causing the application to fail. Where the idiom above is required a 453 once the handler finishes. If it is not, the code above must take other steps
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | lwm2m.rst | 339 ``Device`` object with some data and the callback we defined above: 674 Sending of data in the table above refers to calling :c:func:`lwm2m_send_cb` or by writing into one…
|
/Zephyr-latest/soc/intel/intel_adsp/ace/ |
D | ace-link.ld | 318 * So we can't keep this in .xtensa_vector_code above. Though we try to
|
/Zephyr-latest/doc/releases/ |
D | migration-guide-4.1.rst | 208 /* Pin selection(s) using bindings included above */
|
/Zephyr-latest/doc/develop/getting_started/ |
D | installation_linux.rst | 306 As already noted above, the SDK also includes prebuilt host tools. To use the
|
/Zephyr-latest/boards/acrn/acrn/doc/ |
D | index.rst | 261 configured as ``<vm id="0">`` above). This minimal configuration will
|
/Zephyr-latest/ |
D | LICENSE | 134 Notwithstanding the above, nothing herein shall supersede or modify
|
/Zephyr-latest/boards/microchip/mec172xevb_assy6906/doc/ |
D | index.rst | 229 The jumper configuration explained above covers the base board. The ASSY
|
/Zephyr-latest/doc/contribute/documentation/ |
D | guidelines.rst | 48 line should align with the text of the line above. 335 link above. 1192 A flag to include a search box right above the listing. The search box allows users to filter
|
/Zephyr-latest/doc/kernel/usermode/ |
D | kernelobjects.rst | 65 Kernel objects that are found but do not meet the above conditions will not be
|
/Zephyr-latest/doc/develop/languages/cpp/ |
D | index.rst | 229 required by C++20 and above which perceive such braces as mixing bare
|
/Zephyr-latest/doc/develop/west/ |
D | built-in.rst | 72 As above, ``--mf`` defaults to ``west.yml``.
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | i3c.rst | 321 Note that, with either methods mentioned above, the devicetree node of
|
/Zephyr-latest/boards/arm/v2m_musca_s1/doc/ |
D | index.rst | 351 picture above. The 3 LEDs should be lit (PWR, ON and 5VON) and you should see a
|
1...<<111213141516