All of lore.kernel.org
 help / color / mirror / Atom feed
From: wens@csie.org (Chen-Yu Tsai)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH 4/6] ARM: dts: sun9i: Add GPIO LEDs for A80 Optimus board
Date: Wed, 29 Oct 2014 09:54:10 +0800	[thread overview]
Message-ID: <CAGb2v64t3hdAk4NRioqpFBS++VzvU_26hzgG14ucTgnho7MANg@mail.gmail.com> (raw)
In-Reply-To: <20141028202708.GB9255@lukather>

On Wed, Oct 29, 2014 at 4:27 AM, Maxime Ripard
<maxime.ripard@free-electrons.com> wrote:
> On Tue, Oct 28, 2014 at 12:04:28PM +0100, Koen Kooi wrote:
>>
>> > Op 28 okt. 2014, om 10:50 heeft Chen-Yu Tsai <wens@csie.org> het volgende geschreven:
>> >
>> > The A80 Optimus board has 3 usable LEDs that are controlled via GPIO.
>> >
>> > This patch adds support for 2 of them which are driver by GPIOs in the
>> > main pin controller. The remaining one uses GPIO from the R_PIO
>> > controller, which we don't support yet.
>>
>> Out of curiousity, are those LEDs labeled and if so, would it make
>> sense to assign default triggers matching the labels to them? As a
>> personal preference I tend to have one of the LEDs use the
>> 'heartbeat' trigger so I can see that it's alive.

They are not labeled in any meaningful way (LED2~4), are next to each
other, and are all the same color. Not very helpful. :|

The stock firmware uses them for mmc0, mmc1, and sleep activity.

> I'm not a huge fan of forcing this kind of policy decision down to the
> users, especially for such "generic" boards that don't have any
> labeled LEDs.
>
> I feel like it's a userspace decision, but I don't have a strong
> opinion on this :)

If the LEDs were more distinguishable from each other, I would go for
a default behavior. But that is not the case.

ChenYu

  reply	other threads:[~2014-10-29  1:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28  9:50 [PATCH 0/6] ARM: sun9i: Enable extra uarts, leds and i2c controllers Chen-Yu Tsai
2014-10-28  9:50 ` [PATCH 1/6] ARM: dts: sun9i: Add i2c controller nodes to a80 dtsi Chen-Yu Tsai
2014-10-28  9:50 ` [PATCH 2/6] ARM: dts: sun9i: Add i2c3 pinmux setting for A80 SoC Chen-Yu Tsai
2014-10-28  9:50 ` [PATCH 3/6] ARM: dts: sun9i: Enable i2c3 on A80 Optimus board Chen-Yu Tsai
2014-10-28  9:50 ` [PATCH 4/6] ARM: dts: sun9i: Add GPIO LEDs for " Chen-Yu Tsai
2014-10-28 11:04   ` [linux-sunxi] " Koen Kooi
2014-10-28 20:27     ` Maxime Ripard
2014-10-29  1:54       ` Chen-Yu Tsai [this message]
2014-10-28 20:16   ` Maxime Ripard
2014-10-28 21:19     ` Andreas Färber
2014-10-29  2:02       ` Chen-Yu Tsai
2014-10-30 15:53       ` Maxime Ripard
2014-10-29  1:50     ` Chen-Yu Tsai
2014-10-28  9:50 ` [PATCH 5/6] ARM: dts: sun9i: Add uart4 pinmux setting for A80 SoC Chen-Yu Tsai
2014-10-28  9:50 ` [PATCH 6/6] ARM: dts: sun9i: Enable uart4 for A80 Optimus board Chen-Yu Tsai

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=CAGb2v64t3hdAk4NRioqpFBS++VzvU_26hzgG14ucTgnho7MANg@mail.gmail.com \
    --to=wens@csie.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.