diff options
author | Andrew Jeffery <andrew@aj.id.au> | 2016-12-20 08:15:32 +0100 |
---|---|---|
committer | Lee Jones <lee.jones@linaro.org> | 2017-02-13 10:29:42 +0100 |
commit | 0894e9875cff7bcd2a7cb732e84626f320caae96 (patch) | |
tree | 9a1c7d6f3a1fe0d400e9ecc730af3853a9ba93e1 | |
parent | mfd: dt: Fix "indicates" typo in mfd bindings document (diff) | |
download | linux-0894e9875cff7bcd2a7cb732e84626f320caae96.tar.xz linux-0894e9875cff7bcd2a7cb732e84626f320caae96.zip |
mfd: dt: Add ranges, #address-cells and #size-cells as optional properties
Whilst describing a device and not a bus, simple-mfd is modelled on
simple-bus where child nodes are iterated and registered as platform
devices. Some complex devices, e.g. the Aspeed LPC controller, can
benefit from address space mapping such that child nodes can use the
regs property to describe their resource offsets within the
multi-function device.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
-rw-r--r-- | Documentation/devicetree/bindings/mfd/mfd.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/mfd/mfd.txt b/Documentation/devicetree/bindings/mfd/mfd.txt index f1fceeda12f1..bcb6abb9d413 100644 --- a/Documentation/devicetree/bindings/mfd/mfd.txt +++ b/Documentation/devicetree/bindings/mfd/mfd.txt @@ -25,6 +25,16 @@ Optional properties: be used. In the latter case the child devices will be determined by the operating system. +- ranges: Describes the address mapping relationship to the parent. Should set + the child's base address to 0, the physical address within parent's address + space, and the length of the address map. + +- #address-cells: Specifies the number of cells used to represent physical base + addresses. Must be present if ranges is used. + +- #size-cells: Specifies the number of cells used to represent the size of an + address. Must be present if ranges is used. + Example: foo@1000 { |