From: Helge Deller <deller@gmx.de>
To: Thibaut VARENE <varenet@parisc-linux.org>,
Kyle McMartin <kyle@infradead.org>
Cc: linux-parisc@vger.kernel.org
Subject: Re: commit mail stuff
Date: Fri, 30 Jan 2009 21:27:50 +0100 [thread overview]
Message-ID: <498362C6.5060309@gmx.de> (raw)
In-Reply-To: <7d01f9f00901220323u2898ae25hf149c65956fc2a4e@mail.gmail.com>
Thibaut VARENE wrote:
> On Wed, Jan 21, 2009 at 3:31 PM, Kyle McMartin <kyle@infradead.org> wrote:
>
>> commit 1890e15142aa1318bb9775c4ea021aa022c506dc
>> Author: Helge Deller <deller@gmx.de>
>> Date: Tue Jan 6 14:23:13 2009 +0100
>>
>> parisc: blink loadavg LEDs on Oops
>>
>
> I thought we agreed this was a bad idea and that this patch should be
> left aside?
> Helge?
Yes, that was an idea.
But we can easily detect which kind of machine it is, and then
either blink all LEDs or just the loadavg. LEDs. The patch below
does this and should be then fine for you?
Kyle, could you apply the patch below as well?
Helge
------------------------------------------------------------
parisc: blink all or loadavg. LEDs on Oops depending on machine type.
Signed-off-by: Helge Deller <deller@gmx.de>
diff --git a/drivers/parisc/led.c b/drivers/parisc/led.c
index 6d8753e..d6026d4 100644
--- a/drivers/parisc/led.c
+++ b/drivers/parisc/led.c
@@ -463,12 +463,19 @@ static void led_work_func (struct work_struct *unused)
if (likely(led_lanrxtx)) currentleds |= led_get_net_activity();
if (likely(led_diskio)) currentleds |= led_get_diskio_activity();
- /* blink loadavg LEDs twice per second if we got an Oops (HPMC) */
+ /* blink LEDs if we got an Oops (HPMC) */
if (unlikely(oops_in_progress)) {
- if (count_HZ <= (HZ/2))
- currentleds &= ~(LED4|LED5|LED6|LED7);
- else
- currentleds |= (LED4|LED5|LED6|LED7);
+ if (boot_cpu_data.cpu_type >= pcxl2) {
+ /* newer machines don't have loadavg. LEDs, so we
+ * let all LEDs blink twice per second instead */
+ currentleds = (count_HZ <= (HZ/2)) ? 0 : 0xff;
+ } else {
+ /* old machines: blink loadavg. LEDs twice per second */
+ if (count_HZ <= (HZ/2))
+ currentleds &= ~(LED4|LED5|LED6|LED7);
+ else
+ currentleds |= (LED4|LED5|LED6|LED7);
+ }
}
if (currentleds != lastleds)
next prev parent reply other threads:[~2009-01-30 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 14:31 commit mail stuff Kyle McMartin
2009-01-21 18:53 ` Helge Deller
2009-01-22 20:10 ` Kyle McMartin
2009-01-22 11:23 ` Thibaut VARENE
2009-01-22 17:43 ` Kyle McMartin
2009-01-22 18:36 ` Thibaut VARENE
2009-01-30 20:27 ` Helge Deller [this message]
2009-01-30 22:34 ` Thibaut VARENE
2009-04-02 0:31 ` Kyle McMartin
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=498362C6.5060309@gmx.de \
--to=deller@gmx.de \
--cc=kyle@infradead.org \
--cc=linux-parisc@vger.kernel.org \
--cc=varenet@parisc-linux.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.