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
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
