From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: "Dasgupta, Romit" <romit@ti.com>
Cc: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: prevent auto binding for some platform devices
Date: Mon, 21 Jul 2008 09:33:55 +0200 [thread overview]
Message-ID: <20080721073355.GA29676@digi.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930111C4F31C@dbde02.ent.ti.com>
Hello Romit,
Dasgupta, Romit wrote:
> I think with 2.6.18 or so onwards, there are two entries under /sys/bus/<bus_type>/
> drivers_autoprobe, drivers_probe. (Here bus_type is platform, usb, pci, etc...)
> By default drivers_autoprobe is 1. You need to disable autprobing of the driver by writing a 0 to that entry.
I saw that, too, but this fails in two ways: First if the drivers are
compiled in (as usual with an embedded machine) it's too late when
userspace is able to do that because then the drivers are already bound.
(The underlain kernel data is currently not available to platform code.)
And I don't want to stop the whole bus from binding, only the
conflicting devices.
Thanks
Uwe
--
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962
next prev parent reply other threads:[~2008-07-21 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 6:42 RFC: prevent auto binding for some platform devices Uwe Kleine-König
2008-07-21 7:24 ` Dasgupta, Romit
2008-07-21 7:33 ` Uwe Kleine-König [this message]
2008-07-21 7:31 ` RFC: " Alexey Zaytsev
2008-07-21 7:38 ` Alexey Zaytsev
2008-07-21 7:44 ` Uwe Kleine-König
2008-07-21 7:44 ` Ben Nizette
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=20080721073355.GA29676@digi.com \
--to=uwe.kleine-koenig@digi.com \
--cc=linux-embedded@vger.kernel.org \
--cc=romit@ti.com \
/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).