From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Q] reprobe deferred-probing drivers
Date: Wed, 17 Oct 2012 10:43:20 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1210171039410.7402@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.1210171021060.7402@axis700.grange>
On Wed, 17 Oct 2012, Guennadi Liakhovetski wrote:
> Hi
>
> I've got a situation, for which I currently don't have a (good) solution.
Ok, right, would it be acceptable to just do something like
if (dev->parent)
device_lock(dev->parent);
device_release_driver(dev);
device_attach(dev);
?
Thanks
Guennadi
> Let's say device A depends on device B and as long as B hasn't probed, A
> requests deferred probing. Now B probes, which causes A to also succeed
> its probing. Next we want to remove B, say, by unloading its driver. A has
> to go back into "deferred-probing" state. How do we do it? This can be
> achieved by unloading B's driver and loading again. Essentially, we have
> to use the sysfs "unbind" and then the "bind" attributes. But how do we do
> this from the kernel? Shall we export driver_bind() and driver_unbind()?
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2012-10-17 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 8:27 Guennadi Liakhovetski
2012-10-17 8:43 ` Guennadi Liakhovetski [this message]
2012-10-17 16:02 ` Ming Lei
2012-10-17 15:02 ` Greg Kroah-Hartman
2012-10-17 15:10 ` Guennadi Liakhovetski
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=Pine.LNX.4.64.1210171039410.7402@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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®