From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: enable GPIO fan alarm support for 2Big Network v2
Date: Mon, 23 Feb 2015 18:35:36 +0300 [thread overview]
Message-ID: <54EB48C8.6010506@cogentembedded.com> (raw)
In-Reply-To: <1424696523-14855-1-git-send-email-simon.guinot@sequanux.org>
Hello.
On 2/23/2015 4:02 PM, Simon Guinot wrote:
> On the LaCie 2Big Network v2 (net2big_v2) board, the fan alarm is not
> wired to the I2C fan controller but to a separe GPIO. This GPIO can be
> controlled by using the gpio-fan driver.
> This patch adds the gpio-fan alarm description in the net2big_v2 DTS.
> Signed-off-by: Simon Guinot <simon.guinot@sequanux.org>
> ---
> arch/arm/boot/dts/kirkwood-net2big.dts | 5 +++++
> 1 file changed, 5 insertions(+)
> diff --git a/arch/arm/boot/dts/kirkwood-net2big.dts b/arch/arm/boot/dts/kirkwood-net2big.dts
> index 53dc37a3b687..e4f7e497379f 100644
> --- a/arch/arm/boot/dts/kirkwood-net2big.dts
> +++ b/arch/arm/boot/dts/kirkwood-net2big.dts
> @@ -27,6 +27,11 @@
> device_type = "memory";
> reg = <0x00000000 0x10000000>;
> };
> +
> + gpio_fan {
The ePAPR standard says that node name should be generic, so "fan" would
fit better here...
> + compatible = "gpio-fan";
> + alarm-gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;
> + };
> };
WBR, Sergei
prev parent reply other threads:[~2015-02-23 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:02 [PATCH] ARM: Kirkwood: enable GPIO fan alarm support for 2Big Network v2 Simon Guinot
2015-02-23 14:10 ` Guenter Roeck
2015-02-23 14:40 ` Simon Guinot
2015-02-23 14:49 ` Guenter Roeck
2015-02-25 12:36 ` Simon Guinot
2015-02-25 14:31 ` Guenter Roeck
2015-02-25 15:01 ` Simon Guinot
2015-02-25 16:27 ` Guenter Roeck
2015-02-23 15:35 ` Sergei Shtylyov [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=54EB48C8.6010506@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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).