> sendsetup is to prevent the driver from sending a specific USB control
> message for setting up serial parameters, which some devices ignore and
> cause the driver to stall.
>
> reserved is what you're looking for. This one tells option not to bind to the
> given USB interfaces.
>
> So for exa
On Tue, 2017-08-08 at 22:22 +0200, Giuseppe Lippolis wrote:
> > The option driver use interface blacklists instead of multiple
> > match entries.
> > You should probably follow the same style there. But this is up to
> > Johan...
>
> Can I ask what ist he difference between .sendsetup and .reserve
> The option driver use interface blacklists instead of multiple match entries.
> You should probably follow the same style there. But this is up to Johan...
Can I ask what ist he difference between .sendsetup and .reserved and how to
use the bitmask in drivers/usb/serial/option.c ?
Thanks,
Bye.
> But we already have many Sierra devices with 2 QMI interfaces (the 3rd one
> is documented and verified non-functional for unknown reasons). And these
> tend to come with multiple OEM device IDs. So a whitelist method could
> reduce the number of matching entries considerably. Feel free to subm
