linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] driver for the hardware monitoring chip in the Zyxel NSA320
Date: Sun, 28 Feb 2016 22:30:11 +0000	[thread overview]
Message-ID: <1456698614-15176-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 the Zyxel NSA320. It is believed that this is
identical to the one used in the NSA325 and some variants of the NSA310.

 Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt |  21 +++
 Documentation/hwmon/nsa320                             |  53 +++++++
 arch/arm/boot/dts/kirkwood-nsa320.dts                  |  13 +-
 drivers/hwmon/Kconfig                                  |  15 ++
 drivers/hwmon/Makefile                                 |   1 +
 drivers/hwmon/nsa320-hwmon.c                           | 215 ++++++++++++++++++++++++++++
 6 files changed, 316 insertions(+), 2 deletions(-)

---
Changes since v1
Update to reflect linux at roeck-us.netreview comments from Guenter Roeck,
mainly changing it to be nsa320, not nsa3xx but also making it
return an errno on failure and various other tidy ups.

Changes since v2
Update patch 2/3 based on further review from Guenter Roeck, patches
1/3 and 3/3 are unchanged except for adding Rob's Ack to 1/3

             reply	other threads:[~2016-02-28 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 22:30 Adam Baker [this message]
2016-02-28 22:30 ` [PATCH v3 1/3] hwmon: Define binding for the nsa320-hwmon driver Adam Baker
2016-02-28 22:30 ` [PATCH v3 2/3] hwmon: Create an NSA320 hardware monitoring driver Adam Baker
2016-02-29  0:45   ` Guenter Roeck
2016-03-02 23:43     ` Adam Baker
2016-03-03  4:38       ` Guenter Roeck
2016-02-28 22:30 ` [PATCH v3 3/3] ARM: mvebu: Add the hardware monitor to the NSA320 device tree Adam Baker

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=1456698614-15176-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).