From: <hildawu@realtek.com>
To: <marcel@holtmann.org>
Cc: <johan.hedberg@gmail.com>, <luiz.dentz@gmail.com>,
<linux-bluetooth@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<max.chou@realtek.com>, <alex_lu@realsil.com.cn>,
<kidman@realtek.com>
Subject: [PATCH v2 0/5] Bluetooth: btusb: Add support IDs for Realtek RTL8852C
Date: Thu, 14 Jul 2022 19:25:18 +0800 [thread overview]
Message-ID: <20220714112523.13242-1-hildawu@realtek.com> (raw)
From: Hilda Wu <hildawu@realtek.com>
Add support IDs to usb_device_id table for Realtek RTL8852C.
Support VID, PID as below
0x04CA, 0x4007
0x04c5, 0x1675
0x0CB8, 0xC558
0x13D3, 0x3587
0x13D3, 0x3586
---
Changes in v2:
-Modify commit messeage summary.
---
Thank you for your review and suggestions.
Hilda Wu (5):
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
drivers/bluetooth/btusb.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
--
2.17.1
next reply other threads:[~2022-07-14 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 11:25 hildawu [this message]
2022-07-14 11:25 ` [PATCH v2 1/5] Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007 hildawu
2022-07-14 11:25 ` [PATCH v2 2/5] Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675 hildawu
2022-07-14 11:25 ` [PATCH v2 3/5] Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558 hildawu
2022-07-14 11:25 ` [PATCH v2 4/5] Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587 hildawu
2022-07-14 11:25 ` [PATCH v2 5/5] Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586 hildawu
2022-07-20 16:20 ` [PATCH v2 0/5] Bluetooth: btusb: Add support IDs for Realtek RTL8852C patchwork-bot+bluetooth
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=20220714112523.13242-1-hildawu@realtek.com \
--to=hildawu@realtek.com \
--cc=alex_lu@realsil.com.cn \
--cc=johan.hedberg@gmail.com \
--cc=kidman@realtek.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.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®