mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: kogiidena@eggplant.ddo.jp
Cc: linux-kernel@vger.kernel.org, lethal@linux-sh.org
Subject: Re: [PATCH 2/2] leds:arch/sh/boards/landisk LEDs supports
Date: Tue, 08 May 2007 13:46:47 +0100	[thread overview]
Message-ID: <1178628407.6061.24.camel@localhost.localdomain> (raw)
In-Reply-To: <1743.192.168.1.10.1178627225.squirrel@eggplant.ddo.jp>

On Tue, 2007-05-08 at 21:27 +0900, kogiidena wrote:
> I wrote LED Blink Trigger. Pleas apply if there is no problem.
> 
> This allows LEDs to be controlled by a programmable timer.
> "blink" blinks LED at a constant cycle.
> "bitshift" turns LED or Buzzer on and off by the value of pattern.
> 
> Kernel version: linux-2.6.21-rc4
> Signed-off-by: kogiidena <kogiidena@eggplant.ddo.jp>

As far as I can tell, the existing timer trigger can do everything the
blink trigger can (and more besides). The driver looks like it would be
a lot easier to read if it just contained the bitshift trigger. To be
accepted, the bitshift trigger needs more documentation, particularly
the Kconfig entry. Its not clear for example that the bits are just
shifted once and don't repeat. Most people would probably want it to
repeat and with a repeat mode, it might be able to replace the heartbeat
trigger too?

Regards,

Richard





  reply	other threads:[~2007-05-08 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08 12:27 kogiidena
2007-05-08 12:46 ` Richard Purdie [this message]
2007-05-09 11:42   ` kogiidena
2007-05-09 12:14     ` Richard Purdie
2007-05-09 13:45       ` kogiidena
2007-05-09 15:06         ` Richard Purdie
2007-05-09 22:18           ` kogiidena
2007-05-11 15:02             ` kogiidena
2007-05-12  4:01               ` kogiidena

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=1178628407.6061.24.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=kogiidena@eggplant.ddo.jp \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®