From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Wei Ni <wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH RESEND] ARM: tegra: set regulator full constraints
Date: Wed, 13 Nov 2013 10:29:07 -0700 [thread overview]
Message-ID: <5283B6E3.9070206@wwwdotorg.org> (raw)
In-Reply-To: <20131113122329.GC878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On 11/13/2013 05:23 AM, Mark Brown wrote:
> On Tue, Nov 12, 2013 at 11:20:44AM -0700, Stephen Warren wrote:
>
>> The only issue you may have to watch out for is: When is
>> regulator_init() called (i.e. when does core_initcall happen)
>> relative to when driver probe()s can be called? If it's earlier,
>> then core_initcall is early enough I suspect.
>
> What I said was to set this up when we hand the DT over to the DT
> code to be parsed so that we don't need to worry about any gaps
> like that, it seems like a more direct solution than worrying about
> initcall ordering.
I guess this means putting the call to
regulator_has_full_constraints() somewhere inside
early_init_dt_scan(), unflatten_device_tree(), or just perhaps inside
of_platform_populate() (all in drivers/of/*.c).
It seems slightly odd to tightly link the drivers/of and
drivers/regulator code like that, but I guess with the appropriate
ifdefs it'll work out OK.
next prev parent reply other threads:[~2013-11-13 17:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 7:05 [PATCH RESEND] ARM: tegra: set regulator full constraints Wei Ni
[not found] ` <1383203126-3243-1-git-send-email-wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-31 15:56 ` Stephen Warren
[not found] ` <52727DB7.9030109-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-01 1:31 ` Wei Ni
[not found] ` <52730480.6020607-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-01 16:01 ` Stephen Warren
2013-10-31 16:20 ` Mark Brown
[not found] ` <20131031162029.GF2493-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-04 5:59 ` Wei Ni
[not found] ` <527737C5.5080901-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-04 16:18 ` Mark Brown
[not found] ` <20131104161828.GK2493-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-05 9:05 ` Wei Ni
[not found] ` <5278B4CB.9050305-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-06 8:51 ` Mark Brown
[not found] ` <20131106085100.GB11602-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-06 10:39 ` Wei Ni
[not found] ` <527A1C47.6050405-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-06 11:01 ` Mark Brown
[not found] ` <20131106110154.GG11602-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-12 5:52 ` Wei Ni
[not found] ` <5281C228.3000404-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-11-12 18:20 ` Stephen Warren
[not found] ` <5282717C.3050502-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 10:12 ` Wei Ni
2013-11-13 12:23 ` Mark Brown
[not found] ` <20131113122329.GC878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 17:29 ` Stephen Warren [this message]
[not found] ` <5283B6E3.9070206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 19:07 ` Mark Brown
[not found] ` <20131113190745.GD878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 20:13 ` Stephen Warren
[not found] ` <5283DD52.5050903-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 20:49 ` Mark Brown
[not found] ` <20131113204923.GG878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 21:59 ` Stephen Warren
[not found] ` <5283F625.403-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-13 22:29 ` Mark Brown
[not found] ` <20131113222953.GA26614-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 23:41 ` Stephen Warren
[not found] ` <52840E23.5080105-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-14 11:36 ` Mark Brown
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=5283B6E3.9070206@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wni-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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