From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] core: Ensure drivers are given a chance to re-probe() late-on
Date: Tue, 12 Jul 2016 17:19:25 +0100 [thread overview]
Message-ID: <20160712161927.7521-1-lee.jones@linaro.org> (raw)
If a driver's resources are not available at probe() time, it is
common practice to defer probe (return -EPROBE_DEFER) until a time
where the required dependencies have been satisfied. However, if a
driver's resources are not provided by other drivers probe()ing
e.g. in a case where a driver is waiting for initramfs or rootfs to
be mounted in order to retrieve firmware located within, then
eventually we will run out of binding drivers (the trigger to re-run
deferred driver's probe()), and another re-probe() opportunity will
not be given.
This patch ensures that all drivers still on the deferred list are
given at least one more shot at probe()ing very late on in boot. This
ensures drivers who find themselves in the position explained in the
aforementioned example are able to locate their resources, resulting
in a successful probe().
Lee Jones (2):
driver-core: Add externally callable function to trigger deferred
probes
init/main: Trigger re-execution of deferred deferred probe()s
drivers/base/dd.c | 8 ++++++++
include/linux/device.h | 1 +
init/main.c | 1 +
3 files changed, 10 insertions(+)
--
2.9.0
next reply other threads:[~2016-07-12 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 16:19 Lee Jones [this message]
2016-07-12 16:19 ` [PATCH 1/2] driver-core: Add externally callable function to trigger deferred probes Lee Jones
2016-07-12 16:19 ` [PATCH 2/2] init/main: Trigger re-execution of deferred deferred probe()s Lee Jones
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=20160712161927.7521-1-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--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).