From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: linux-embedded@vger.kernel.org
Subject: RFC: prevent auto binding for some platform devices
Date: Mon, 21 Jul 2008 08:42:24 +0200 [thread overview]
Message-ID: <20080721064224.GA28238@digi.com> (raw)
Hello,
I have an emedded machine here on my desk and want to stop some
driver/device pairs from binding. There are two types of reason for it:
a) pin muxing doesn't allow attaching e.g. spi and serial at the same
time. In this case I want a defined "winner" that doesn't depend
on link (or module load) order.
b) the devboard has attached an led on a line that is also available
on a header. So I don't want to bind the led driver by default
because there might be another device connected to the gpio line.
Still I want to provide the led device and driver such that
userspace can bind these two via sysfs and use it.
I think a patch would be easy:
- add a flag to struct device(?) settable by platform code that would
indicate that the device should not autoprobe.
- change bus_attach_device to check that flag and only call
device_attach if it's not set.
Would this be sensible? Would it help anyone else?
Best regards
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 reply other threads:[~2008-07-21 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 6:42 Uwe Kleine-König [this message]
2008-07-21 7:24 ` prevent auto binding for some platform devices Dasgupta, Romit
2008-07-21 7:33 ` Uwe Kleine-König
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=20080721064224.GA28238@digi.com \
--to=uwe.kleine-koenig@digi.com \
--cc=linux-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.