From: Mike Rapoport <mike@compulab.co.il>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: 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 17:08:28 +0300 [thread overview]
Message-ID: <4A3655DC.9090407@compulab.co.il> (raw)
In-Reply-To: <20090615135117.GC4094@sortiz.org>
Samuel Ortiz wrote:
> Hi Mike,
>
> On Mon, Jun 15, 2009 at 03:02:09PM +0300, Mike Rapoport wrote:
>> Samuel,
>> It'd be great if this can go to 2.6.31
> 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 :)
> Cheers,
> Samuel.
>
>> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
>> ---
>> drivers/mfd/da903x.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/mfd/da903x.c b/drivers/mfd/da903x.c
>> index 7283d88..e5ffe56 100644
>> --- a/drivers/mfd/da903x.c
>> +++ b/drivers/mfd/da903x.c
>> @@ -561,7 +561,7 @@ static int __init da903x_init(void)
>> {
>> return i2c_add_driver(&da903x_driver);
>> }
>> -module_init(da903x_init);
>> +subsys_initcall(da903x_init);
>>
>> static void __exit da903x_exit(void)
>> {
>> --
>> 1.6.0.6
>>
>>
>> --
>> Sincerely yours,
>> Mike.
>>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-06-15 14:08 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 [this message]
2009-06-15 14:34 ` Mark Brown
2009-06-15 14:44 ` Samuel Ortiz
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=4A3655DC.9090407@compulab.co.il \
--to=mike@compulab.co.il \
--cc=eric.y.miao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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