From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: shawn.guo@linaro.org, linux-kernel@vger.kernel.org,
thierry.reding@gmail.com,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] regulator: core: Use postcore_initcall(regulator_init_complete)
Date: Tue, 26 Nov 2013 00:46:03 +0000 [thread overview]
Message-ID: <20131126004603.GU14725@sirena.org.uk> (raw)
In-Reply-To: <1385416655-7859-1-git-send-email-festevam@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Mon, Nov 25, 2013 at 07:57:35PM -0200, Fabio Estevam wrote:
> Calling regulator_init_complete via late_initcall can be too 'late' for the
> regulator to be available for the pwm backlight driver.
> Call regulator_init_complete with postcore_initcall level instead.
That's too early for some of the other functionality in this function
though - I'd be particularly worried about the code that goes aroud
turning off unused supplies running before drivers have a chance to load
either breaking things or causing user visible glitches (and of course
the goal here is to get have this run before that happens...).
I seem to remember that there's also some one initcall per object
limitation so if we are going to try to dance this dance purely in the
regulator code it'd probably need to be split out into another object as
well as another function. The other options that were suggested were to
either have the DT code push out the announcement or change the callers
to check of_have_populated_dt() as well as looking at the flag, of this
lot changing the callers is probably the cleanest. I'll probably do
that tomorrow if a patch doesn't turn up before then.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-26 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 21:57 [PATCH] regulator: core: Use postcore_initcall(regulator_init_complete) Fabio Estevam
2013-11-26 0:46 ` Mark Brown [this message]
2013-11-27 0:55 ` Mark Brown
2013-12-15 13:06 ` Shawn Guo
2013-12-15 17:03 ` Fabio Estevam
2013-12-16 8:40 ` Shawn Guo
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=20131126004603.GU14725@sirena.org.uk \
--to=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=thierry.reding@gmail.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