From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, Greg KH <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [UPDATED v3][PATCH 5/7] regulator: sysfs ABI
Date: Fri, 7 Mar 2008 17:17:43 -0800 [thread overview]
Message-ID: <200803071717.44028.david-b@pacbell.net> (raw)
In-Reply-To: <20080307211714.GA26534@sirena.org.uk>
On Friday 07 March 2008, Mark Brown wrote:
> On Fri, Mar 07, 2008 at 08:12:12AM -0800, Greg KH wrote:
> > On Thu, Mar 06, 2008 at 06:12:05PM +0000, Liam Girdwood wrote:
>
> > > + Some regulator directories will contain a link called parent.
> > > + This points to the parent or supply regulator if one exists.
>
> > I don't think this is needed, why not just parent the device properly in
> > the device tree itself?
>
> The device tree would tend to show parent for the the control interfaces
> for the regulators (typically I2C or SPI) but there is likely to be
> little or no relationship between that and the power distribution in the
> system.
I find "parent" a bit awkward, and Greg won't be the only one to
be asking that question. Maybe it'd be better named "supply"?
- Dave
next prev parent reply other threads:[~2008-03-08 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 18:12 [UPDATED v3][PATCH 5/7] regulator: sysfs ABI Liam Girdwood
2008-03-07 16:12 ` Greg KH
2008-03-07 21:17 ` Mark Brown
2008-03-08 1:17 ` David Brownell [this message]
2008-03-08 5:52 ` Greg KH
2008-03-08 17:26 ` Liam Girdwood
2008-03-08 1:13 ` David Brownell
2008-03-08 21:13 ` Liam Girdwood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803071717.44028.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=greg@kroah.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox