From: tbm@cyrius.com (Martin Michlmayr)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] orion5x: Set links to solid on D-Link DNS-323
Date: Tue, 25 May 2010 20:04:46 +0100 [thread overview]
Message-ID: <20100525190446.GA27367@jirafa.cyrius.com> (raw)
In-Reply-To: <20100326112030.GA29585@jirafa.cyrius.com>
* Martin Michlmayr <tbm@cyrius.com> [2010-03-26 11:20]:
> Among other changes, commit b2a731aa ("D-link DNS-323 revision A1 power
> LED") changed the default behaviour of the power LED from solid to
> blinking. This was done to match the original DNS-323 firmware which
> blinks during the boot process and sets the LED to solid when booting
> has completed. However, the downside of this behaviour is that it
> requires userland code to change the LED, even for those who don't
> care about the behaviour of the original firmware. Therefore, change
> it to solid again and let those who care about the original behaviour
> change the behaviour from userland.
*ping*
> Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
>
> --- a/arch/arm/mach-orion5x/dns323-setup.c
> +++ b/arch/arm/mach-orion5x/dns323-setup.c
> @@ -262,7 +262,7 @@ static struct gpio_led dns323_leds[] = {
> {
> .name = "power:blue",
> .gpio = DNS323_GPIO_LED_POWER2,
> - .default_trigger = "timer",
> + .default_trigger = "default-on",
> }, {
> .name = "right:amber",
> .gpio = DNS323_GPIO_LED_RIGHT_AMBER,
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Martin Michlmayr
http://www.cyrius.com/
prev parent reply other threads:[~2010-05-25 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 11:20 [PATCH] orion5x: Set links to solid on D-Link DNS-323 Martin Michlmayr
2010-05-25 19:04 ` Martin Michlmayr [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=20100525190446.GA27367@jirafa.cyrius.com \
--to=tbm@cyrius.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).