diff options
| author | Simon Glass <sjg@chromium.org> | 2017-01-17 16:52:55 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2017-02-08 06:12:14 -0700 |
| commit | e160f7d430f163bc42757aff3bf2bcac0a459f02 (patch) | |
| tree | ce006f94b4a52f6fff567eacd86922c3be6df706 /doc/driver-model/README.txt | |
| parent | 8aa41363ebf46b9ff63b311bd2aa793c67a49def (diff) | |
dm: core: Replace of_offset with accessor
At present devices use a simple integer offset to record the device tree
node associated with the device. In preparation for supporting a live
device tree, which uses a node pointer instead, refactor existing code to
access this field through an inline function.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/driver-model/README.txt')
| -rw-r--r-- | doc/driver-model/README.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/driver-model/README.txt b/doc/driver-model/README.txt index 1b5ccec4b2e..fea324e25ee 100644 --- a/doc/driver-model/README.txt +++ b/doc/driver-model/README.txt @@ -684,7 +684,7 @@ steps (see device_probe()): g. If the driver provides an ofdata_to_platdata() method, then this is called to convert the device tree data into platform data. This should - do various calls like fdtdec_get_int(gd->fdt_blob, dev->of_offset, ...) + do various calls like fdtdec_get_int(gd->fdt_blob, dev_of_offset(dev), ...) to access the node and store the resulting information into dev->platdata. After this point, the device works the same way whether it was bound using a device tree node or U_BOOT_DEVICE() structure. In either case, |