From: Richard Purdie <rpurdie@rpsys.net>
To: cbou@mail.ru
Cc: kogiidena@eggplant.ddo.jp, linux-kernel@vger.kernel.org,
lethal@linux-sh.org
Subject: Re: [PATCH 1/2] leds:arch/sh/boards/landisk LEDs supports
Date: Mon, 14 May 2007 21:33:36 +0100 [thread overview]
Message-ID: <1179174816.5877.60.camel@localhost.localdomain> (raw)
In-Reply-To: <20070514201256.GB26554@zarina>
On Tue, 2007-05-15 at 00:12 +0400, Anton Vorontsov wrote:
> This change needed for two purposes:
>
> 1. When somebody sets trigger, and that trigger would setup
> brightness in its activate() function, and led driver would check
> if that trigger supported (used by hwtimer trigger and drivers
> supporting hw blinking LEDs, not in mainline yet).
Why does led_cdev->trigger need to be set to do this? Any well written
LED drivers shouldn't need to look at it as the LED drivers shouldn't
have or need any knowledge about specific triggers. If they need this,
you hw blinking abstraction isn't generic.
I had reservations about the hw blinking support last time we discussed
it but I can't remember the specifics of that discussion now without
looking it up. I'm going to hold this patch until we're about the merge
something that needs it, if it really needs it.
> 2. If trigger would access itself through led_cdev in its activate()
> function.
I can't see why you'd need to do this...
> Pros of that patch:
>
> 1. Just sane to do;
> 2. Trivial;
> 3. Can't break anything;
> 4. No new code, just one line movement.
>
> Cons of applying that patch:
>
> 1. No mainline kernel user, but offshores.
2. Encourages bad code ;-).
--
Richard
next prev parent reply other threads:[~2007-05-14 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 12:26 [PATCH 1/2] leds:arch/sh/boards/landisk LEDs supports kogiidena
2007-05-08 12:54 ` Richard Purdie
2007-05-09 14:26 ` kogiidena
2007-05-09 15:13 ` Richard Purdie
2007-05-09 16:03 ` Anton Vorontsov
2007-05-10 11:52 ` kogiidena
2007-05-10 14:04 ` Paul Mundt
2007-05-11 15:03 ` kogiidena
2007-05-12 4:01 ` kogiidena
2007-05-13 23:16 ` Richard Purdie
2007-05-14 19:56 ` Anton Vorontsov
2007-05-14 20:12 ` Anton Vorontsov
2007-05-14 20:33 ` Richard Purdie [this message]
2007-05-14 21:13 ` Anton Vorontsov
2007-05-09 21:48 ` 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=1179174816.5877.60.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=cbou@mail.ru \
--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