All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Kevin Hickey <khickey@rmicorp.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH v2 5/6] Alchemy: DB1300 blink leds on timer tick
Date: Tue, 24 Mar 2009 14:17:07 +0100	[thread overview]
Message-ID: <20090324131707.GA6509@linux-mips.org> (raw)
In-Reply-To: <1237582306-10800-6-git-send-email-khickey@rmicorp.com>

On Fri, Mar 20, 2009 at 03:51:45PM -0500, Kevin Hickey wrote:

> Blinks the dots on the hex display on the DB1300 board every 1000 timer ticks.
> This can help tell the difference between a soft and hard hung board.

How about putting this into a software timer.  The Malta does that for its
ASCII display, see arch/mips/mti-malta/malta-display.c.

  Ralf

  parent reply	other threads:[~2009-03-24 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 20:51 [PATCH v2 0/6] Alchemy: Basic Au1300 and DBAu1300 support Kevin Hickey
2009-03-20 20:51 ` [PATCH v2 1/6] Alchemy: Initial " Kevin Hickey
2009-03-20 20:51   ` [PATCH v2 2/6] Alchemy: Au1300 new interrupt controller Kevin Hickey
2009-03-20 20:51     ` [PATCH v2 3/6] Alchemy: Au1300/DB1300 UART support Kevin Hickey
2009-03-20 20:51       ` [PATCH v2 4/6] Alchemy: Au1300/DB1300 peripheral resource declarations Kevin Hickey
2009-03-20 20:51         ` [PATCH v2 5/6] Alchemy: DB1300 blink leds on timer tick Kevin Hickey
2009-03-20 20:51           ` [PATCH v2 6/6] Alchemy: Au1300: Add LCD framebuffer support Kevin Hickey
2009-03-24 13:17           ` Ralf Baechle [this message]
2009-03-24 15:44             ` [PATCH v2 5/6] Alchemy: DB1300 blink leds on timer tick Atsushi Nemoto
2009-03-24 13:26         ` [PATCH v2 4/6] Alchemy: Au1300/DB1300 peripheral resource declarations Ralf Baechle

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=20090324131707.GA6509@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=khickey@rmicorp.com \
    --cc=linux-mips@linux-mips.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.