[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1481324115.3112.8.camel@aj.id.au>
Date: Sat, 10 Dec 2016 09:25:15 +1030
From: Andrew Jeffery <andrew@...id.au>
To: Rob Herring <robh@...nel.org>
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 Fri, 2016-12-09 at 16:49 -0600, Rob Herring wrote:
> 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.
Thanks for clarifying. I wasn't sure so I wrote the patch with the
thought that we could drop it if it wasn't necessary. Regardless, I
think being explicit about the properties is nice.
>
> Acked-by: Rob Herring <robh@...nel.org>
Thanks,
Andrew
>
> Rob
Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)
Powered by blists - more mailing lists