All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: David Pye <dmp@davidmpye.dyndns.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] J5000 LED LCD patch (take 2)
Date: Sun, 27 Mar 2005 19:13:10 -0700	[thread overview]
Message-ID: <20050328021310.GC30963@colo.lackof.org> (raw)
In-Reply-To: <200503271038.42434.dmp@davidmpye.dyndns.org>

On Sun, Mar 27, 2005 at 09:38:38AM +0000, David Pye wrote:
> > I think I would be ok with it implemented inside the led_get*
> > activity routines. They have access to lastleds and jiffies and
> > that should be enough to figure out how long an LED should stay
> > on if it's already on.  The main routine can stay simple/readable.
> 
> Yep, I hadn't really thought of doing it in there - I'll have a play with it 
> and maybe annoy everyone with another patch in a bit.   Downside is that it's 
> not really the right place to put it *if* you want it to be lcd-only.

I don't really care if it's LCD only.
LCD clearly has different response times than LED.

> The only other way to do it which you might not find as ugly is to move this 
> into the drivers.  ie the drivers would need to be given the responsibility 
> of deciding whether they need to update anything (ie each of them has to 
> store currentleds rather than the generic calculator function). That way, 
> they'll get called each time the work runs, but can decide for themselves 
> whether to actually do anything.  It's only a couple of lines to add to the 
> other functions e.g. lasi.   How does that sound?

Yeah - having the LCD_driver regulate minimum on probably makes just as
much sense since LED really doesn't need it.

Implementing it in led_get* routines was just my first thought.
led_get* controls state of the LEDs and could avoid extra calculations
if it knows about minimum-on time. 
Maybe minimum-on time should be a parameter that's different for LED/LCD
if a hardcoded value isn't acceptable for both.

thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

      parent reply	other threads:[~2005-03-28  2:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 18:48 [parisc-linux] J5000 LED LCD patch (take 2) David Pye
2005-03-24 20:01 ` [parisc-linux] A second LCD patch David Pye
2005-03-24 20:05 ` [parisc-linux] J5000 LED LCD patch (take 2) James Bottomley
2005-03-24 21:00   ` David Pye
2005-03-25  6:25     ` Grant Grundler
2005-03-25 17:05       ` David Pye
2005-03-25 21:50         ` David Pye
2005-03-26  7:13           ` Grant Grundler
2005-03-26 15:14             ` David Pye
2005-03-26 15:33               ` James Bottomley
     [not found]                 ` <200503261545.05372.dmp@davidmpye.dyndns.org>
2005-03-26 15:51                   ` David Pye
2005-03-27  8:53               ` Grant Grundler
2005-03-27  9:38                 ` David Pye
2005-03-27 17:55                   ` David Pye
2005-03-28  1:51                     ` Grant Grundler
2005-03-28  2:13                   ` Grant Grundler [this message]

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=20050328021310.GC30963@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=dmp@davidmpye.dyndns.org \
    --cc=parisc-linux@lists.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.