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 v4 0/4] Broadcom Bluetooth UART device driver
Date: Wed, 17 Jun 2015 17:30:54 -0400 [thread overview]
Message-ID: <1434576658-20730-1-git-send-email-ifaenson@broadcom.com> (raw)
v4 - Make idle-timeout the device tree parameter
Keep speeds both in the line discipline and in the protocol
Remove unnecessary checks and traces
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 (4):
Broadcom Bluetooth UART Device Tree bindings
hci_uart: line discipline enhancements
btbcm_uart: Broadcom UART Platform Driver
hci_bcm: Broadcom UART protocol enhancements
.../devicetree/bindings/net/bluetooth/btbcm.txt | 86 ++++
drivers/bluetooth/Makefile | 1 +
drivers/bluetooth/btbcm_uart.c | 538 +++++++++++++++++++++
drivers/bluetooth/btbcm_uart.h | 74 +++
drivers/bluetooth/hci_bcm.c | 340 ++++++++++++-
drivers/bluetooth/hci_ldisc.c | 106 +++-
drivers/bluetooth/hci_uart.h | 7 +
7 files changed, 1137 insertions(+), 15 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
next reply other threads:[~2015-06-17 21:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 21:30 Ilya Faenson [this message]
2015-06-17 21:30 ` [PATCH v4 1/4] Broadcom Bluetooth UART Device Tree bindings Ilya Faenson
2015-06-17 21:33 ` Arend van Spriel
2015-06-17 23:11 ` FW: " Ilya Faenson
2015-06-18 15:02 ` Rob Herring
2015-06-18 18:54 ` Ilya Faenson
2015-06-18 19:41 ` Rob Herring
2015-06-18 20:37 ` Ilya Faenson
2015-06-19 15:47 ` Rob Herring
2015-06-19 17:06 ` Arend van Spriel
2015-06-19 18:49 ` Rob Herring
2015-06-19 19:20 ` Arend van Spriel
2015-06-29 18:36 ` Arend van Spriel
2015-07-02 18:26 ` Rob Herring
2015-06-19 20:37 ` Ilya Faenson
2015-06-19 19:23 ` Fabio Estevam
2015-06-19 20:40 ` Ilya Faenson
2015-06-17 21:30 ` [PATCH v4 2/4] hci_uart: line discipline enhancements Ilya Faenson
2015-06-17 21:50 ` Marcel Holtmann
2015-06-17 21:53 ` Ilya Faenson
2015-06-18 9:46 ` Frederic Danis
2015-06-18 10:17 ` Marcel Holtmann
2015-06-17 21:30 ` [PATCH v4 3/4] btbcm_uart: Broadcom UART Platform Driver Ilya Faenson
2015-06-17 21:30 ` [PATCH v4 4/4] hci_bcm: Broadcom UART protocol enhancements 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=1434576658-20730-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;
as well as URLs for NNTP newsgroup(s).