Searched refs:either (Results 301 – 325 of 370) sorted by relevance
1...<<1112131415
/Zephyr-latest/doc/build/dts/ |
D | phandles.rst | 29 - ``/node-2`` as either ``&lbl_b`` or ``&lbl_c``
|
D | troubleshooting.rst | 348 If the build fails to :ref:`dts-find-binding` for a node, then either the
|
D | api-usage.rst | 182 as shown above. It will expand to either 0 or 1 depending on if the property
|
D | intro-syntax-structure.rst | 283 A node is considered enabled if its status property is either ``"okay"`` or
|
/Zephyr-latest/boards/ezurio/bl5340_dvk/doc/ |
D | index.rst | 208 using either Zephyr or `Trusted Firmware M`_ (TF-M). Non-Secure
|
/Zephyr-latest/doc/kernel/services/threads/ |
D | workqueue.rst | 24 thread is configurable, allowing it to be either cooperative or preemptive 226 thread, initializing the :c:struct:`k_work_q`, either zeroing its
|
/Zephyr-latest/doc/develop/west/ |
D | manifest.rst | 1155 it's not passed to ``git submodule`` commands either. The ``name`` key 1230 other manifest files in your :file:`west.yml`. This key can be either a 1309 - name: p3 # Nothing is imported from p3 either. 1311 It's an error to set ``import`` to either ``true`` or ``false`` inside 2215 The ``--validate`` action either succeeds if the current manifest file is valid,
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | access.rst | 32 Mesh models have several parameters that can be configured either through
|
/Zephyr-latest/boards/st/steval_stwinbx1/doc/ |
D | index.rst | 20 sensor data through either the built-in RS485 transceiver, BLE, Wi-Fi, and
|
/Zephyr-latest/boards/st/sensortile_box_pro/doc/ |
D | index.rst | 20 sensor data through either the BLE or USB protocols to a host application running
|
/Zephyr-latest/modules/trusted-firmware-m/ |
D | CMakeLists.txt | 42 # for either the build or the boot to succeed.
|
/Zephyr-latest/doc/contribute/coding_guidelines/ |
D | index.rst | 696 … - A default label shall appear as either the first or the last switch label of a switch statement 724 - Functions shall not call themselves, either directly or indirectly 823 - The #include directive shall be followed by either a <filename> or "filename" sequence 970 …- The pointer arguments to the Standard Library function memcmp shall point to either a pointer t…
|
/Zephyr-latest/samples/tfm_integration/psa_crypto/ |
D | README.rst | 22 The sample prints test info to the console either as a single-thread or
|
/Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/doc/ |
D | index.rst | 211 You can either debug a running image that was flashed onto the device in User
|
/Zephyr-latest/doc/contribute/ |
D | contributor_expectations.rst | 292 expected to block the PR from being merged either by not
|
/Zephyr-latest/doc/services/smf/ |
D | index.rst | 372 call either :c:func:`smf_set_state` or :c:func:`smf_set_handled`.
|
/Zephyr-latest/boards/nordic/nrf9160dk/doc/ |
D | index.rst | 154 image. The Secure image can be built using either Zephyr or
|
/Zephyr-latest/arch/arm/core/cortex_m/ |
D | Kconfig | 398 # Implement the null pointer detection using either the Data Watchpoint and
|
/Zephyr-latest/boards/arm/mps2/doc/ |
D | mps2_an521.rst | 397 firmware image. The Secure image can be built using either Zephyr
|
/Zephyr-latest/boards/phytec/reel_board/doc/ |
D | index.rst | 334 reel board can be flashed and debugged, powered either from battery or USB.
|
/Zephyr-latest/dts/arm/nxp/ |
D | nxp_rt7xx_cm33_cpu0.dtsi | 75 * the reg properties of either sram0 or sram_code nodes to change the balance
|
/Zephyr-latest/doc/build/dts/api/ |
D | api.rst | 348 These conveniences may be used for nodes which describe either SPI controllers
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
D | gap.rst | 113 :code:`bt adv-create` command. Parameters for the advertiser can be passed either at the creation of
|
/Zephyr-latest/doc/develop/tools/ |
D | coccinelle.rst | 333 the script. It can be either ``High``, ``Moderate`` or ``Low`` depending
|
/Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
D | main.rst | 64 …Typically, iface state and IP assignment are updated either by the iface's :ref:`L2 implementation…
|
1...<<1112131415