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 12:50:46 +0000 [thread overview]
Message-ID: <4BAA0AA6.80902@warmcat.com> (raw)
In-Reply-To: <005501cacb42$c5bbcde0$513369a0$%szyprowski@samsung.com>
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?
>
> On the other hand a more generic solution might be needed, because besides
> the PMU there might be some other dependences between various devices that
> not possible to be ensured in the current framework (I'm thinking of v4l2
> subdevs that link 2 separate devices together, but currently are used only
> with i2c clients).
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.
-Andy
next prev parent reply other threads:[~2010-03-24 12:50 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 [this message]
2010-03-24 13:11 ` Mark Brown
2010-03-24 13:22 ` Andy Green
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=4BAA0AA6.80902@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.