linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Oliver Neukum <oneukum@suse.com>
Cc: Johan Hovold <johan@kernel.org>,
	Aleksander Morgado <aleksander@aleksander.es>,
	gregkh@linuxfoundation.org, linux-usb@vger.kernel.org
Subject: usb: serial: qcserial: add support for the Dell DW5821e module
Date: Tue, 26 Jun 2018 10:49:24 +0200	[thread overview]
Message-ID: <876026c4q3.fsf@miraculix.mork.no> (raw)

Oliver Neukum <oneukum@suse.com> writes:

> On Di, 2018-06-26 at 09:40 +0200, Bjørn Mork  wrote:
>> This code can make Linux default to a MBIM configuration if the MBIM
>> function uses the first interface in that configuration, even if this
>> configuration is not the first one. Availability of a driver is not
>> considered. Except for RNDIS, just to make it the whole mess even more
>> confusing....
>
> How would you consider it? We chose a configuration before we load
> drivers. Even if we looked at the currently available drivers we'd end
> up with a choice depending on which devices were used in the past.
> A nondeterministic choice would be awkward.
>
> We can load drivers for all configurations' interfaces, but we cannot
> really wait for the loads to happen at that stage.

No, we do not want more driver support guesswork.

Going back in time, I believe it would be far better to simply let the
firmware decide the default by using the first configuration.  It's the
least surprising choice, and the likely tested configuration. And
it would simplify the code.

You are of course correct that we have no knowledge of available,
matching, or successfully probing, drivers at this point.  All the
problems come from the attempt to consider driver availability anyway.
The preference for class functions is clearly(?) based on an assumption
that class drivers are more likely to be available.

But I do realize that this was more difficult when the code was written.
We did not support many vendor specific functions, and there wasn't mcuh
reason to believe this would change over time. And it might have been
more complicated/impossible to override the kernel default in userspace,
writing to bConfigurationValue from something like udev?




Bjørn
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-06-26  8:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26  8:49 Bjørn Mork [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-26 12:05 usb: serial: qcserial: add support for the Dell DW5821e module Bjørn Mork
2018-06-26 12:01 Johan Hovold
2018-06-26 11:59 Aleksander Morgado
2018-06-26 11:55 Aleksander Morgado
2018-06-26  9:55 Johan Hovold
2018-06-26  9:43 Johan Hovold
2018-06-26  8:29 Oliver Neukum
2018-06-26  7:44 Bjørn Mork
2018-06-26  7:40 Bjørn Mork
2018-06-26  7:32 Aleksander Morgado
2018-06-26  6:09 Johan Hovold
2018-06-23 21:24 Aleksander Morgado

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=876026c4q3.fsf@miraculix.mork.no \
    --to=bjorn@mork.no \
    --cc=aleksander@aleksander.es \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).