Searched full:generally (Results 1 – 25 of 118) sorted by relevance
12345
| /Zephyr-latest/soc/aspeed/ast10x0/ |
| D | Kconfig | 23 of /chosen/zephyr,sram in devicetree. The user should generally avoid
31 generally avoid changing it via menuconfig or in configuration files.
|
| /Zephyr-latest/doc/security/ |
| D | sensor-threat.rst | 65 based services, this list will generally be provided by the service
71 client must possess some kind of secret. This is generally a private
77 This secret is generally generated by the service provider, or by
90 Also, token based client authentication will generally require the
93 time to be accurate within a day or so. Token generation generally
118 devices generally have limited storage, and as such, these logs need
215 that are generally considered secure [2]_, including forward
219 communication with generally agreed secure cipher suites
248 There are several options, and the technique used is generally
254 the secret described by that certificate. Generally, these
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_cli.rst | 68 Using group addresses for transferring the BLOBs can generally increase the transfer speed, as the
70 large, segmented messages to group addresses in Bluetooth Mesh is generally less reliable than
73 losing Target nodes. Using group addresses for BLOB transfers will generally only pay off if the
97 It is generally recommended to retrieve BLOB transfer capabilities before starting a transfer. The
|
| D | cfg.rst | 9 Bluetooth Mesh nodes should generally be configured by a central network
|
| /Zephyr-latest/arch/posix/ |
| D | Linux.aarch64.cmake | 4 # distributions. Userspace is (generally) either 32-bit or 64-bit but not
|
| /Zephyr-latest/include/zephyr/drivers/timer/ |
| D | system_timer.h | 124 * Timer drivers are generally responsible for the system cycle
126 * generally called out of the architecture layer (@see
158 * fewer bits of precision in the timer is generally not expected to
|
| /Zephyr-latest/tests/kernel/timer/starve/ |
| D | README.txt | 11 This test is not run in automatic test suites because it generally takes
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | index.rst | 23 Note also that these libraries are generally unsynchronized; access to
|
| /Zephyr-latest/drivers/display/ |
| D | Kconfig.mcux_dcnano_lcdif | 33 Maintain cache coherency for LCDIF framebuffer. This is generally
|
| /Zephyr-latest/lib/utils/ |
| D | Kconfig | 41 "windows", generally for transmit to non-Zephyr contexts that
|
| /Zephyr-latest/doc/develop/api/ |
| D | terminology.rst | 138 function will return a specific error (generally ``-EWOULDBLOCK``).
161 Generally a function that is **pre-kernel-ok** checks
173 generally provide a mechanism by which operation completion is reported,
|
| /Zephyr-latest/doc/services/tfm/ |
| D | testsuites.rst | 42 to the core TF-M module(s). They should generally be run as a coherence check
|
| D | overview.rst | 41 A TF-M application will, generally, have the following three parts, from most
106 Protected Storage (PS), and generally custom secure services that you implement
199 As of TF-M 1.8.0, the following secure services are generally available (although vendor support ma…
264 Generally, you simply need to select the ``*/ns`` board target of a valid board
|
| /Zephyr-latest/boards/shields/arduino_uno_click/doc/ |
| D | index.rst | 13 In other words, the Arduino UNO click will generally be used by other
|
| /Zephyr-latest/dts/bindings/spi/ |
| D | spi-controller.yaml | 52 If unsure about the flags cell, GPIO_ACTIVE_LOW is generally a safe
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 003_rfc-proposal.md | 53 List any concerns, unknowns, and generally unresolved questions etc.
|
| /Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/ |
| D | Kconfig | 67 generally be EVENT_OVERHEAD_START_US + a small margin to cover ISOAL
|
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | CMakeLists.txt | 17 # available; generally it isn't except in SOF builds). Note that the
|
| /Zephyr-latest/doc/build/dts/ |
| D | intro-input-output.rst | 35 Generally speaking, every supported board has a :file:`BOARD.dts` file
51 and includes are generally done with ``#include <filename>`` directives, even
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i2c.rst | 21 given SoC will generally support the controller role, and some will also
|
| /Zephyr-latest/include/zephyr/misc/ |
| D | lorem_ipsum.h | 14 * N.B. These strings are generally only used for tests and samples. They are not part of any
|
| /Zephyr-latest/samples/bluetooth/mesh_demo/ |
| D | README.rst | 24 board's 5x5 LED display. It's generally recommended to use unicast
|
| /Zephyr-latest/dts/bindings/mspi/ |
| D | mspi-controller.yaml | 87 If unsure about the flags cell, GPIO_ACTIVE_LOW is generally a safe
|
| /Zephyr-latest/include/zephyr/dt-bindings/pcie/ |
| D | pcie.h | 14 * generally also require CONFIG_DYNAMIC_INTERRUPTS.
|
| /Zephyr-latest/modules/mbedtls/configs/ |
| D | config-coap.h | 80 #define MBEDTLS_PSK_MAX_LEN 16 /* 128-bits keys are generally enough */
|
12345
