From: Dan Williams <dcbw@redhat.com>
To: "Kristian Evensen" <kristian.evensen@gmail.com>,
"Bjørn Mork" <bjorn@mork.no>
Cc: Network Development <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net] qmi_wwan: Add support for Quectel EG12/EM12
Date: Tue, 05 Mar 2019 11:28:03 -0600 [thread overview]
Message-ID: <252cc21cc2ec219912a57e1fc09bf5b01f6ab92c.camel@redhat.com> (raw)
In-Reply-To: <CAKfDRXidQjY7i6MmqLc2OKO5RWm0uYSU60WEgg7b02-Jw4hHpg@mail.gmail.com>
On Sat, 2019-03-02 at 22:19 +0100, Kristian Evensen wrote:
> On Sat, Mar 2, 2019 at 4:00 PM Bjørn Mork <bjorn@mork.no> wrote:
> > I am not too happy about the double device id matching with extra
> > magic
> > applied. outside the device id table. It does not scale, and it
> > does
> > not play well at all with dynamic IDs. But I guess it's acceptable
> > for
> > two devices when it was ok for one, so
> >
> > Acked-by: Bjørn Mork <bjorn@mork.no>
> >
> > But I assume this isn't the last device we've seen with this issue.
> > Someone has already mention Quectel EM20. Maybe convert this code
> > to a
> > quirk for the next device and leave all the device specific magic
> > in the
> > device id table? Could even add a macro for the class match +
> > quirk
> > thing.
>
> (Appologies to Bjørn for receiving multiple copies of this email - I
> forgot that the Gmail app sends HTML-encoded emails)
>
> Thanks for your feedback. My reasoning was the same. For one or two
> devices, the current approach is (probably) ok. Any more, and a
> different approach is needed.
>
> Looking through the documentation I have, it seems like most
> Quectel-modems support the command used to change the
> USB-configuration. Thus, I wouldn’t be surprised if all or most
> existing Quectel-devices should have this quirk applied. I have a
> couple of older modules, so I will look at how they behave with
> different configurations. I will then either add the quirk soon or
> when for example EM20 is available (unless someone else does it
> earlier :)).
Yeah, this should really be a new quirk from here on.
Dan
next prev parent reply other threads:[~2019-03-05 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 12:32 [PATCH net] qmi_wwan: Add support for Quectel EG12/EM12 Kristian Evensen
2019-03-02 15:00 ` Bjørn Mork
2019-03-02 21:19 ` Kristian Evensen
2019-03-05 17:28 ` Dan Williams [this message]
2019-03-04 5:40 ` 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=252cc21cc2ec219912a57e1fc09bf5b01f6ab92c.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--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).