[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161209224927.3indhfdjgyndtjid@rob-hp-laptop>
Date: Fri, 9 Dec 2016 16:49:27 -0600
From: Rob Herring <robh@...nel.org>
To: Andrew Jeffery <andrew@...id.au>
Cc: Lee Jones <lee.jones@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Linus Walleij <linus.walleij@...aro.org>,
Corey Minyard <minyard@....org>,
Cédric Le Goater <clg@...d.org>,
Joel Stanley <joel@....id.au>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/6] mfd: dt: ranges, #address-cells and #size-cells
as optional properties
On Tue, Dec 06, 2016 at 01:53:17PM +1100, Andrew Jeffery wrote:
> 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 resources within the multi-function
> device.
>
> Signed-off-by: Andrew Jeffery <andrew@...id.au>
> ---
> Documentation/devicetree/bindings/mfd/mfd.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
No objections to this, but this is all implied by having a reg property.
Acked-by: Rob Herring <robh@...nel.org>
Rob
Powered by blists - more mailing lists