From: Kiran K <kiraank@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: sathish.narasimman@intel.com, chethan.tumkur.narayan@intel.com,
ravishankar.srivatsa@intel.com, kiraank@gmail.com,
Kiran K <kiran.k@intel.com>
Subject: [PATCH v7 4/4] Bluetooth: btusb: Map Typhoon peak controller to BTUSB_INTEL_NEWGEN
Date: Wed, 14 Oct 2020 17:58:37 +0530 [thread overview]
Message-ID: <1602678517-9912-4-git-send-email-kiran.k@intel.com> (raw)
In-Reply-To: <1602678517-9912-1-git-send-email-kiran.k@intel.com>
Map Typhoon peak Intel controller to BTUSB_INTEL_NEWGEN
Signed-off-by: Kiran K <kiran.k@intel.com>
Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
---
drivers/bluetooth/btusb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 5d68cdb..3e21d5e 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -366,7 +366,7 @@ static const struct usb_device_id blacklist_table[] = {
BTUSB_WIDEBAND_SPEECH },
{ USB_DEVICE(0x8087, 0x0029), .driver_info = BTUSB_INTEL_NEW |
BTUSB_WIDEBAND_SPEECH },
- { USB_DEVICE(0x8087, 0x0032), .driver_info = BTUSB_INTEL_NEW |
+ { USB_DEVICE(0x8087, 0x0032), .driver_info = BTUSB_INTEL_NEWGEN |
BTUSB_WIDEBAND_SPEECH},
{ USB_DEVICE(0x8087, 0x07da), .driver_info = BTUSB_CSR },
{ USB_DEVICE(0x8087, 0x07dc), .driver_info = BTUSB_INTEL },
--
2.7.4
next prev parent reply other threads:[~2020-10-14 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 12:28 [PATCH v7 1/4] Bluetooth: btusb: Add *setup* function for new generation Intel controllers Kiran K
2020-10-14 12:28 ` [PATCH v7 2/4] Bluetooth: btusb: Define a function to construct firmware filename Kiran K
2020-11-11 11:02 ` Marcel Holtmann
2020-11-19 11:22 ` K, Kiran
2020-10-14 12:28 ` [PATCH v7 3/4] Bluetooth: btusb: Helper function to download firmware to Intel adapters Kiran K
2020-10-14 12:28 ` Kiran K [this message]
2020-11-11 11:01 ` [PATCH v7 1/4] Bluetooth: btusb: Add *setup* function for new generation Intel controllers Marcel Holtmann
2020-11-19 11:19 ` K, Kiran
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=1602678517-9912-4-git-send-email-kiran.k@intel.com \
--to=kiraank@gmail.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravishankar.srivatsa@intel.com \
--cc=sathish.narasimman@intel.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;
as well as URLs for NNTP newsgroup(s).