From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: Tegra board file deprecation schedule
Date: Fri, 27 Apr 2012 16:20:04 -0600 [thread overview]
Message-ID: <4F9B1B94.2030909@wwwdotorg.org> (raw)
In-Reply-To: <CAOMZO5Cnd9knDUuc4aZrPrtk5YKUwpr-oJhUnu=z94=9CfY1ug@mail.gmail.com>
On 04/27/2012 04:00 PM, Fabio Estevam wrote:
> On Fri, Apr 27, 2012 at 6:53 PM, Stephen Warren <swarren@wwwdotorg•org> wrote:
>
>> The only one sticking point might be that the Harmony regulator
>> initialization needs to wait for the regulator driver to be probed, but
>> happen before the PCIe driver is registers. Perhaps we could hook up
>> some temporary bus notifiers to handle that. But since PCIe will likely
>> be fixed in 3.6, we could probably just wait for that on Harmony.
>
> Does EPROBE_DEFER help in this case?
That's certainly the solution when everything is instantiated from
device tree, but I'm not sure it'll solve everything when doing the
regulator stuff from temporary code in the board file, which won't be
part of a driver probe.
next prev parent reply other threads:[~2012-04-27 22:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 21:24 Tegra board file deprecation schedule Stephen Warren
2012-04-27 21:39 ` Olof Johansson
2012-04-27 21:53 ` Stephen Warren
2012-04-27 22:00 ` Fabio Estevam
2012-04-27 22:20 ` Stephen Warren [this message]
2012-04-28 16:09 ` Marc Dietrich
2012-04-28 21:34 ` Russell King - ARM Linux
2012-04-29 18:11 ` Marc Dietrich
2012-04-29 18:56 ` Russell King - ARM Linux
2012-04-29 19:16 ` Stephen Warren
2012-04-30 8:58 ` Marc Dietrich
2012-04-30 15:58 ` Stephen Warren
2012-04-30 16:51 ` Marc Dietrich
2012-04-29 19:21 ` Stephen Warren
2012-04-30 9:00 ` Marc Dietrich
2012-04-28 21:26 ` Lucas Stach
2012-04-29 19:25 ` Stephen Warren
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=4F9B1B94.2030909@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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