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: Wed, 09 May 2007 16:06:24 +0100 [thread overview]
Message-ID: <1178723184.6291.16.camel@localhost.localdomain> (raw)
In-Reply-To: <2329.192.168.1.10.1178718316.squirrel@eggplant.ddo.jp>
On Wed, 2007-05-09 at 22:45 +0900, kogiidena wrote:
> > On Wed, 2007-05-09 at 20:42 +0900, kogiidena wrote:
> >> >As far as I can tell, the existing timer trigger can do everything the
> >> >blink trigger can (and more besides).
> >> I want to blink LED in the initial state.
> >
> > Are you after to set that per LED or would some standard configurable
> > default for all LEDs work?
> I'm sorry.The meaning of the question cannot be understood.
> My LED is use in the following.
> I want to blink LED while booting it.
> When boot ends, LED is turned on.
Your device has more than one LED. Do you need to be able to configure
each LED individually or can they all have the same default settings?
> > The approach is probably a good idea but you'll have to split struct
> > timer_list timer from the data structure.
"struct timer_list timer" in "struct timer_trig_data" is unused when its
used for a default_trigger_data which is wasted space.
> > Also, if default_trigger wasn't the timer trigger you have a nice oops
> > waiting to happen.
> I'm sorry that it is not possible to understand enough.
> Please teach concretely.
You don't check default_trigger == "timer" before using
default_trigger_data.
Imagine we have:
struct led_classdev landisk_leds = {
.name = "power",
.default_trigger = "bitshift",
.default_trigger_data =&default_bitshift_trig_data,
};
where:
struct bitshift_trig_data {
unsigned long single_variable;
};
If you then:
echo "timer" > /sys/class/leds/power/trigger
your patch will use random data and possibly oops.
Regards,
Richard
next prev parent reply other threads:[~2007-05-09 15:06 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
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 [this message]
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=1178723184.6291.16.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®