From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ARM: mvebu: Add the hardware monitor to the NSA320 device tree
Date: Mon, 15 Feb 2016 23:25:04 +0000 [thread overview]
Message-ID: <1455578705-10531-4-git-send-email-linux@baker-net.org.uk> (raw)
In-Reply-To: <1455578705-10531-1-git-send-email-linux@baker-net.org.uk>
Add an entry for the hardware monitoring MCU
Signed-off-by: Adam Baker <linux@baker-net.org.uk>
---
arch/arm/boot/dts/kirkwood-nsa320.dts | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/kirkwood-nsa320.dts b/arch/arm/boot/dts/kirkwood-nsa320.dts
index 24f686d..2a935e9 100644
--- a/arch/arm/boot/dts/kirkwood-nsa320.dts
+++ b/arch/arm/boot/dts/kirkwood-nsa320.dts
@@ -193,10 +193,19 @@
};
};
+ hwmon {
+ compatible = "zyxel,nsa320-mcu";
+ pinctrl-0 = <&pmx_mcu_data &pmx_mcu_clk &pmx_mcu_act>;
+ pinctrl-names = "default";
+
+ data-gpios = <&gpio0 14 GPIO_ACTIVE_HIGH>;
+ clk-gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
+ act-gpios = <&gpio0 17 GPIO_ACTIVE_LOW>;
+ };
+
/* The following pins are currently not assigned to a driver,
some of them should be configured as inputs.
- pinctrl-0 = <&pmx_mcu_data &pmx_mcu_clk &pmx_mcu_act
- &pmx_htp &pmx_vid_b1
+ pinctrl-0 = <&pmx_htp &pmx_vid_b1
&pmx_power_resume_data &pmx_power_resume_clk>; */
};
--
2.1.4
prev parent reply other threads:[~2016-02-15 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 23:25 [PATCH v2] A driver for the hardware monitoring chip in the Zyxel NSA320 Adam Baker
2016-02-15 23:25 ` [PATCH v2 1/3] hwmon: Define binding for the nsa320-hwmon driver Adam Baker
2016-02-16 1:48 ` Guenter Roeck
2016-02-15 23:25 ` [PATCH v2 2/3] hwmon: Create an NSA320 hardware monitoring driver Adam Baker
2016-02-16 2:13 ` Guenter Roeck
2016-02-28 22:44 ` Adam Baker
2016-02-28 23:22 ` Guenter Roeck
2016-02-15 23:25 ` Adam Baker [this message]
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=1455578705-10531-4-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).