From: andy@warmcat.com (Andy Green)
To: linux-arm-kernel@lists.infradead.org
Subject: Device probe order (i2c regulator vs. platform device)
Date: Wed, 24 Mar 2010 13:22:13 +0000 [thread overview]
Message-ID: <4BAA1205.6020309@warmcat.com> (raw)
In-Reply-To: <20100324131131.GB26453@rakim.wolfsonmicro.main>
On 03/24/10 13:11, Somebody in the thread at some point said:
> On Wed, Mar 24, 2010 at 12:50:46PM +0000, Andy Green wrote:
>> On 03/24/10 11:11, Somebody in the thread at some point said:
>>
>> Hi -
>>
>>> Right, this is a really common case. Maybe this callback could be added
>>> to the regulator framework as well?
>
> Looks like there's somethin up with the quoting configuration in your
Must be bugs in rawhide thunderbird.
>> Right, it's a generic issue with needing to delay other device
>> registration until something else has completed probe, not just PMU.
>> PMU is just the most common parent.
>
>> A callback is needed after probe() returned without error somehow.
>
> I rather suspect that the approach you suggest would have some usability
> issues, especially on PCs which don't by and by large have custom board
> code at all. Something more data driven, or handled more in drivers, is
> probably in order if this does get done. Anyway, this should probably
> be discussed elsewhere.
Fine, at the moment there are no arrangements for it and you have to go
hack callbacks in case by case, so anything would be better.
I agree it's not arm-specific so this isn't the place, but it'll be sad
if it just disappears off the radar.
-Andy
next prev parent reply other threads:[~2010-03-24 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 7:10 Device probe order (i2c regulator vs. platform device) Marek Szyprowski
2010-03-24 9:19 ` Andy Green
2010-03-24 11:11 ` Marek Szyprowski
2010-03-24 12:50 ` Andy Green
2010-03-24 13:11 ` Mark Brown
2010-03-24 13:22 ` Andy Green [this message]
2010-03-24 11:32 ` Mark Brown
2010-03-24 12:11 ` Andy Green
2010-03-24 14:01 ` Mark Brown
2010-03-24 14:38 ` Andy Green
2010-03-25 10:22 ` Mark Brown
2010-03-25 10:52 ` Andy Green
2010-03-24 10:21 ` Mark Brown
2010-03-24 10:57 ` Andy Green
2010-03-24 11:02 ` Marek Szyprowski
2010-03-24 11:08 ` Mark Brown
2010-03-24 11:27 ` Andy Green
2010-03-24 12:19 ` Mark Brown
2010-03-24 12:29 ` Andy Green
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=4BAA1205.6020309@warmcat.com \
--to=andy@warmcat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).