From: Daniel Mack <daniel@zonque.org>
To: zbr@ioremap.net, robh+dt@kernel.org, mark.rutland@arm.com,
szabolcs.gyurko@tlt.hu
Cc: sre@kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
robert.jarzmik@free.fr, Daniel Mack <daniel@zonque.org>
Subject: [PATCH v3 0/4] Add devicetree functionality to w1 busses and ds2760
Date: Fri, 29 Jun 2018 19:31:33 +0200 [thread overview]
Message-ID: <20180629173137.12690-1-daniel@zonque.org> (raw)
This patch set contains four small patches that bring devicetree
functionality to w1 bus masters and slaves in general. As an example,
the DS2760 driver is made aware of devicetree nodes as an example.
Other drivers can easily be ported later.
W1 masters scan their bus in order to discover slave devices. Once
one is found, a driver matching the family of the device is instanciated
which handles it.
All that's needed for now is a call to of_find_matching_node() when
a slave device is attached, so the corresponding of_node pointer is
set.
The series also contains a patch that merges the w1 slave driver for the
DS2760 battery monitor into its only user, the ds2760 supply driver.
The indirection with two drivers never had any benefit, and here is
a good opportunity to clean this up.
Patch #1 adds some DT bindings documentation
Patch #2 adds the call to of_find_matching_node()
Patch #3 merges the w1 slave and the supply driver for ds2760
Patch #4 makes the ds2760 supply driver aware of DT environments
This works fine on a PXA3xx based board with a battery attached to
the w1-gpio bus master controller.
Daniel Mack (4):
dt-bindings: w1: document sub-node bindings for DS2760
w1: core: match sub-nodes of bus masters in devicetree
w1: ds2760: add devicetree matching glue
power: ds2760_battery: add device tree glue
.../devicetree/bindings/w1/maxim,ds2760.txt | 15 +++++++++++++++
.../devicetree/bindings/w1/w1-gpio.txt | 6 ++++++
Documentation/devicetree/bindings/w1/w1.txt | 18 ++++++++++++++++++
drivers/power/supply/ds2760_battery.c | 6 +++++-
drivers/w1/slaves/w1_ds2760.c | 9 +++++++++
drivers/w1/w1.c | 3 +++
include/linux/w1.h | 2 ++
7 files changed, 58 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/w1/maxim,ds2760.txt
create mode 100644 Documentation/devicetree/bindings/w1/w1.txt
--
2.17.1
next reply other threads:[~2018-06-29 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 17:31 Daniel Mack [this message]
2018-06-29 17:31 ` [PATCH v3 1/4] dt-bindings: w1: document generic onewire and DS2760 bindings Daniel Mack
2018-06-29 17:31 ` [PATCH v3 2/4] w1: core: match sub-nodes of bus masters in devicetree Daniel Mack
2018-06-29 17:31 ` [PATCH v3 3/4] power: supply: ds2760_battery: merge ds2760 supply driver with its w1 slave companion Daniel Mack
2018-06-29 17:31 ` [PATCH v3 4/4] power: supply: ds2760_battery: add devicetree probing Daniel Mack
2018-06-29 17:35 ` [PATCH v3 0/4] Add devicetree functionality to w1 busses and ds2760 Daniel Mack
-- strict thread matches above, loose matches on Subject: below --
2018-07-04 4:44 Daniel Mack
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=20180629173137.12690-1-daniel@zonque.org \
--to=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=szabolcs.gyurko@tlt.hu \
--cc=zbr@ioremap.net \
/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