From: Johan Hovold <johan@kernel.org>
To: Davide Tronchin <davide.tronchin.94@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
larsm17@gmail.com, marco.demarco@posteo.net,
cesare.marzano@gmail.com
Subject: Re: [PATCH v4 3/3] USB: serial: option: add u-blox LARA-L6 modem
Date: Tue, 15 Nov 2022 11:22:46 +0100 [thread overview]
Message-ID: <Y3NodufBpWHAl1qG@hovoldconsulting.com> (raw)
In-Reply-To: <Y3NnaMkDraj5fwvu@hovoldconsulting.com>
On Tue, Nov 15, 2022 at 11:18:17AM +0100, Johan Hovold wrote:
> On Tue, Nov 08, 2022 at 05:30:01PM +0100, Davide Tronchin wrote:
> > Add LARA-L6 PIDs for three different USB compositions.
> >
> > LARA-L6 module can be configured (by AT interface) in three different
> > USB modes:
> > * Default mode (Vendor ID: 0x1546 Product ID: 0x1341) with 4 serial
> > interfaces
> > * RmNet mode (Vendor ID: 0x1546 Product ID: 0x1342) with 4 serial
> > interfaces and 1 RmNet virtual network interface
> > * CDC-ECM mode (Vendor ID: 0x1546 Product ID: 0x1343) with 4 serial
> > interface and 1 CDC-ECM virtual network interface
> >
> > In default mode LARA-L6 exposes the following interfaces:
> > If 0: Diagnostic
> > If 1: AT parser
> > If 2: AT parser
> > If 3: AT parser/alternative functions
> > @@ -1125,6 +1130,13 @@ static const struct usb_device_id option_ids[] = {
> > .driver_info = RSVD(1) | RSVD(3) },
> > { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x908b), /* u-blox LARA-R6 00B */
> > .driver_info = RSVD(4) },
> > + /* u-blox products using u-blox vendor ID */
> > + { USB_DEVICE(UBLOX_VENDOR_ID, UBLOX_PRODUCT_LARA_L6),
> > + .driver_info = RSVD(4) },
>
> Why are you reserving interface 4 here? This should be removed or
> explained in the commit message.
Apparently Lars already pointed this out, but again you ignored review
feedback without any comment and sent a v5.
Mistakes happen, but this is starting to look like more than that.
> > + { USB_DEVICE(UBLOX_VENDOR_ID, UBLOX_PRODUCT_LARA_L6_RMNET),
> > + .driver_info = RSVD(4) },
> > + { USB_DEVICE(UBLOX_VENDOR_ID, UBLOX_PRODUCT_LARA_L6_ECM),
> > + .driver_info = RSVD(4) },
> > /* Quectel products using Quectel vendor ID */
> > { USB_DEVICE_AND_INTERFACE_INFO(QUECTEL_VENDOR_ID, QUECTEL_PRODUCT_EC21, 0xff, 0xff, 0xff),
> > .driver_info = NUMEP2 },
Johan
next prev parent reply other threads:[~2022-11-15 10:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 9:27 [PATCH v3] USB: serial: option: the patch is meant to support LARA-R6 Cat 1 and LARA-L6 CAT 4 module family Davide Tronchin
2022-10-27 14:11 ` Johan Hovold
2022-11-08 16:29 ` [PATCH v4 1/3] USB: serial: option: remove old LARA-R6 PID Davide Tronchin
2022-11-08 16:30 ` [PATCH v4 2/3] USB: serial: option: add u-blox LARA-R6 00B modem Davide Tronchin
2022-11-08 16:30 ` [PATCH v4 3/3] USB: serial: option: add u-blox LARA-L6 modem Davide Tronchin
2022-11-09 4:10 ` Lars Melin
2022-11-15 10:18 ` Johan Hovold
2022-11-15 10:22 ` Johan Hovold [this message]
2022-11-15 16:50 ` Davide Tronchin
2022-11-16 8:10 ` Johan Hovold
2022-11-09 4:15 ` [PATCH v4 1/3] USB: serial: option: remove old LARA-R6 PID Lars Melin
2022-11-09 9:34 ` Lars Melin
2022-11-09 16:17 ` [PATCH v5 " Davide Tronchin
2022-11-09 16:17 ` [PATCH v5 2/3] USB: serial: option: add u-blox LARA-R6 00B modem Davide Tronchin
2022-11-09 16:17 ` [PATCH v5 3/3] USB: serial: option: add u-blox LARA-L6 modem Davide Tronchin
2022-11-15 10:12 ` [PATCH v5 1/3] USB: serial: option: remove old LARA-R6 PID Johan Hovold
2022-11-15 16:46 ` Davide Tronchin
2022-11-16 8:05 ` Johan Hovold
2022-11-16 9:50 ` Davide Tronchin
2022-11-16 9:55 ` Johan Hovold
2022-11-16 15:59 ` [PATCH v6 " Davide Tronchin
2022-11-16 15:59 ` [PATCH v6 2/3] USB: serial: option: add u-blox LARA-R6 00B modem Davide Tronchin
2022-11-16 15:59 ` [PATCH v6 3/3] USB: serial: option: add u-blox LARA-L6 modem Davide Tronchin
2022-11-16 16:28 ` Johan Hovold
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=Y3NodufBpWHAl1qG@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=cesare.marzano@gmail.com \
--cc=davide.tronchin.94@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=larsm17@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=marco.demarco@posteo.net \
/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).