From: Johan Hovold <johan@kernel.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: Re: [PATCH] USB: serial: option: add support for DW5829e
Date: Mon, 21 Feb 2022 10:43:02 +0100 [thread overview]
Message-ID: <YhNepjwXJQH+Koof@hovoldconsulting.com> (raw)
In-Reply-To: <14f5bdc0.3675.17f1b94b947.Coremail.slark_xiao@163.com>
On Mon, Feb 21, 2022 at 05:20:05PM +0800, Slark Xiao wrote:
>> >> @@ -1063,6 +1065,10 @@ static const struct usb_device_id option_ids[] = {
> >> >> .driver_info = RSVD(0) | RSVD(1) | RSVD(6) },
> >> >> { USB_DEVICE(DELL_VENDOR_ID, DELL_PRODUCT_5821E_ESIM),
> >> >> .driver_info = RSVD(0) | RSVD(1) | RSVD(6) },
> >> >> + { USB_DEVICE_INTERFACE_CLASS(DELL_VENDOR_ID, DELL_PRODUCT_5829E, 0xff),
> >> >> + .driver_info = RSVD(6) },
> >> >> + { USB_DEVICE_INTERFACE_CLASS(DELL_VENDOR_ID, DELL_PRODUCT_5829E_ESIM, 0xff),
> >> >> + .driver_info = RSVD(6) },
> >> >
> >> >It looks like these entries will cause the driver to bind also to the
> >> >QMI port however.
> >> >
> >
> >> Actually not, currently RMNET port would load the qmi_wwan driver
> >> successfully even the class of QMI is also 0xff.
> >
> >That's not guaranteed so RMNET mode could break depending on probe
> >order with the above entries.
> >
> >> Do you mean I should add RSVD(0) to reduce confusion?
> >
> >You need to reserve it for correctness (or restructure the entries in
> >some other way to achieve the same result).
> >
> Yes, so I re-send a V2 version to reserve interface 0,1,6. Please help take a look on that.
There's no need to reserve interface 1 since it's not vendor class in
any configuration. I've already fixed up and applied your v2.
Also, in the future, please make sure to wrap the lines of your mails at
72 column or so.
Johan
prev parent reply other threads:[~2022-02-21 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 3:15 Slark Xiao
2022-02-09 14:27 ` Johan Hovold
2022-02-10 3:27 ` Slark Xiao
2022-02-21 9:07 ` Johan Hovold
2022-02-21 9:20 ` Slark Xiao
2022-02-21 9: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=YhNepjwXJQH+Koof@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=slark_xiao@163.com \
/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
all inboxes | Powered by JetHome®