From: Lars Melin <larsm17@gmail.com>
To: Kristian Evensen <kristian.evensen@gmail.com>
Cc: Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] option: Improve Quectel EP06 detection
Date: Thu, 13 Sep 2018 01:25:43 +0700 [thread overview]
Message-ID: <f2c15eef-ed8d-12c0-2ba4-3dc068ca9fd4@gmail.com> (raw)
In-Reply-To: <CAKfDRXi3QdB0qCvqHPFXpxdpiHSJ2WoSqZGgjD3gEzAaPbBPUQ@mail.gmail.com>
On 9/12/2018 23:57, Kristian Evensen wrote:
> On Wed, Sep 12, 2018 at 6:32 PM Lars Melin <larsm17@gmail.com> wrote:
>> You have chosen a platform which has limited usb resources and want to
>> solve that problem by adjusting the device driver?
>
> No, you asked for a good reason for why disabling and not just
> ignoring an interface makes sense, and I think that supporting
> multiple EP06 on platforms with limited endpoints qualifies as a
> reason. My motivation behind this patch and modifying the driver, is
> to make the driver work with the different options/combinations
> supported by the modem. The platforms I am working on merely triggered
> the error and inspired the change.
>
>> Why don't you just unbind those interfaces which you are not using and
>> which are eating up your usb resources?
>
> As far as I know, unbinding interfaces from the driver does not free
> up the memory allocated to the interface by/on the USB controller. I
> also tried, just in case, and the output from lsusb is the same
> regardless of bind/unbind.
>
> Btw, the patch for the QMI driver has been accepted, since you
> mentioned that driver earlier. So the assumption about interface four
> is removed from there.
>
> BR,
> Kristian
>
That the patch has qmi-wwan patch has been accepted does not change the
fact that you are solving your problems in the wrong end.
You are using the OEM re-branding AT cmd to change the interface
composition without changing the vid and pid at the same time, this is a
big donut and the whole reason for why you have submitted patches which
shouldn't be needed.
rgds
/Lars
next prev parent reply other threads:[~2018-09-12 18:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 12:57 Kristian Evensen
2018-09-10 10:30 ` Johan Hovold
2018-09-10 11:39 ` Kristian Evensen
2018-09-11 14:00 ` Lars Melin
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 [this message]
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=f2c15eef-ed8d-12c0-2ba4-3dc068ca9fd4@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
Powered by JetHome