From: Johan Hovold <johan@kernel.org>
To: sdlyyxy <sdlyyxy@bupt.edu.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Reinhard Speyerer <rspmn@arcor.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: usb-serial-simple: add new device id for OPPO R11
Date: Fri, 29 Jul 2022 08:37:21 +0200 [thread overview]
Message-ID: <YuOAIdKlJKyh9o2k@hovoldconsulting.com> (raw)
In-Reply-To: <B47DDA3C-3CE2-4E25-B764-1744A4AA04A0@bupt.edu.cn>
On Fri, Jul 29, 2022 at 02:13:56PM +0800, sdlyyxy wrote:
>
> > On Jul 24, 2022, at 22:26, Johan Hovold <johan@kernel.org> wrote:
> >
> > On Sun, Jul 24, 2022 at 04:00:36PM +0200, Greg Kroah-Hartman wrote:
> >> On Sat, Jul 23, 2022 at 06:36:25PM +0200, Johan Hovold wrote:
> >>> On Mon, Jul 18, 2022 at 10:47:24PM +0200, Reinhard Speyerer wrote:
> >
> >>>> Please don't give the OPPO R11 diag port on Linux a bad name by letting
> >>>> the usb-serial-simple driver handle it.
> >>>
> >>> So while I'm not sure bandwidth is really a problem, I still tend to
> >>> agree that we should add this one to the option driver for now as that
> >>> is how we handle (non-GOBI) Qualcomm modems and their QCDM ports.
> >>
> >> If you want it to stay on the option driver, that's fine, but I still
> >> think it feels odd as it obviously does not follow the vendor-specific
> >> protocol that the option driver supports.
> >
> > But we've been dumping modem device-id entries in there since forever.
> >
> > The entries added to option have been for devices whose interfaces did
> > not follow any particular pattern (e.g. unlike the old GOBI modems).
> >
> > And as Reinhard mentioned, the line-control requests (which follow CDC)
> > are actually required by some Qualcomm modems so moving things out would
> > need to be done carefully.
> >
> > On the other hand, that request likely isn't needed for any QCDM/DIAG
> > ports, but who knows for sure.
>
> Test result for bandwidth problem:
> Sending 0x1f mask (diag command: 0x7d0500001f000000) and running LTE
> speedtest on the device, both option and simple can dump more than 80Mbps.
> The CRC of diag packets is OK at this high speed, so it seems that
> there is no message loss. I think this bandwidth is enough.
>
> For the flow control problem, it seems the SetControlLineState request
> send by option (usb_wwan) has no effect on the device. Both with and
> without this request the diag port works the same.
>
> Hope this can help you decide which driver to choose :)
Thanks a lot for confirming! I'll try to revisit this next week and get
something merged for 5.20-rcN.
Johan
prev parent reply other threads:[~2022-07-29 6:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 14:24 [PATCH] USB: usb-serial-simple: add new device id for OPPO R11 Greg Kroah-Hartman
2022-07-15 14:59 ` sdlyyxy
2022-07-16 12:13 ` Reinhard Speyerer
2022-07-16 13:36 ` sdlyyxy
2022-07-17 15:48 ` Reinhard Speyerer
2022-07-18 14:02 ` Yan Xinyu
2022-07-17 20:14 ` Greg Kroah-Hartman
2022-07-18 20:47 ` Reinhard Speyerer
2022-07-23 16:36 ` Johan Hovold
2022-07-24 14:00 ` Greg Kroah-Hartman
2022-07-24 14:26 ` Johan Hovold
2022-07-29 6:13 ` sdlyyxy
2022-07-29 6:37 ` Johan Hovold [this message]
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=YuOAIdKlJKyh9o2k@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rspmn@arcor.de \
--cc=sdlyyxy@bupt.edu.cn \
/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