From: Ming Lei <tom.leiming@gmail.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: kay.sievers@vrfy.org, greg@kroah.com, arjan@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: remove polling for driver_probe_done(v2)
Date: Fri, 30 Jan 2009 18:17:36 +0800 [thread overview]
Message-ID: <d82e647a0901300217s73a6a295sa61232bac8c95115@mail.gmail.com> (raw)
In-Reply-To: <20090130110555.116f747a@gondolin>
2009/1/30 Cornelia Huck <cornelia.huck@de.ibm.com>:
> On Fri, 30 Jan 2009 10:31:42 +0800,
> tom.leiming@gmail.com wrote:
>
>
>> /**
>> + * driver_wait_probe_done_and_dev_appear
>> + * wait until the probe sequence is finished _and_ the dev @name appears.
>> + *
>> + */
>> +void driver_wait_probe_done_and_dev_appear(char *name)
>> +{
>> + pr_debug("%s: probe_count = %d\n", __func__,
>> + atomic_read(&probe_count));
>> +
>> + wait_event(probe_waitqueue, (atomic_read(&probe_count) == 0) &&
>> + name_to_dev_t(name));
>
> probe_waitqueue is only woken at the end of really_probe(), not when
> whatever needs to be done to make the device available is done...
Yes.
If probing done does not mean the device is available, this patch should be
ignored or fixed further.
But polling is really not good, is there a approach to avoid the polling for
appearence of the root device?
Thanks!
>
>> +}
>> +/**
>> * driver_probe_device - attempt to bind device & driver together
>> * @drv: driver to bind a device to
>> * @dev: device to try to bind to the driver
>
--
Lei Ming
next prev parent reply other threads:[~2009-01-30 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 2:31 tom.leiming
2009-01-30 5:04 ` Arjan van de Ven
2009-01-30 9:59 ` Ming Lei
2009-01-30 10:05 ` Cornelia Huck
2009-01-30 10:17 ` Ming Lei [this message]
2009-01-30 10:30 ` Cornelia Huck
2009-01-30 10:51 ` Ming Lei
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=d82e647a0901300217s73a6a295sa61232bac8c95115@mail.gmail.com \
--to=tom.leiming@gmail.com \
--cc=arjan@infradead.org \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®