[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130920155517.GM21013@sirena.org.uk>
Date: Fri, 20 Sep 2013 16:55:17 +0100
From: Mark Brown <broonie@...nel.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: Laxman Dewangan <ldewangan@...dia.com>, sameo@...ux.intel.com,
linus.walleij@...aro.org, akpm@...ux-foundation.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
rtc-linux@...glegroups.com, rob.herring@...xeda.com,
mark.rutland@....com, pawel.moll@....com, swarren@...dotorg.org,
rob@...dley.net, ijc+devicetree@...lion.org.uk,
grant.likely@...aro.org,
Florian Lobmaier <florian.lobmaier@....com>
Subject: Re: [PATCH V2 2/5] mfd: add support for AMS AS3722 PMIC
On Fri, Sep 20, 2013 at 01:39:30PM +0100, Lee Jones wrote:
> Personally I think the device should have sub-nodes. It's how we
> dealt with our DB8500 and AB8500 and it works very well. At the end of
> the day these all-in-one chips do house very different devices. I see
> no harm in describing them that way. I'm sure other OSes can make use
> of the sub-devices in similar ways.
For some bits of the device it makes sense - the regulators are a good
example with this device - but for others it's more questionable if the
Linux division of the device into subsystems is general enough (or even
static for Linux - like this one where there's the 32kHz clock being
handled by the RTC driver binding in the last patch posted).
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists