From: Dan Williams <dcbw@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>,
"Kristian Evensen" <kristian.evensen@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] qmi_wwan: Support dynamic config on Quectel EP06
Date: Mon, 10 Sep 2018 09:42:13 -0500 [thread overview]
Message-ID: <6e60e3dc73f1d9f797298afaa60dd8776455521d.camel@redhat.com> (raw)
In-Reply-To: <87musst6wo.fsf@miraculix.mork.no>
On Sat, 2018-09-08 at 16:12 +0200, Bjørn Mork wrote:
> Kristian Evensen <kristian.evensen@gmail.com> writes:
>
> > Quectel EP06 (and EM06/EG06) supports dynamic configuration of USB
> > interfaces, without the device changing VID/PID or configuration
> > number.
> > When the configuration is updated and interfaces are added/removed,
> > the
> > interface numbers change. This means that the current code for
> > matching
> > EP06 does not work.
>
> That's annoying, but hardly surprising. They obviously try to make
> life
> as hard as possible for the drivers. I wonder what the Windows
> drivers
> do here, if there are any? Or are these modules only used in
> embedded
> Linux devices?
>
> > This patch removes the current EP06 interface number match, and
> > replaces
> > it with a match on class, subclass and protocol. Unfortunately,
> > matching
> > on those three alone is not enough, as the diag interface exports
> > the
> > same values as QMI. The other serial interfaces + adb export
> > different
> > values and do not match.
> >
> > The diag interface only has two endpoints, while the QMI interface
> > has
> > three. I have therefore added a check for number of interfaces, and
> > we
> > ignore the interface if the number of endpoints equals two.
>
> Could this break if more/other functions are enabled? Are you sure
> there can't be any other type of serial function with 3 endpoints and
> ff/ff/ff? Well, I guess no one knows for sure... And this is more
> than
> good enough until it breaks. Thanks for solving the puzzle. Looks
> good
> to me.
I'm sure they could add another serial interface with ff/ff/ff and 3
endpoints, but I don't know what else we can do to make this device
work correctly. I double-checked the permutations & logic and it makes
sense to me.
Acked-by: Dan Williams <dcbw@redhat.com>
Dan
next prev parent reply other threads:[~2018-09-10 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 11:50 [PATCH net] qmi_wwan: Support dynamic config on Quectel EP06 Kristian Evensen
2018-09-08 14:12 ` Bjørn Mork
2018-09-09 14:37 ` Kristian Evensen
2018-09-10 14:42 ` Dan Williams [this message]
2018-09-10 17:49 ` David Miller
2018-11-01 17:40 ` Kristian Evensen
2018-11-01 19:30 ` Kristian Evensen
2018-11-01 19:37 ` Kristian Evensen
2018-11-02 3:34 ` David Miller
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=6e60e3dc73f1d9f797298afaa60dd8776455521d.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=bjorn@mork.no \
--cc=kristian.evensen@gmail.com \
--cc=netdev@vger.kernel.org \
/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).