Linux bluetooth development
 help / color / mirror / Atom feed
From: Ilya Faenson <ifaenson@broadcom.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: <linux-bluetooth@vger.kernel.org>,
	Arend van Spriel <arend@broadcom.com>,
	Ilya Faenson <ifaenson@broadcom.com>
Subject: [PATCH v3 0/5] Broadcom Bluetooth UART device driver
Date: Wed, 17 Jun 2015 11:42:42 -0400	[thread overview]
Message-ID: <1434555767-18234-1-git-send-email-ifaenson@broadcom.com> (raw)

v3 -	Renamed brcm device into bcm.
	Allowed for the Broadcom protocol running without Broadcom device
		at the request of Loic Poulain.
	Introduced structure definitions for vendor specific commands.
	Transferred init-speed and oper-speed from protocol into the
		line discipline as they are configurable.
	Introduced hci_uart_init_tty function.
	Removed driver specific Kconfig menu option.
	Introduced protocol timer helper function.
	Converted single driver control dispatch routine into individual
		action routines & removed interface versioning.
	Eliminated specific firmware file name.
	Removed excessive tracing.
	Took care of numerous other comments from Marcel.
v2 -	Release upon the acceptance of Fred's updates, updated as per
		the latest comments from Marcel.
v1 -	Original release against the Fred Danis' updates.

Ilya Faenson (5):
  Broadcom Bluetooth UART Device Tree bindings
  H4 line discipline enhancements
  Broadcom Bluetooth UART Platform Driver
  Support the BCM4354 Bluetooth UART device
  BlueZ Broadcom UART Protocol

 .../devicetree/bindings/net/bluetooth/btbcm.txt    |  82 +++
 drivers/bluetooth/Makefile                         |   1 +
 drivers/bluetooth/btbcm.c                          |   2 +
 drivers/bluetooth/btbcm.h                          |  31 ++
 drivers/bluetooth/btbcm_uart.c                     | 580 +++++++++++++++++++++
 drivers/bluetooth/btbcm_uart.h                     |  74 +++
 drivers/bluetooth/hci_bcm.c                        | 340 +++++++++++-
 drivers/bluetooth/hci_ldisc.c                      |  93 +++-
 drivers/bluetooth/hci_uart.h                       |   9 +-
 9 files changed, 1195 insertions(+), 17 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/net/bluetooth/btbcm.txt
 create mode 100644 drivers/bluetooth/btbcm_uart.c
 create mode 100644 drivers/bluetooth/btbcm_uart.h

-- 
1.9.1

             reply	other threads:[~2015-06-17 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 15:42 Ilya Faenson [this message]
2015-06-17 15:42 ` [PATCH v3 1/5] Broadcom Bluetooth UART Device Tree bindings Ilya Faenson
2015-06-17 16:55   ` Marcel Holtmann
2015-06-17 15:42 ` [PATCH v3 2/5] H4 line discipline enhancements Ilya Faenson
2015-06-17 16:55   ` Marcel Holtmann
2015-06-17 19:48     ` Ilya Faenson
2015-06-17 15:42 ` [PATCH v3 3/5] Broadcom Bluetooth UART Platform Driver Ilya Faenson
2015-06-17 17:14   ` Marcel Holtmann
2015-06-17 20:01     ` Ilya Faenson
2015-06-17 15:42 ` [PATCH v3 4/5] Support the BCM4354 Bluetooth UART device Ilya Faenson
2015-06-17 16:59   ` Marcel Holtmann
2015-06-17 15:42 ` [PATCH v3 5/5] BlueZ Broadcom UART Protocol Ilya Faenson

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=1434555767-18234-1-git-send-email-ifaenson@broadcom.com \
    --to=ifaenson@broadcom.com \
    --cc=arend@broadcom.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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