From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ux500: add a few AB8500 regulator consumers
Date: Mon, 17 Jan 2011 15:33:03 +0000 [thread overview]
Message-ID: <20110117153303.GK21113@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTi=gsmiGFF31Si71LQBAZqpZZcxMDOK6e3xAyZV7@mail.gmail.com>
On Mon, Jan 17, 2011 at 03:11:04PM +0100, Linus Walleij wrote:
> 2011/1/17 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> >> + ? ? {
> >> + ? ? ? ? ? ? .supply = "ab8500-gpadc",
> >> + ? ? },
> > I suspect there's a device for the ab8500?
> This is not the AB8500 actually, but a subdevice (MFD cell) for it
> that creates its own platform device and is separately powered.
> (Though using in-chip wiring I presume.)
It may be more sane to just have the subdevices use the core struct
device for requests for legibility.
next prev parent reply other threads:[~2011-01-17 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 13:04 [PATCH] ux500: add a few AB8500 regulator consumers Linus Walleij
2011-01-17 13:27 ` Mark Brown
2011-01-17 14:11 ` Linus Walleij
2011-01-17 15:33 ` Mark Brown [this message]
2011-01-18 21:11 ` Linus Walleij
2011-01-20 13:49 ` Mark Brown
2011-01-17 14:59 ` Rabin Vincent
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=20110117153303.GK21113@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).