From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: mvebu: Add driver for the Zyxel NSA3XX hwmon MCU
Date: Wed, 10 Feb 2016 23:33:41 +0000 [thread overview]
Message-ID: <1455147224-6742-1-git-send-email-linux@baker-net.org.uk> (raw)
This patch series adds a driver to support the hardware monitoring MCU
that is present in some models of the Zyxel NSA3xx series of NAS units.
A patch is included to add it to the device tree for the NSA320 model,
patches to the other device trees will be included if testers come
forward (I already have a possible tester for NSA325).
There are no dependencies between the patches so I guess the first two
should go via the hardware monitoring maintainers and the third via
the ARM mvebu maintainers.
[PATCH 1/3] Define a binding for the hardware monitoring chip present
[PATCH 2/3] Create a driver to support the hardware monitoring chip
[PATCH 3/3] Add an entry for the hardware monitoring MCU
Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt | 21 ++++++++
arch/arm/boot/dts/kirkwood-nsa320.dts | 13 ++++-
drivers/hwmon/Kconfig | 13 +++++
drivers/hwmon/Makefile | 1 +
drivers/hwmon/nsa3xx-hwmon.c | 223 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 269 insertions(+), 2 deletions(-)
next reply other threads:[~2016-02-10 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 23:33 Adam Baker [this message]
2016-02-10 23:33 ` [PATCH 1/3] ARM: mvebu: Define binding for the nsa3xx-hwmon driver Adam Baker
2016-02-12 15:59 ` Rob Herring
2016-02-10 23:33 ` [PATCH 2/3] ARM: mvebu: Create a NSA3xx hardware monitoring driver Adam Baker
2016-02-13 2:35 ` Guenter Roeck
2016-02-15 23:08 ` Adam Baker
2016-02-10 23:33 ` [PATCH 3/3] ARM: mvebu: Add the hardware monitor to the NSA320 device tree Adam Baker
2016-02-12 16:35 ` [PATCH 0/3] ARM: mvebu: Add driver for the Zyxel NSA3XX hwmon MCU Gregory CLEMENT
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=1455147224-6742-1-git-send-email-linux@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).