Searched refs:cases (Results 151 – 175 of 248) sorted by relevance
12345678910
| /Zephyr-latest/doc/services/ |
| D | formatted_output.rst | 49 family is called. However, there are cases when it is beneficial that formatting
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 59 failure, and in many cases to build several tests into the same binary.
|
| /Zephyr-latest/include/zephyr/arch/riscv/common/ |
| D | linker.ld | 72 #else /* Use Kconfig to cover the remaining cases */
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | memory_domain.rst | 161 mode. In some cases this may be unavoidable; for example some architectures do
447 In almost all cases ``K_MEM_PARTITION_P_RW_U_RW`` is the right choice.
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 88 As such can provide better integration coverage than simulation in some cases,
90 test in general not being reproducible, and in many cases failures
|
| D | arch_soc.rst | 39 a HW agnostic test platform which in some cases utilizes the host OS
269 and, in some cases, can expose host HW as emulated target peripherals.
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-3.1.rst | 81 cases other than NO_REMAP/REMAP_0)
670 certain test cases.
746 Some use cases that this work intends to enable are:
784 In some cases, this resulted in the removal of old bindings, or other
1206 …github:`43928` - pm: going to PM_STATE_SOFT_OFF in pm_policy_next_state causes assert in some cases
1269 - :github:`46157` - ACRN: some cases still failed because of the log missing
1529 * :github:`44535` - mgmt/mcumgr/lib: Incorrect use of MGMT_ERR_ENOMEM, in most cases where it is us…
1572 * :github:`44261` - twister: some changes make test cases work abnormally.
1680 * :github:`43600` - tests: mec15xxevb_assy6853: most of the test cases failed
1785 * :github:`42857` - sam_e70b_xplained: failed to run test cases tests/net/npf and tests/net/bridge
|
| D | release-notes-2.2.rst | 203 space. Older methods which had problems in some cases or on some
776 * :github:`22885` - Sanitycheck timeout all test cases on mec15xxevb_assy6853 board.
895 …`22188` - drivers: espi: xec : eSPI driver should not send VWire SUS_ACK automatically in all cases
1043 * :github:`21123` - sanitycheck halt some test cases with parallel running.
1103 * :github:`20026` - sanitycheck corrupts stty in some cases
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 36 Assertions are enabled by default when running Zephyr test cases, as
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-ctlr-arch.rst | 214 …* Note also - there are miscellaneous cases where connection termination is triggered on invalid p…
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_l2.rst | 155 employs an "inversion-of-control" pattern in such cases avoids duplication of
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | demand_paging.rst | 46 The data type will always be ``void *`` or in some cases ``uint8_t *``
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-upstream.rst | 221 You must add this prefix to property names in the following cases:
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob.rst | 153 Mode. In most cases, the transfer should be conducted in Push BLOB Transfer Mode.
|
| /Zephyr-latest/doc/develop/west/ |
| D | release-notes.rst | 231 instead of ``RuntimeError`` in some cases
381 some edge cases described in `issue #523`_.
629 part of an effort to make west generally usable for non-Zephyr use cases.
|
| D | west-apis.rst | 326 ``die()``. Two special cases of ``inf()``, ``banner()`` and ``small_banner()``,
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | tips.rst | 78 other cases where devicetree.h provides :ref:`devicetree-hw-api` for referring
143 More insidious cases with dependencies inherited from ``if`` and ``menu``
307 Rare exceptions might include cases where you're sure that the dependencies
|
| /Zephyr-latest/cmake/modules/ |
| D | boards.cmake | 154 # in the system in the following cases:
|
| /Zephyr-latest/modules/hostap/ |
| D | Kconfig | 29 # 30K is mandatory, but might need more for long duration use cases
|
| /Zephyr-latest/ |
| D | CMakeLists.txt | 39 # In some cases the "final" things are not used at all and "_prebuilt"
56 # Multiple linking stages are required in the following cases:
770 "not supported and known to break in many cases due to stack overflow or "
1780 # Note, the `+ 0` in formula below avoids errors in cases where a Kconfig
1827 # Those files can be very large in some cases, delete them as we do not need them.
|
| D | Kconfig.zephyr | 297 correctly calculated, even in cases where the location counter may
301 Note: in cases where the flash is fully used, for example application
304 In such cases this setting should be disabled.
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 501 In some cases, logs need to be redirected at the macro level. For these cases,
608 In most cases, the address space of each domain is unique, and one domain
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.fish | 88 # function similar to '__fish_use_subcommand' but with special cases
114 # function similar to '__fish_seen_subcommand_from' but with special cases
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/ |
| D | Kconfig.nrfwifi | 84 # Use a maximum that works for typical use cases and boards, each sample/app can override
623 multiple virtual interfaces. For geo-location use cases, these networks
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.df | 166 For general use cases Bluetooth Core 5.1 spec. required the value
|
12345678910
