From mboxrd@z Thu Jan 1 00:00:00 1970 From: maxime.ripard@free-electrons.com (Maxime Ripard) Date: Sat, 11 Jun 2016 17:45:33 +0200 Subject: [PATCH 1/3] ARM: dts: sun4i: The blue led on the Mele A1000 is a power led In-Reply-To: <0acb666e-3fa7-fb10-4c0d-1d7990f9eaa6@redhat.com> References: <1465129393-22379-1-git-send-email-hdegoede@redhat.com> <20160607212419.GE14179@lukather> <0acb666e-3fa7-fb10-4c0d-1d7990f9eaa6@redhat.com> Message-ID: <20160611154533.GE19854@lukather> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Jun 08, 2016 at 03:23:31PM +0200, Hans de Goede wrote: > Hi, > > On 07-06-16 23:24, Maxime Ripard wrote: > >On Sun, Jun 05, 2016 at 02:23:11PM +0200, Hans de Goede wrote: > >>The blue led on the Mele A1000 is wired to light up as soon as the board > >>has powered (it will be on while the gpio is still in input / floating > >>mode), also its location on the top-set box clearly signals "power led". > >> > >>Until now we've been treating this as a generic usr function led, which > >>means that when you plug power into the top-set box, the power-led lights > >>and then turns off as soon as the kernel loads, which looks wrong. > > > >I'm not sure I understand the relationship between usr vs pwr led and > >the fact that it's disabled. > > There is no relation, other then that pwr leds typically have > default-state = "on"; set whereas usr leds do not. > > >>This renames the led from a1000:blue:usr to a1000:blue:pwr and marks > >>it as default on, fixing this. > > > >however, the default on might. Is it just a confusing commit log, or > >am I overlooking something? > > Just a slightly confusing commit log. Ok, applied all three. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: