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>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] bluetooth: hci_ll: Get MAC address from NVMEM
Date: Sun, 3 Dec 2017 21:21:19 -0600 [thread overview]
Message-ID: <1512357682-8911-1-git-send-email-david@lechnology.com> (raw)
This series adds supporting getting the MAC address from a NVMEM provider
for "LL" HCI controllers (Texas Instruments).
The second patch is just cleaning things up before I add another similar
vendor-specific HCI command constant in the final patch.
David Lechner (3):
dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st
bluetooth: hci_ll: add constant for vendor-specific command
bluetooth: hci_ll: Add optional nvmem MAC address source
.../devicetree/bindings/net/ti,wilink-st.txt | 4 ++
drivers/bluetooth/hci_ll.c | 43 +++++++++++++++++++++-
2 files changed, 45 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2017-12-04 3:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 3:21 David Lechner [this message]
2017-12-04 3:21 ` [PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st David Lechner
2017-12-04 6:50 ` Marcel Holtmann
2017-12-04 9:54 ` Sergei Shtylyov
2017-12-04 10:09 ` Sergei Shtylyov
2017-12-04 3:21 ` [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command David Lechner
2017-12-04 6:23 ` Marcel Holtmann
2017-12-07 21:29 ` David Lechner
2017-12-07 21:43 ` Marcel Holtmann
2017-12-04 3:21 ` [PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source David Lechner
2017-12-04 6:48 ` 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=1512357682-8911-1-git-send-email-david@lechnology.com \
--to=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo@padovan.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).