From: Frederic Danis <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v7 2/6] Bluetooth: btbcm: Add BCM4324B3 UART device
Date: Thu, 28 May 2015 11:25:02 +0200 [thread overview]
Message-ID: <1432805106-25719-3-git-send-email-frederic.danis@linux.intel.com> (raw)
In-Reply-To: <1432805106-25719-1-git-send-email-frederic.danis@linux.intel.com>
Add "waiting for configuration" address.
Add lmp_subver and firmware name for BCM4324B3 controller.
Signed-off-by: Frederic Danis <frederic.danis@linux.intel.com>
---
drivers/bluetooth/btbcm.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/bluetooth/btbcm.c b/drivers/bluetooth/btbcm.c
index c7aec97..e90e6b8 100644
--- a/drivers/bluetooth/btbcm.c
+++ b/drivers/bluetooth/btbcm.c
@@ -33,6 +33,7 @@
#define VERSION "0.1"
#define BDADDR_BCM20702A0 (&(bdaddr_t) {{0x00, 0xa0, 0x02, 0x70, 0x20, 0x00}})
+#define BDADDR_BCM4324B3 (&(bdaddr_t) {{0x00, 0x00, 0x00, 0xb3, 0x24, 0x43}})
int btbcm_check_bdaddr(struct hci_dev *hdev)
{
@@ -56,10 +57,11 @@ int btbcm_check_bdaddr(struct hci_dev *hdev)
bda = (struct hci_rp_read_bd_addr *)skb->data;
- /* The address 00:20:70:02:A0:00 indicates a BCM20702A0 controller
- * with no configured address.
+ /* Check if the address indicates a controller with no configured
+ * address.
*/
- if (!bacmp(&bda->bdaddr, BDADDR_BCM20702A0)) {
+ if (!bacmp(&bda->bdaddr, BDADDR_BCM20702A0) ||
+ !bacmp(&bda->bdaddr, BDADDR_BCM4324B3)) {
BT_INFO("%s: BCM: Using default device address (%pMR)",
hdev->name, &bda->bdaddr);
set_bit(HCI_QUIRK_INVALID_BDADDR, &hdev->quirks);
@@ -233,6 +235,7 @@ static const struct {
const char *name;
} bcm_uart_subver_table[] = {
{ 0x410e, "BCM43341B0" }, /* 002.001.014 */
+ { 0x4406, "BCM4324B3" }, /* 002.004.006 */
{ }
};
@@ -288,6 +291,7 @@ int btbcm_setup_patchram(struct hci_dev *hdev)
switch ((rev & 0xf000) >> 12) {
case 0:
+ case 3:
for (i = 0; bcm_uart_subver_table[i].name; i++) {
if (subver == bcm_uart_subver_table[i].subver) {
hw_name = bcm_uart_subver_table[i].name;
--
1.9.1
next prev parent reply other threads:[~2015-05-28 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:25 [PATCH v7 0/6] Add baudrate management for Bluetooth UART Frederic Danis
2015-05-28 9:25 ` [PATCH v7 1/6] Bluetooth: btbcm: Move request/release_firmware() Frederic Danis
2015-06-06 5:41 ` Marcel Holtmann
2015-05-28 9:25 ` Frederic Danis [this message]
2015-06-06 5:41 ` [PATCH v7 2/6] Bluetooth: btbcm: Add BCM4324B3 UART device Marcel Holtmann
2015-05-28 9:25 ` [PATCH v7 3/6] Bluetooth: hci_uart: Support operational speed during setup Frederic Danis
2015-05-28 9:25 ` [PATCH v7 4/6] Bluetooth: btbcm: Add helper functions for UART setup Frederic Danis
2015-06-06 5:41 ` Marcel Holtmann
2015-05-28 9:25 ` [PATCH v7 5/6] Bluetooth: hci_uart: Update Broadcom " Frederic Danis
2015-05-28 9:25 ` [PATCH v7 6/6] Bluetooth: hci_uart: Add bcm_set_baudrate() Frederic Danis
2015-06-06 5:47 ` Marcel Holtmann
2015-06-06 5:48 ` [PATCH v7 0/6] Add baudrate management for Bluetooth UART Marcel Holtmann
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=1432805106-25719-3-git-send-email-frederic.danis@linux.intel.com \
--to=frederic.danis@linux.intel.com \
--cc=linux-bluetooth@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).