linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars Melin <larsm17@gmail.com>
To: Kristian Evensen <kristian.evensen@gmail.com>,
	Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] option: Improve Quectel EP06 detection
Date: Tue, 11 Sep 2018 21:00:15 +0700	[thread overview]
Message-ID: <8ce10eef-f332-a1c0-e16e-fb1c2055131a@gmail.com> (raw)
In-Reply-To: <CAKfDRXiVbE3-eteTCZjEqyR0LaLMpN8t4P_ihzHPChse9=FxmQ@mail.gmail.com>

On 9/10/2018 18:39, Kristian Evensen wrote:
> Hi,
> 
> On Mon, Sep 10, 2018 at 12:30 PM Johan Hovold <johan@kernel.org> wrote:
>> Please provide the output of usb-devices (or lsusb -v) for both
>> "configurations". How do you update the configuration by the way?
> 
> The configuration is updated using a proprietary AT-command
> (AT+QCFG="usbcfg"). The format of the command is as follows:
> AT+QCFG="usbcfg",<vid>,<pid>,<diag>,<nmea>,<at_port>,<modem>,<rmnet>,<adb>.
> In other words, you set which interfaces to enable/disable. Based on
> my testing, it is only possible to enable/disable diag, rmnet (QMI)
> and adb, as well as nmea, at_port and modem together. I.e., it is not
> possible to only disable for example nmea.
> 

> If I for example disable diag, then the bInterfaceNumber of nmea
> changes from 1 to 0, at from 2 to 1, etc., etc.
> 
> BR,
> Kristian
>

This also becomes a mess for the qmi-wwan driver which has the rmnet/qmi 
interface hardcoded to 4 so that driver will also need a workaround.
Quectel seems to have completely missed the reason why usb id's should 
be unique and not reused  for a different product or a different 
interface layout, there is already a workaround in qmi-wwan for their 
previous EC-20 card...
My opinion is that the option and qmi-wwan drivers should support EP06 
in the factory delivery configuration and not in a configuration the 
user has selected with a Quectel proprietary AT cmd.
Can you give some good reason for disabling an interface instead of 
letting it stay but not use it if you don't need it?


Thanks
/Lars


  reply	other threads:[~2018-09-11 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-08 12:57 [PATCH] option: Improve Quectel EP06 detection Kristian Evensen
2018-09-10 10:30 ` Johan Hovold
2018-09-10 11:39   ` Kristian Evensen
2018-09-11 14:00     ` Lars Melin [this message]
2018-09-11 14:34       ` Kristian Evensen
2018-09-12 16:32         ` Lars Melin
2018-09-12 16:57           ` Kristian Evensen
2018-09-12 18:25             ` Lars Melin
2018-09-12 19:18               ` Dan Williams
2018-09-12 20:34                 ` Bjørn Mork
2018-09-13  9:17                   ` Johan Hovold
2018-09-13  9:21                     ` [PATCH 1/2] USB: serial: option: improve " Johan Hovold
2018-09-13  9:21                       ` [PATCH 2/2] USB: serial: option: add two-endpoints device-id flag Johan Hovold
2018-09-13  9:44                     ` [PATCH] option: Improve Quectel EP06 detection Kristian Evensen
2018-09-13 15:13                     ` Kristian Evensen
2018-09-14  7:51                       ` Johan Hovold
2018-09-14  7:53                         ` Kristian Evensen
2018-09-14  8:42                           ` Johan Hovold
2018-09-10 14:43 ` Dan Williams

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=8ce10eef-f332-a1c0-e16e-fb1c2055131a@gmail.com \
    --to=larsm17@gmail.com \
    --cc=johan@kernel.org \
    --cc=kristian.evensen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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).