From: David Vrabel <dvrabel@cantab.net>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>, John Lenz <lenz@cs.wisc.edu>,
Pavel Machek <pavel@suse.cz>
Subject: Re: [RFC PATCH 1/8] LED: Add LED Class
Date: Mon, 05 Dec 2005 14:59:08 +0000 [thread overview]
Message-ID: <439455BC.4080908@cantab.net> (raw)
In-Reply-To: <1133788166.8101.125.camel@localhost.localdomain>
This LED subsystem isn't usable with LEDs that are controlled by I2C
GPIO devices. Getting rid of (struct led_device).lock would go some way
to making it work. It's not clear to me why it's needed anyway.
Suspend and resume probably needs to be LED specific.
Richard Purdie wrote:
> Index: linux-2.6.15-rc2/drivers/leds/Kconfig
> ===================================================================
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ linux-2.6.15-rc2/drivers/leds/Kconfig 2005-12-05 11:29:19.000000000 +0000
> @@ -0,0 +1,18 @@
> +
> +menu "LED devices"
> +
> +config NEW_LEDS
Is there a better name than NEW_LEDS? It won't be 'new' for very long...
> Index: linux-2.6.15-rc2/include/linux/leds.h
> ===================================================================
> --- /dev/null 1970-01-01 00:00:00.000000000 +0000
> +++ linux-2.6.15-rc2/include/linux/leds.h 2005-12-05 11:29:19.000000000 +0000
> [...]
> + /* A function to set the brightness of the led.
> + * Values are between 0-100 */
> + void (*brightness_set)(struct led_device *led_dev, int value);
0-255 is probably a better range to use. Might be worth having an enum
like.
enum led_brightness {
LED_OFF = 0, LED_HALF_BRIGHT = 127, LED_FULL_BRIGHT = 255,
};
David Vrabel
next prev parent reply other threads:[~2005-12-05 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 13:09 [RFC PATCH 1/8] LED: Add LED Class Richard Purdie
2005-12-05 14:59 ` David Vrabel [this message]
2005-12-05 15:38 ` Richard Purdie
2005-12-05 17:02 ` Pavel Machek
2005-12-06 21:20 ` Greg KH
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=439455BC.4080908@cantab.net \
--to=dvrabel@cantab.net \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
/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