From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: NSA310 + DT
Date: Thu, 1 Aug 2013 18:04:14 +0200 [thread overview]
Message-ID: <20130801160414.GI19725@lunn.ch> (raw)
In-Reply-To: <51FA15F3.7050708@uni-bremen.de>
> The LED's on after kernel is loaded, while starting up does not work.
> pmx_led_sys_green: pmx-led-sys-green {
> marvell,pins = "mpp28";
> marvell,function = "gpio";
> linux,default-trigger = "heartbeat";
> brightness = <255>;
> };
> I first tried default-trigger, then I added brightness additionally
> but LED's wont turn on.
Can you manually turn the LED on, using /sys/class/led/.../brightness?
It could be we have the wrong GPIO line for the led. It would be good
if you could test them all, not just this one led.
> There is no sata hdd trigger and nand-disk does not trigger on sata
> hdd activity.
They are out of tree patches. There was some discussion about SATA led
activity maybe 6 to 9 months ago. Maybe you can see why the suggested
patches got rejected. If i remember correctly, it was because they are
in the hot path.
Andrew
next prev parent reply other threads:[~2013-08-01 16:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51DC564A.8050002@harsszegi.com>
2013-07-09 19:36 ` NSA310 + DT Andrew Lunn
2013-07-09 20:21 ` Andrew Lunn
2013-07-10 0:53 ` tibor at harsszegi.com
2013-07-10 6:23 ` Andrew Lunn
2013-07-10 8:42 ` tibor at harsszegi.com
2013-07-10 13:41 ` Andrew Lunn
[not found] ` <51DD8E8B.2040505@harsszegi.com>
2013-07-10 16:44 ` Tibor Harsszegi
2013-07-10 16:53 ` Andrew Lunn
2013-07-10 16:57 ` Tibor Harsszegi
2013-07-10 17:13 ` Tibor Harsszegi
2013-07-10 17:15 ` Tibor Harsszegi
2013-07-10 17:23 ` Andrew Lunn
2013-07-10 17:29 ` Tibor Harsszegi
2013-07-10 1:01 ` tibor at harsszegi.com
2013-07-10 7:37 ` Andrew Lunn
2013-07-10 8:43 ` tibor at harsszegi.com
[not found] ` <51DEDB32.4080101@harsszegi.com>
2013-07-11 16:44 ` gpio_blink_set + Kirkwood Andrew Lunn
2013-07-11 18:32 ` Tibor Harsszegi
2013-07-11 18:37 ` Jason Cooper
2013-07-11 18:52 ` Tibor Harsszegi
2013-07-11 19:44 ` Jason Cooper
2013-07-29 17:05 ` NSA310 + DT Finn Hoffmann
2013-07-29 19:21 ` Jason Cooper
2013-07-29 20:43 ` Andrew Lunn
[not found] ` <51F78DA6.8010307@uni-bremen.de>
[not found] ` <20130730144752.GR24782@lunn.ch>
[not found] ` <20130730172407.3aab15c6@skate>
[not found] ` <51F7EBB9.7000504@uni-bremen.de>
[not found] ` <20130730191943.49f8070c@skate>
2013-07-30 18:36 ` Andrew Lunn
2013-07-30 19:31 ` Finn Hoffmann
2013-07-30 19:42 ` Andrew Lunn
2013-07-30 21:23 ` Thomas Petazzoni
2013-07-31 9:14 ` Thomas Petazzoni
2013-07-31 9:43 ` Finn Hoffmann
2013-07-31 9:51 ` Thomas Petazzoni
2013-07-31 11:41 ` Finn Hoffmann
2013-07-31 11:47 ` Thomas Petazzoni
2013-07-31 16:45 ` Andrew Lunn
2013-08-01 8:01 ` Finn Hoffmann
2013-08-01 16:04 ` Andrew Lunn [this message]
2013-08-01 20:43 ` Finn Hoffmann
2013-08-02 8:35 ` Finn Hoffmann
2013-08-02 8:46 ` Thomas Petazzoni
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=20130801160414.GI19725@lunn.ch \
--to=andrew@lunn.ch \
--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.