devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Faenson <ifaenson-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
Cc: linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Ilya Faenson <ifaenson-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Subject: [RFC v4 0/4] Broadcom Bluetooth UART device driver
Date: Fri, 22 May 2015 16:10:16 -0400	[thread overview]
Message-ID: <1432325420-12782-1-git-send-email-ifaenson@broadcom.com> (raw)

The next version of the driver changed as per Arend's comments.
The next step should be integration with the H4 line discipline
and BlueZ protocol enhancements from Intel. 

Ilya Faenson (4):
  Broadcom Bluetooth UART Device Tree bindings
  Broadcom Bluetooth UART Platform Driver
  Broadcom Bluetooth protocol UART support
  BlueZ Broadcom UART Protocol

 .../devicetree/bindings/net/bluetooth/btbcm.txt    |  82 +++
 drivers/bluetooth/Kconfig                          |   9 +
 drivers/bluetooth/Makefile                         |   1 +
 drivers/bluetooth/btbcm.c                          | 155 ++++-
 drivers/bluetooth/btbcm_uart.c                     | 674 +++++++++++++++++++++
 drivers/bluetooth/btbcm_uart.h                     |  89 +++
 drivers/bluetooth/hci_bcm.c                        | 528 +++++++++++++++-
 7 files changed, 1518 insertions(+), 20 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-05-22 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 20:10 Ilya Faenson [this message]
     [not found] ` <1432325420-12782-1-git-send-email-ifaenson-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-05-22 20:10   ` [RFC v4 1/4] Broadcom Bluetooth UART Device Tree bindings Ilya Faenson
     [not found]     ` <1432325420-12782-2-git-send-email-ifaenson-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-06-02  0:18       ` Rob Herring
     [not found]         ` <CAL_JsqLO+g56KYUocpWLpz4dDTP0fEXTa4RjJzeRsPvYjCyF4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-02 12:20           ` Ilya Faenson
     [not found]             ` <E0D3336E15B58B4294723AC879BA5E9425D49D-Wwdb2uEOBX8N93KskqRXH71+IgudQmzARxWJa1zDYLQ@public.gmane.org>
2015-06-02 15:34               ` Rob Herring
2015-05-22 20:10   ` [RFC v4 2/4] Broadcom Bluetooth UART Platform Driver Ilya Faenson
2015-05-22 20:10   ` [RFC v4 3/4] Broadcom Bluetooth protocol UART support Ilya Faenson
2015-05-22 20:10   ` [RFC v4 4/4] 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=1432325420-12782-1-git-send-email-ifaenson@broadcom.com \
    --to=ifaenson-dy08kvg/lbpwk0htik3j/w@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.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).