Searched refs:often (Results 1 – 25 of 78) sorted by relevance
1234
| /Zephyr-latest/samples/net/stats/ |
| D | Kconfig | 9 int "How often to print statistics (in seconds)"
|
| /Zephyr-latest/doc/services/ |
| D | notify.rst | 6 Zephyr APIs often include :ref:`api_term_async` functions where an
9 often a good method, but some application architectures may be more
|
| /Zephyr-latest/drivers/misc/coresight/ |
| D | Kconfig | 36 Period (in milliseconds) how often it is checked if any dropped messages
56 Determines how often attempt to dump the data is performed.
63 there is still a pending ETR data. This option specifies how often
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | auxdisplay.rst | 12 graphical output to displays (and most often monochrome), the most
|
| D | haptics.rst | 19 Additionally, haptic driver devices often offer controls for adjusting and
|
| D | fuel_gauge.rst | 33 specific payload will do a battery cutoff. This battery cutoff is often referred to as ship, shelf,
|
| /Zephyr-latest/cmake/usage/ |
| D | usage.cmake | 44 message(" 1: warnings which may be relevant and do not occur too often")
45 message(" 2: warnings which occur quite often but may still be relevant")
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | unsigned_lesser_than_zero.cocci | 2 /// comparisons 'unsigned (<|<=) 0' often indicates a bug,
|
| /Zephyr-latest/subsys/emul/ |
| D | Kconfig | 18 Emulators often implement special features for testing. For example
|
| /Zephyr-latest/cmake/modules/ |
| D | python.cmake | 8 # to the current code page if not connected to a terminal, which is often
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | index.rst | 11 Configuration options (often called *symbols*) are defined in :file:`Kconfig`
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | power_management.rst | 4 Power management of sensors is often a non-trivial task as sensors may have multiple power states
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 56 Multiple SoCs can even be defined in one directory. In Zephyr, SoCs are often
85 configuration macros for the SoC. The :file:`soc.h` will often be included in
196 CPU cluster will often have its own :file:`.dtsi` file.
256 The :file:`Kconfig` will often indicate given hardware support using a setting
|
| /Zephyr-latest/doc/develop/manifest/external/ |
| D | cannectivity.rst | 12 The firmware implements the Geschwister Schneider USB/CAN device protocol (often referred to as
|
| /Zephyr-latest/samples/drivers/can/babbling/ |
| D | README.rst | 11 transmitting CAN frames with identical - often high - priority. This constant babbling blocks CAN
|
| /Zephyr-latest/samples/net/sockets/http_server/ |
| D | Kconfig | 69 This interval controls how often the net stats data shown on the web page
|
| /Zephyr-latest/boards/arduino/opta/ |
| D | arduino_opta-common.dtsi | 99 /* The RS485 is often used with the ModBus protocol. */
|
| /Zephyr-latest/ |
| D | .gitlint | 58 # This is useful for when developers often erroneously edit certain files or git submodules.
|
| /Zephyr-latest/samples/sensor/ccs811/ |
| D | README.rst | 11 for indoor air quality measurements. VOCs are often categorized as
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_timeout.rst | 18 Timeout processing is often affected by latency, so that the time at which the
|
| /Zephyr-latest/samples/boards/espressif/light_sleep/ |
| D | README.rst | 26 button attached to GPIO0, often labelled BOOT. If the board does not have such
|
| /Zephyr-latest/samples/bluetooth/bap_broadcast_sink/ |
| D | Kconfig | 87 Determines how often information about received data is logged.
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 11 this. Now, code running on small microcontrollers often has access to
13 vulnerabilities). Given the volume they are often deployed at,
258 Because security issues are often sensitive, this issue tracking
267 because security considerations are often external to the Zephyr
|
| /Zephyr-latest/samples/tfm_integration/psa_protected_storage/ |
| D | README.rst | 13 The encryption key is derived from the Hardware Unique Key (HUK), which is often set via device
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 28 Determines how often a report about dropped messages is printed. Given
|
1234
