From: Johan Hovold <johan@kernel.org>
To: ebrahim@gnu.org
Cc: linux-usb@vger.kernel.org
Subject: USB: serial: pl2303: add Delock Infrared device id
Date: Sat, 9 Feb 2019 10:46:25 +0100 [thread overview]
Message-ID: <20190209094625.GR4686@localhost> (raw)
On Sat, Feb 09, 2019 at 12:18:40PM +0330, ebrahim@gnu.org wrote:
> From: Ebrahim Byagowi <ebrahim@gnu.org>
>
> This makes Delock Infrared adapter to work as a USB to Serial device.
> ---
> drivers/usb/serial/pl2303.c | 1 +
> drivers/usb/serial/pl2303.h | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
> index 98e7a5df0..d5ec72575 100644
> --- a/drivers/usb/serial/pl2303.c
> +++ b/drivers/usb/serial/pl2303.c
> @@ -105,6 +105,7 @@ static const struct usb_device_id id_table[] = {
> { USB_DEVICE(SANWA_VENDOR_ID, SANWA_PRODUCT_ID) },
> { USB_DEVICE(ADLINK_VENDOR_ID, ADLINK_ND6530_PRODUCT_ID) },
> { USB_DEVICE(SMART_VENDOR_ID, SMART_PRODUCT_ID) },
> + { USB_DEVICE(DELOCK_VENDOR_ID, DELOCK_PRODUCT_ID) },
> { } /* Terminating entry */
> };
>
> diff --git a/drivers/usb/serial/pl2303.h b/drivers/usb/serial/pl2303.h
> index 4e2554d55..01936de13 100644
> --- a/drivers/usb/serial/pl2303.h
> +++ b/drivers/usb/serial/pl2303.h
> @@ -153,3 +153,6 @@
> #define SMART_VENDOR_ID 0x0b8c
> #define SMART_PRODUCT_ID 0x2303
>
> +/* Delock Infrared Adapter */
> +#define DELOCK_VENDOR_ID 0x1685
> +#define DELOCK_PRODUCT_ID 0x2000
Please post the output of lsusb -v for this device, and perhaps also a
log from when connecting the device with driver debugging enabled.
How did you determine that this a pl2303 device?
Johan
next reply other threads:[~2019-02-09 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 9:46 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-11 10:17 USB: serial: pl2303: add Delock Infrared device id ebrahim
2019-02-11 8:24 Johan Hovold
2019-02-09 22:19 ebrahim
2019-02-09 15:41 Johan Hovold
2019-02-09 10:44 ebrahim
2019-02-09 9:08 Greg Kroah-Hartman
2019-02-09 8:48 ebrahim
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=20190209094625.GR4686@localhost \
--to=johan@kernel.org \
--cc=ebrahim@gnu.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).