Hi,
On 09-06-17 10:52, Bjørn Mork wrote:
Greg KH <greg@xxxxxxxxx> writes:
On Fri, Jun 09, 2017 at 10:21:47AM +0200, Jiri Kosina wrote:
Longer-term, we'd ideally make 'generic' driver special and let it attach
as a 'last resort driver' if none of the specific driver picked the device
up during probe. But I don't think our current driver model allows this
easily ... or is there way I am not seeing?
Nope, the driver model does not provide a way for this, sorry, it's been
a complaint from the very beginning that we don't really know how to
handle, except to make sure the order of the drivers loaded are the
priority list, and that's not really a solution at all.
Add a 'priority' field to struct device_driver and sort the list by this
field instead of load order?
It is not that easy, e.g. with the HID use-case in question the
generic HID driver will typically be built-in where as the vendor
specific drivers will be modules, so you don't know if a higher
priority driver may show up later...
TBH I think that just adding a bunch of #ifdef's to the
hid_have_special_driver array may be best (esp. for 4.12)
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
