On Tue, Mar 03, 2015 at 06:35:51PM +0100, Peter Stuge wrote: > > c) If the driver is configured to do something that the connected > > hardware is not capable of doing, it simply logs a message to > > kernel log and automatically disables it trying to work has > > fluid as possible > > How the driver reacts in this situation is a matter of policy, which > should probably not be specific to any one driver, but should > probably be set at a slightly higher level, perhaps even by the > person configuring/building the kernel. no, that's wrong. If I enable e.g. Isochronous endpoints on a version of DWC2 configured without Isochronous, I want the driver to just ignore Isochronous endpoints, not refuse to work. -- balbi
Attachment:
signature.asc
Description: Digital signature
