From: Scott Branden <scott.branden@broadcom.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Scott Branden <scott.branden@broadcom.com>
Subject: [PATCH 0/3] Add Support for Broadcom D1W controller
Date: Wed, 16 Aug 2017 10:45:22 -0700 [thread overview]
Message-ID: <1502905525-5646-1-git-send-email-scott.branden@broadcom.com> (raw)
Add support for Broadcom Dallas One wire (D1W) bus master controller.
This patch series adds a callback for the ds1wm read/write functions
to the common DS1W driver code and the Broadcom specific DS1W controller.
Shreesha Rajashekar (3):
dt-bindings: mfd: d1w: iproc: Documentation for d1w driver
w1: d1w: Provide callback for ds1wm read/write
mfd: d1w: iproc: Add d1w driver
.../devicetree/bindings/mfd/brcm,iproc-d1w.txt | 27 +++
drivers/mfd/Kconfig | 11 ++
drivers/mfd/Makefile | 1 +
drivers/mfd/bcm-iproc-d1w.c | 202 +++++++++++++++++++++
drivers/w1/masters/ds1wm.c | 18 +-
include/linux/mfd/ds1wm.h | 2 +
6 files changed, 259 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/brcm,iproc-d1w.txt
create mode 100644 drivers/mfd/bcm-iproc-d1w.c
--
2.5.0
next reply other threads:[~2017-08-16 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 17:45 Scott Branden [this message]
2017-08-16 17:45 ` [PATCH 1/3] dt-bindings: mfd: d1w: iproc: Documentation for d1w driver Scott Branden
2017-08-16 20:45 ` Rob Herring
2017-08-17 18:20 ` Scott Branden
2017-08-16 17:45 ` [PATCH 2/3] w1: d1w: Provide callback for ds1wm read/write Scott Branden
2017-08-17 1:10 ` Florian Fainelli
2017-08-16 17:45 ` [PATCH 3/3] mfd: d1w: iproc: Add d1w driver Scott Branden
2017-08-17 10:02 ` Lee Jones
2017-08-17 18:19 ` Scott Branden
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=1502905525-5646-1-git-send-email-scott.branden@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®