Pantelis Antoniou | 7941b27 | 2014-07-04 19:59:20 +0300 | [diff] [blame] | 1 | Device Tree Dynamic Resolver Notes |
| 2 | ---------------------------------- |
| 3 | |
| 4 | This document describes the implementation of the in-kernel |
| 5 | Device Tree resolver, residing in drivers/of/resolver.c and is a |
| 6 | companion document to Documentation/devicetree/dt-object-internal.txt[1] |
| 7 | |
| 8 | How the resolver works |
| 9 | ---------------------- |
| 10 | |
| 11 | The resolver is given as an input an arbitrary tree compiled with the |
| 12 | proper dtc option and having a /plugin/ tag. This generates the |
| 13 | appropriate __fixups__ & __local_fixups__ nodes as described in [1]. |
| 14 | |
| 15 | In sequence the resolver works by the following steps: |
| 16 | |
| 17 | 1. Get the maximum device tree phandle value from the live tree + 1. |
| 18 | 2. Adjust all the local phandles of the tree to resolve by that amount. |
| 19 | 3. Using the __local__fixups__ node information adjust all local references |
| 20 | by the same amount. |
| 21 | 4. For each property in the __fixups__ node locate the node it references |
| 22 | in the live tree. This is the label used to tag the node. |
| 23 | 5. Retrieve the phandle of the target of the fixup. |
| 24 | 6. For each fixup in the property locate the node:property:offset location |
| 25 | and replace it with the phandle value. |