From: Bill Gatliff <bgat@billgatliff.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Paul Mundt <lethal@linux-sh.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: A better way to sequence driver initialization?
Date: Sat, 10 Apr 2010 20:33:53 -0500 [thread overview]
Message-ID: <4BC12701.7000208@billgatliff.com> (raw)
In-Reply-To: <k2ufa686aa41004101647md1e8cfbfw85c5b98b9613cd2d@mail.gmail.com>
Grant Likely wrote:
> On Sat, Apr 10, 2010 at 5:39 PM, Paul Mundt <lethal@linux-sh.org> wrote:
>
>> In cases where you can specifically note that dependencies, doing so will
>> save you a world of pain. Despite that, it's simply not possible to do
>> this as a free-for-all. Devices or busses that can tolerate multi-threaded
>> probing need to be converted over one at a time, but even then you still
>> need the dependency tracking for those that depend on link order today.
>>
Who's to say a function like gpio_request_wait_for_it(GPIO_NUMBER,
"dependent-driver") isn't the way to do the dependency tracking? I
can't even implement that without a context that can sleep...
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2010-04-11 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 19:23 A better way to sequence driver initialization? Bill Gatliff
2010-04-10 3:54 ` Bill Gatliff
2010-04-10 3:59 ` Bill Gatliff
2010-04-10 4:19 ` Bill Gatliff
2010-04-10 5:29 ` Grant Likely
2010-04-10 13:56 ` Bill Gatliff
2010-04-10 8:53 ` Benjamin Herrenschmidt
2010-04-10 13:35 ` Bill Gatliff
2010-04-10 23:39 ` Paul Mundt
2010-04-10 23:47 ` Grant Likely
2010-04-11 1:33 ` Bill Gatliff [this message]
2010-04-11 1:47 ` Paul Mundt
2010-04-11 3:30 ` Bill Gatliff
2010-04-11 1:31 ` Bill Gatliff
2010-04-11 7:26 ` Benjamin Herrenschmidt
2010-04-11 7:18 ` Benjamin Herrenschmidt
2010-04-11 7:15 ` Benjamin Herrenschmidt
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=4BC12701.7000208@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=lethal@linux-sh.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).