linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: NSA310 + DT
Date: Wed, 31 Jul 2013 13:47:44 +0200	[thread overview]
Message-ID: <20130731134744.2d8830f0@skate> (raw)
In-Reply-To: <51F8F7E3.9090404@uni-bremen.de>

Dear Finn Hoffmann,

On Wed, 31 Jul 2013 13:41:23 +0200, Finn Hoffmann wrote:

> I have a question about LED's:
> Is it possible to have the powerled blinking while kernel is loading? 
> Right now all LED's are turned off when the kernel starts.

Yes, you can set a default trigger for GPIO LEDs. Just edit the
kirkwood-nsa310.dts file and add:

	linux,default-trigger	= "heartbeat";

into the GPIO LED that you want to see blinking once the kernel is
running. Note that it won't be blinking while the kernel is loading
(because loading the kernel is done by the bootloader), but it will
start blinking as soon as the kernel has initialized the GPIO LEDs.

> I came across one curious thing: With Andrews kernel I had:
> $ sensors
> adt7476-i2c-0-2e
> Adapter: mv64xxx_i2c adapter
> in0: +1.82 V (min = +0.00 V, max = +3.31 V)
> in1: +1.09 V (min = +0.00 V, max = +2.99 V)
> in2: +3.27 V (min = +2.98 V, max = +3.63 V)
> in3: +5.12 V (min = +4.53 V, max = +5.52 V)
> in4: +11.98 V (min = +0.00 V, max = +15.69 V)
> fan1: 4330 RPM (min = 0 RPM)
> fan2: 0 RPM (min = 0 RPM)
> fan3: 0 RPM (min = 0 RPM)
> fan4: 0 RPM (min = 0 RPM)
> temp1: +32.2??C (low = -127.0??C, high = +127.0??C)
> (crit = +100.0??C, hyst = +96.0??C)
> temp2: +32.5??C (low = -127.0??C, high = +127.0??C)
> (crit = +100.0??C, hyst = +96.0??C)
> temp3: +41.0??C (low = -127.0??C, high = +127.0??C)
> (crit = +100.0??C, hyst = +96.0??C)
> cpu0_vid: +0.000 V
> 
> normally I have:
> # sensors
> lm85-i2c-0-2e
> Adapter: mv64xxx_i2c adapter
> in0: +1.82 V (min = +0.00 V, max = +3.32 V)
> Vcore: +1.07 V (min = +0.00 V, max = +2.99 V)
> +3.3V: +3.25 V (min = +2.97 V, max = +3.63 V)
> +5V: +5.05 V (min = +4.50 V, max = +5.50 V)
> +12V: +12.12 V (min = +0.00 V, max = +15.94 V)
> fan1: 2480 RPM (min = 0 RPM)
> temp1: +35.0?C (low = -127.0?C, high = +127.0?C)
> temp2: +34.0?C (low = -127.0?C, high = +127.0?C)
> temp3: +47.0?C (low = -127.0?C, high = +127.0?C)

I am not sure to understand which one you believe is correct and which
one is wrong, and how the wrong one is wrong. But I don't have much
sensor experience, maybe Andrew has more knowledge than me on this
stuff.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-07-31 11:47 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 [this message]
2013-07-31 16:45                                     ` Andrew Lunn
2013-08-01  8:01                                       ` Finn Hoffmann
2013-08-01 16:04                                         ` Andrew Lunn
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=20130731134744.2d8830f0@skate \
    --to=thomas.petazzoni@free-electrons.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).