Searched +full:runtime +full:- +full:modifiable (Results 1 – 3 of 3) sorted by relevance
| /Zephyr-latest/dts/bindings/base/ |
| D | mutable.yaml | 2 # SPDX-License-Identifier: Apache-2.0
12 Inherit this binding for devices that are runtime-modifiable, in-place.
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.device | 1 # Copyright (c) 2014-2015 Wind River Systems, Inc.
3 # SPDX-License-Identifier: Apache-2.0
11 queried at runtime. Device dependencies are typically inferred from
20 runtime.
27 instead of Flash and are runtime modifiable in kernel mode.
74 This priority level is for end-user drivers such as sensors and display
|
| /Zephyr-latest/doc/build/dts/ |
| D | dt-vs-kconfig.rst | 12 * Use devicetree to describe **hardware** and its **boot-time configuration**.
13 Examples include peripherals on a board, boot-time clock frequencies,
29 * Additionally, the UART **boot-time configuration** is also described with
31 priority and the UART baud rate. These may be modifiable at runtime, but
32 their boot-time configuration is described in devicetree.
38 As another example, consider a device with a 2.4GHz, multi-protocol radio
43 * **Boot-time configuration** for the radio, such as TX power in dBm, should
51 :ref:`status <dt-important-props>` keyword on the corresponding hardware
56 * Because Kconfig is unable to flexibly control some instance-specific driver
61 e.g. ``zephyr,random-mac-address`` in the common Ethernet devicetree
|
