From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org
Subject: Re: [PATCH 2/3] DT: EVM: add LEDs
Date: Tue, 27 Sep 2016 12:49:05 -0700 [thread overview]
Message-ID: <20160927194904.4im7ukktg5afjmki@atomide.com> (raw)
In-Reply-To: <d68619a23d642eacf12fd0a3c51f19d006436cbe.1474953969.git.hns@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [160926 22:27]:
> + led@6 {
> + label = "omap5:green:led3";
> + gpios = <&gpio9 4 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "heartbeat";
> + default-state = "off";
> + };
> +
> + led@7 {
> + label = "omap5:green:led4";
> + gpios = <&gpio9 5 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "heartbeat";
> + default-state = "off";
> + };
> +
> + led@8 {
> + label = "omap5:green:led5";
> + gpios = <&gpio9 6 GPIO_ACTIVE_HIGH>;
> + linux,default-trigger = "heartbeat";
> + default-state = "off";
> + };
How about this for defaults:
- heartbeat for led3
- cpu0 for led4
- cpu1 for led5
Or something along those lines that by default shows the
active CPUs. Don't have a omap5-uevm near by right now so
not sure about the ordering of the LEDs for displaying
cpu0 and cpu1.
Regards,
Tony
next prev parent reply other threads:[~2016-09-27 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 5:26 [PATCH 0/3] ARM: dts: omap5 uevm: add LEDs, USR1 button and EEPROM H. Nikolaus Schaller
2016-09-27 5:26 ` [PATCH 1/3] DT: EVM: add EEPROM H. Nikolaus Schaller
2016-09-27 5:26 ` [PATCH 2/3] DT: EVM: add LEDs H. Nikolaus Schaller
2016-09-27 19:49 ` Tony Lindgren [this message]
2016-09-27 20:10 ` H. Nikolaus Schaller
2016-09-28 3:37 ` Tony Lindgren
2016-09-28 6:49 ` H. Nikolaus Schaller
2016-09-28 15:12 ` Tony Lindgren
2016-09-28 15:28 ` H. Nikolaus Schaller
2016-09-28 16:12 ` Tony Lindgren
2016-09-29 5:14 ` Rob Herring
2016-09-29 5:18 ` H. Nikolaus Schaller
2016-09-29 5:20 ` H. Nikolaus Schaller
2016-09-27 5:26 ` [PATCH 3/3] DT: EVM: add USR1 button H. Nikolaus Schaller
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=20160927194904.4im7ukktg5afjmki@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®