Lines Matching +full:a +full:- +full:rx +full:- +full:clock +full:- +full:source

7 source code. Whether to use devicetree or Kconfig for a particular purpose can
12 * Use devicetree to describe **hardware** and its **boot-time configuration**.
13   Examples include peripherals on a board, boot-time clock frequencies,
22 For example, consider a board containing a SoC with 2 UART, or serial port,
29 * Additionally, the UART **boot-time configuration** is also described with
30   devicetree. This could include configuration such as the RX IRQ line's
32   their boot-time configuration is described in devicetree.
35   remove the driver source code from the build using Kconfig, even though the
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
46   radio, such as selecting a BLE or 802.15.4 protocol stack.
48 As another example, Kconfig options that formerly enabled a particular
49 instance of a driver (that is itself enabled by Kconfig) have been
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
63 * Devicetree's ``chosen`` keyword, which allows the user to select a specific
64   instance of a hardware device to be used for a particular purpose. An example
65   of this is selecting a particular UART for use as the system's console.