From: Johan Hovold <johan@kernel.org>
To: Aleksander Morgado <aleksander@aleksander.es>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: option: add support for SIM7070/SIM7080/SIM7090 modules
Date: Mon, 31 Aug 2020 08:43:06 +0200 [thread overview]
Message-ID: <20200831064306.GN21288@localhost> (raw)
In-Reply-To: <20200829090539.80140-1-aleksander@aleksander.es>
On Sat, Aug 29, 2020 at 11:05:39AM +0200, Aleksander Morgado wrote:
> These modules have 2 different USB layouts:
>
> The default layout with PID 0x9205 (AT+CUSBSELNV=1) exposes 4 TTYs and
> an ECM interface:
>
> T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=1e0e ProdID=9205 Rev=00.00
> S: Manufacturer=SimTech, Incorporated
> S: Product=SimTech SIM7080
> S: SerialNumber=1234567890ABCDEF
> C: #Ifs= 6 Cfg#= 1 Atr=e0 MxPwr=500mA
> I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x4 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=cdc_ether
> I: If#=0x5 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_ether
>
> The purpose of each TTY is as follows:
> * ttyUSB0: DIAG/QCDM port.
> * ttyUSB1: GNSS data.
> * ttyUSB2: AT-capable port (control).
> * ttyUSB3: AT-capable port (data).
>
> In the secondary layout with PID=0x9206 (AT+CUSBSELNV=86) the module
> exposes 6 TTY ports:
>
> T: Bus=02 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 8 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=1e0e ProdID=9206 Rev=00.00
> S: Manufacturer=SimTech, Incorporated
> S: Product=SimTech SIM7080
> S: SerialNumber=1234567890ABCDEF
> C: #Ifs= 6 Cfg#= 1 Atr=e0 MxPwr=500mA
> I: If#=0x0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#=0x5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
>
> The purpose of each TTY is as follows:
> * ttyUSB0: DIAG/QCDM port.
> * ttyUSB1: GNSS data.
> * ttyUSB2: AT-capable port (control).
> * ttyUSB3: QFLOG interface.
> * ttyUSB4: DAM interface.
> * ttyUSB5: AT-capable port (data).
>
> Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
Now applied. Thanks, Aleksander.
Johan
prev parent reply other threads:[~2020-08-31 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 9:05 [PATCH] USB: serial: option: add support for SIM7070/SIM7080/SIM7090 modules Aleksander Morgado
2020-08-31 6:43 ` 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=20200831064306.GN21288@localhost \
--to=johan@kernel.org \
--cc=aleksander@aleksander.es \
--cc=gregkh@linuxfoundation.org \
--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).