I don't know. Then for every bus specific driver, they would have to do
the "dereference the structure" logic before they can start to determine
if they should bind to this specific device. That's all the PCI and USB
code really does, strip out the proper structures that are relevant to
the specific bus type, and then call the driver.
So in the end you would probably have a lot of duplicated code that
would be better off being in one place, like it is today :)
> There is another advantage to notifiers: they can be chained. Certain bus
> architectures need to do additional setup for things like pci devices. They
> would be able to do this by attaching a notifier.
That seems a bit overkill. The bus specific code can add those
architecture setup hooks right now if it's needed, right?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/