From: Johan Hovold <johan@kernel.org>
To: Karoly Pados <pados@pados.hu>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: USB: serial: cp210x: add Silicon Labs IDs for Windows Update
Date: Mon, 18 Jun 2018 09:10:55 +0200 [thread overview]
Message-ID: <20180618071055.GH32411@localhost> (raw)
On Sat, Jun 09, 2018 at 01:26:08PM +0200, Karoly Pados wrote:
> Silicon Labs defines alternative VID/PID pairs for some chips that when
> used will automatically install drivers for Windows users without manual
> intervention. Unfortunately, these IDs are not recognized by the Linux
> module, so using these IDs improves user experience on one platform but
> degrades it on Linux. This patch addresses this problem.
How does this work; do these chips now come with the "windows update"
PIDs, and the silabs drivers then reprogram them to use other PIDs once
installed?
Is this documented somewhere?
> Now with mailing list in CC.
This kind of revision information should go below the cut-off line (---)
below. I'll just remove it this time unless there's a resend.
> Signed-off-by: Karoly Pados <pados@pados.hu>
> ---
> drivers/usb/serial/cp210x.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
> index eb6c26cbe579..b1849f657e01 100644
> --- a/drivers/usb/serial/cp210x.c
> +++ b/drivers/usb/serial/cp210x.c
> @@ -143,8 +143,11 @@ static const struct usb_device_id id_table[] = {
> { USB_DEVICE(0x10C4, 0x8B34) }, /* Qivicon ZigBee USB Radio Stick */
> { USB_DEVICE(0x10C4, 0xEA60) }, /* Silicon Labs factory default */
> { USB_DEVICE(0x10C4, 0xEA61) }, /* Silicon Labs factory default */
> + { USB_DEVICE(0x10C4, 0xEA63) }, /* Silicon Labs values for Windows Update support (CP2101-4/CP2102N) */
I may shorten this somewhat.
> { USB_DEVICE(0x10C4, 0xEA70) }, /* Silicon Labs factory default */
> { USB_DEVICE(0x10C4, 0xEA71) }, /* Infinity GPS-MIC-1 Radio Monophone */
> + { USB_DEVICE(0x10C4, 0xEA7A) }, /* Silicon Labs values for Windows Update support (CP2105) */
> + { USB_DEVICE(0x10C4, 0xEA7B) }, /* Silicon Labs values for Windows Update support (CP2108) */
> { USB_DEVICE(0x10C4, 0xF001) }, /* Elan Digital Systems USBscope50 */
> { USB_DEVICE(0x10C4, 0xF002) }, /* Elan Digital Systems USBwave12 */
> { USB_DEVICE(0x10C4, 0xF003) }, /* Elan Digital Systems USBpulse100 */
Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-18 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 7:10 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-18 7:46 USB: serial: cp210x: add Silicon Labs IDs for Windows Update Johan Hovold
2018-06-18 7:26 Karoly Pados
2018-06-09 11:26 Karoly Pados
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=20180618071055.GH32411@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=pados@pados.hu \
/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).