All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jaya.p.g" <jaya.p.g@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: tedd.an@intel.com, anand.kalyanakrishnan@intel.com
Subject: [PATCH] Bluetooth: Add Support for Intel Bluetooth Devices JfP and ThP [8087:0025,8087:0aaa]
Date: Wed, 8 Feb 2017 19:32:23 +0530	[thread overview]
Message-ID: <589B24EF.4000401@linux.intel.com> (raw)

 From 1f59dbab81364031ea380d6e4ab79ce0c293b31e Mon Sep 17 00:00:00 2001
From: Jaya Praveen G <jaya.p.g@linux.intel.com>
Date: Wed, 8 Feb 2017 17:30:55 +0530
Subject: [PATCH] Bluetooth: Add Support for Intel Bluetooth Devices JfP 
and ThP [8087:0025,8087:0aaa]

This Patch add support for ThP and JfP Bluetooth Modules.
ThP and JfP are the next generation of Intel Bluetooth Modules.

JeffersonPeak
PID:0XAAA
HW Variant: 0x11 (17)

ThunderPeak
PID:0x0025
HW Variant: 0x12 (18)

Signed-off-by: jaya.p.g <jaya.p.g@intel.com>
---
  drivers/bluetooth/btusb.c | 10 +++++++---
  1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 2f633df..5e37628 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -317,11 +317,13 @@
  	{ USB_DEVICE(0x1286, 0x204e), .driver_info = BTUSB_MARVELL },

  	/* Intel Bluetooth devices */
+	{ USB_DEVICE(0x8087, 0x0025), .driver_info = BTUSB_INTEL_NEW },
  	{ USB_DEVICE(0x8087, 0x07da), .driver_info = BTUSB_CSR },
  	{ USB_DEVICE(0x8087, 0x07dc), .driver_info = BTUSB_INTEL },
  	{ USB_DEVICE(0x8087, 0x0a2a), .driver_info = BTUSB_INTEL },
  	{ USB_DEVICE(0x8087, 0x0a2b), .driver_info = BTUSB_INTEL_NEW },
  	{ USB_DEVICE(0x8087, 0x0aa7), .driver_info = BTUSB_INTEL },
+	{ USB_DEVICE(0x8087, 0x0aaa), .driver_info = BTUSB_INTEL_NEW },

  	/* Other Intel Bluetooth devices */
  	{ USB_VENDOR_AND_INTERFACE_INFO(0x8087, 0xe0, 0x01, 0x01),
@@ -2010,13 +2012,15 @@ static int btusb_setup_intel_new(struct hci_dev 
*hdev)
  		return -EINVAL;
  	}

-	/* At the moment the iBT 3.0 hardware variants 0x0b (LnP/SfP)
-	 * and 0x0c (WsP) are supported by this firmware loading method.
+	/* At the moment the iBT 3.0 hardware variants 0x0b (LnP/SfP),
+	 * 0x0c (WsP),0x11 (JfP), and 0x12 (ThP) are supported by this
+	 * firmware loading method.
  	 *
  	 * This check has been put in place to ensure correct forward
  	 * compatibility options when newer hardware variants come along.
  	 */
-	if (ver.hw_variant != 0x0b && ver.hw_variant != 0x0c) {
+	if (ver.hw_variant != 0x0b && ver.hw_variant != 0x0c &&
+		ver.hw_variant != 0x11 && ver.hw_variant != 0x12) {
  		BT_ERR("%s: Unsupported Intel hardware variant (%u)",
  		       hdev->name, ver.hw_variant);
  		return -EINVAL;
-- 
1.9.1


             reply	other threads:[~2017-02-08 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 14:02 jaya.p.g [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-08 12:44 [PATCH] Bluetooth: Add Support for Intel Bluetooth Devices JfP and ThP [8087:0025,8087:0aaa] jaya.p.g

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=589B24EF.4000401@linux.intel.com \
    --to=jaya.p.g@linux.intel.com \
    --cc=anand.kalyanakrishnan@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tedd.an@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.