Devicetree
The devicetree (device tree, DT (DTS/DTB)) is a data structure which holds information about all components present on a device. This data is structured in nested nodes with key/value property pairs for configuration.
In simpler terms - a devicetree tells the kernel (or another DT-compatible piece of software/firmware like a bootloader) where each component is in register space/on an I2C or similar bus, and what settings to use to set it up. It is the basic mechanism for discovering components on embedded platforms, including ARM.
Devicetrees are validated using devicetree schema, which is described by bindings; see /Bindings for more information.
History
The initial version of the devicetree standard was developed as part of the OpenFirmware initiative; from this standard, the Flattened Device Tree (FDT) emerged and was adopted by the Linux kernel for PowerPC platforms. Around 2009, discussions began to include FDT support for ARM[1]. It was eventually added and first device trees began to appear in 2011[2], although the format didn't see wider usage (especially in vendor kernels) until around 2013/2014.
Nowadays, the devicetree standard is managed by devicetree.org; they maintain the latest version of the Devicetree Specification and the related set of core DT schema.
Before the introduction of devicetrees, ARM kernels used board files. These were C files stored in arch/arm/mach-* which served a similar purpose to devicetrees - they contained structures for defining component configuration ("platform data"). Unlike device trees however, they could also define C functions, since they were regular C sources compiled into the kernel. Board files technically still exist (citation needed?), but are no longer in wide use.
Device Tree Source (DTS) and Device Tree Blob (DTB)
Devicetrees are written in a plaintext format known as the Device Tree Source (DTS) format. The DTS is later compiled into a Device Tree Blob (DTB); in this form, it can be loaded by software/firmware.
The dtc tool handles compiling DTS files into DTBs, as well as decompiling DTBs back into DTS.
Device Tree Source basics
Here is a very simple DTS file to explain the basics of what you might see in a device tree source file:
/dts-v1/;
/ {
#address-cells = <1>;
#size-cells = <1>;
my_node: node1@1000 {
compatible = "vendor,foo";
reg = <0x1000 0x54>;
vendor,bar-factor = <0x2a>;
};
node2@2000 {
compatible = "vendor,bar";
reg = <0x2000 0xa4>;
vendor,baz-companion = <&my_node>;
};
i2c-controller@3000 {
compatible = "vendor,foobar-i2c";
reg = <0x3000 0x800>;
#address-cells = <1>;
#size-cells = <0>;
sensor@10 {
compatible = "vendor,baz-sensor";
reg = <0x10>;
};
};
};
In this example, we define an empty DTS; in its root node (/), we place three nodes: a node named "node1" with a label "my_node" at address 0x1000, a node named "node2" at address 0x2000, and a node named "i2c-controller" at address 0x3000.
A node contains:
- A
compatiblevalue (here"vendor,foo"). This specifies what kind of component it is; Linux uses this information to load the correct driver. - A
regvalue. In this case, the first parameter is the base address in memory (0x1000), and the second is the size it occupies (0x54). The amount of cells for the address and size are specified by the#address-cellsand#size-cellsproperties of the root node, respectively.- You might notice that the i2c-controller node defines another set of these
#address-cellsand#size-cellsproperties - this is because I2C devices contain their own subdevices with addresses ranging from 0x08 to 0x7f (todo verify), and they do not use a size.
- You might notice that the i2c-controller node defines another set of these
- A custom vendor-specific property,
vendor,bar-factor, which takes a number.
On node 2 there is also a property, vendor,baz-companion, which takes a pointer to another node - here the one we labeled "my_node".
Verifying DTS files
The Linux kernel has tools for making sure that device tree sources (DTS) use the bindings correctly. These are useful when writing device sources; getting the DT checks to pass is also mandatory for upstream inclusion of a DTS.
To verify all DTS files built with the selected defconfig options, run:
$ make dtbs_check
To verify a specific DTS, build the DTB target directly and provide the CHECK_DTBS=y option:
$ make CHECK_DTBS=y qcom/sm8450-hdk.dtb
You can also test a DTS against a specific subset of bindings by providing the DT_SCHEMA_FILES variable as mentioned in the previous section:
$ make CHECK_DTBS=y DT_SCHEMA_FILES=trivial-devices.yaml qcom/sm8450-hdk.dtb
See also
- From Linux kernel documentation:
- On elinux.org:
References
todo enable refs extension
[1] https://www.mail-archive.com/[email protected]/msg01721.html [2] https://github.com/torvalds/linux/commit/b85a3ef4ac65169b65fd2fe9bec7912bbf475ba4