devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: devicetree@vger.kernel.org, linux-bluetooth@vger.kernel.org
Cc: David Lechner <david@lechnology.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Bluetooth: Add device tree compatible for TI CC2560
Date: Tue, 12 Dec 2017 18:29:29 -0600	[thread overview]
Message-ID: <1513124971-23717-1-git-send-email-david@lechnology.com> (raw)

This series updates the bindings TI WiLink 7/8 Bluetooth to add TI CC256x
chips as well. A compatible string is also added to the hci_ll driver for
TI CC2560.

David Lechner (2):
  dt-bindings: net: add TI CC2560 Bluetooth chip
  Bluetooth: hci_ll: add "ti,cc2560" compatible string

 .../bindings/net/{ti,wilink-st.txt => ti-bluetooth.txt}     | 13 +++++++++++--
 drivers/bluetooth/hci_ll.c                                  |  1 +
 2 files changed, 12 insertions(+), 2 deletions(-)
 rename Documentation/devicetree/bindings/net/{ti,wilink-st.txt => ti-bluetooth.txt} (78%)

-- 
2.7.4

             reply	other threads:[~2017-12-13  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  0:29 David Lechner [this message]
2017-12-13  0:29 ` [PATCH 1/2] dt-bindings: net: add TI CC2560 Bluetooth chip David Lechner
     [not found]   ` <1513124971-23717-2-git-send-email-david-nq/r/kbU++upp/zk7JDF2g@public.gmane.org>
2017-12-15 23:05     ` Rob Herring
     [not found] ` <1513124971-23717-1-git-send-email-david-nq/r/kbU++upp/zk7JDF2g@public.gmane.org>
2017-12-13  0:29   ` [PATCH 2/2] Bluetooth: hci_ll: add "ti,cc2560" compatible string David Lechner
2017-12-13  8:39 ` [PATCH 0/2] Bluetooth: Add device tree compatible for TI CC2560 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=1513124971-23717-1-git-send-email-david@lechnology.com \
    --to=david@lechnology.com \
    --cc=devicetree@vger.kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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).