From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Mike Rapoport <mike@compulab.co.il>,
eric miao <eric.y.miao@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd/da903x: initialize PMIC core early
Date: Mon, 15 Jun 2009 16:44:36 +0200 [thread overview]
Message-ID: <20090615144434.GD4094@sortiz.org> (raw)
In-Reply-To: <20090615143410.GE6106@sirena.org.uk>
On Mon, Jun 15, 2009 at 03:34:11PM +0100, Mark Brown wrote:
> On Mon, Jun 15, 2009 at 05:08:28PM +0300, Mike Rapoport wrote:
> > Samuel Ortiz wrote:
>
> > > Sure. Care to explain why this needs to be called earlier ?
>
> > We want to have da903x regulators available early during boot, and since they
> > are subdevices of mfd/da903x they cannot be enabled until the da903x core is
> > initialized.
> > I just saw Liam Girdwood pull request with "regulator: Move regulator drivers to
> > subsys_initcall()" commit and jumped in :)
>
> Any MFD core with regulators on it ought to be pulled forward to
> subsys_initcall(). Doing this makes it easier to get a sensible
> ordering during boot without having a song and dance in consumer
> drivers waiting for the regulators that supply them to instantiate.
Yep, I'm preparing a patch for that.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2009-06-15 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 12:02 [PATCH] mfd/da903x: initialize PMIC core early Mike Rapoport
2009-06-15 13:51 ` Samuel Ortiz
2009-06-15 14:08 ` Mike Rapoport
2009-06-15 14:34 ` Mark Brown
2009-06-15 14:44 ` Samuel Ortiz [this message]
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=20090615144434.GD4094@sortiz.org \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=eric.y.miao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@compulab.co.il \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.