Searched refs:cases (Results 101 – 125 of 248) sorted by relevance
12345678910
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-syntax.rst | 110 vendor. In these cases, there is no vendor prefix. One example is the
384 For example, this feature is not meant for cases like naming a property
429 Generally speaking, you should reserve this feature for cases where the
746 In some cases, you may want to include some property definitions from a file,
|
| /Zephyr-latest/doc/project/ |
| D | dev_env_and_tools.rst | 139 Developers and contributors should always seek review, however there are cases
228 cases include constructs like:
241 Maintainers can override the -1 in cases where the CI infrastructure
|
| D | project_roles.rst | 101 be addressed by the original submitter. In cases where the changes requested do
103 of the project or in cases of disagreement, it is the responsibility of the
376 organisation. In such cases, the minimum review period of at least 2 days
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.6.rst | 163 * Imported TinyCrypt test cases for CTR, ECC DSA and ECC DH algorithm.
193 * ``ZEP-614`` - Port TinyCrypt 2.0 test cases to Zephyr
302 * ``ZEP-961`` - samples: other cases cannot execute after run aon_counter case
|
| D | migration-guide-4.1.rst | 88 a reasonable compromise between RAM consumption and most common use cases.
267 In most cases, removing the category prefix is enough: ``VIDEO_CID_CAMERA_GAIN`` becomes
|
| /Zephyr-latest/scripts/ci/es_upload/ |
| D | README.md | 67 ## Index map examples and use cases
|
| /Zephyr-latest/scripts/ci/ |
| D | pylintrc | 52 # cases. f-strings would be nicer too, and it's easier to convert from format()
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_cli.rst | 86 Note that the BLOB Transfer Client only moves forward with the transfer in following cases:
|
| D | core.rst | 81 processed. Exceptions are made in certain cases as described below.
|
| /Zephyr-latest/dts/arm/st/wb0/ |
| D | stm32wb0.dtsi | 19 * between WB05/09 and WB06/07. In these cases, if all the registers fit
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 209 hardware. In many cases, a simple upstream build from source or a
210 copy from a friendly Linux distribution will work. In some cases it
|
| /Zephyr-latest/doc/kernel/services/ |
| D | interrupts.rst | 54 Many kernel APIs can be used only by threads, and not by ISRs. In cases
170 for certain low-latency use-cases.
172 The kernel addresses such use-cases by allowing interrupts with critical
289 known at build time, in some cases this may not be acceptable. It is also
313 for some low-latency use-cases. Specifically:
|
| /Zephyr-latest/drivers/usb/device/ |
| D | Kconfig | 68 In specific cases, this check might provide wrong verdict and should
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig | 132 Asynchronous UART API. It can be used in cases where received data processing
|
| /Zephyr-latest/samples/sensor/bme280/ |
| D | README.rst | 164 That the driver logs include a line saying ``BME280_I2C OK`` in both cases, but
|
| /Zephyr-latest/cmake/linker_script/arm/ |
| D | linker.cmake | 12 # Note, the `+ 0` in formulas below avoids errors in cases where a Kconfig
|
| /Zephyr-latest/doc/develop/test/ |
| D | coverage.rst | 37 cases which consume more RAM will crash when coverage is enabled.
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 6 In some cases it is desirable to leverage existing, external source code in
163 and accepted by the Technical Steering Committee (TSC) and, in some cases, by
|
| /Zephyr-latest/doc/develop/api/ |
| D | api_lifecycle.rst | 95 - Test cases for the new API with 100% coverage
123 its life-cycle. There are however cases where fulfilling this objective prevents
|
| /Zephyr-latest/boards/infineon/cyw920829m2evk_02/doc/ |
| D | index.rst | 6 … provides enough link budget for the entire spectrum of Bluetooth® LE use cases including industri…
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 196 (either missing, or just undocumented/unimplemented). In those cases
250 In those cases where a single set of IPIs is not sufficient to generate a valid
253 soon. However, for cases where neither the approximation nor the delay are
|
| /Zephyr-latest/doc/develop/optimizations/ |
| D | tools.rst | 41 You can have multiple cases of the same function, and the No paths category
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 210 devicetree. In some cases it's necessary to use a non-zero flag value
|
| /Zephyr-latest/boards/we/orthosie1ev/doc/ |
| D | index.rst | 18 but it also facilitates a variety of use-cases based on dual connectivity.
|
| /Zephyr-latest/doc/services/tfm/ |
| D | build.rst | 8 of TF-M's build system is required in most cases, and the following will
|
12345678910
