From: Danny Kukawka <danny.kukawka@web.de>
To: hal@lists.freedesktop.org
Cc: Corentin Chary <corentin.chary@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
acpi4asus-user@lists.sourceforge.net,
Alan Jenkins <sourcejedi.lkml@googlemail.com>,
linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: Illuminated keyboard on ASUS U50VG laptop, backlight or led ?
Date: Thu, 6 Aug 2009 12:48:39 +0200 [thread overview]
Message-ID: <200908061248.40340.danny.kukawka@web.de> (raw)
In-Reply-To: <200908061207.12450.corentin.chary@gmail.com>
On Donnerstag, 6. August 2009, Corentin Chary wrote:
> Hi Danny,
> I was trying to add keyboard_backlight.num_levels support for your modified
> led-addon. But there is something I don't understand :-
> keyboard_backlight.num_levels is used in:
> - examples/light_sensors_and_keyboard_backlight.py
> - fdi/policy/10osvendor/10-macbookpro-utils.fdi
> - kde/solid/hal/halpower.cpp
> But it is not defined in doc/spec/hal-spec-properties.xml.
>
> Should I make another patch to fix hal-spec-properties ?
Can you please provide a "grep . */*" from /sys/class/leds/ with the affected
device? If I read the kernel doc for leds (which this device is), we don't
need a num_levels for it:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/leds-class.txt;h=6399557cdab3d6542a0feea0c0cd2c6b2af5ffad;hb=HEAD
"... The brightness file will set the brightness of the LED (taking a value
0-255). Most LEDs don't have hardware brightness support so will just be
turned on for non-zero brightness settings. ..."
Danny
next prev parent reply other threads:[~2009-08-06 10:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 7:34 Illuminated keyboard on ASUS U50VG laptop, backlight or led ? Corentin Chary
2009-07-28 19:51 ` Corentin Chary
2009-07-28 20:04 ` Matthew Garrett
2009-08-01 10:40 ` Corentin Chary
2009-08-01 11:19 ` Alan Jenkins
2009-08-01 12:40 ` Corentin Chary
2009-08-01 13:21 ` Danny Kukawka
2009-08-01 15:50 ` Corentin Chary
2009-08-01 16:30 ` Alan Jenkins
2009-08-01 17:21 ` Danny Kukawka
2009-08-01 19:43 ` Alan Jenkins
2009-08-01 19:47 ` Alan Jenkins
2009-08-02 7:20 ` Corentin Chary
2009-08-06 10:07 ` Corentin Chary
2009-08-06 10:48 ` Danny Kukawka [this message]
2009-08-06 11:59 ` Corentin Chary
2009-08-06 16:20 ` Danny Kukawka
2009-08-06 17:00 ` Corentin Chary
2009-12-07 7:51 ` Corentin Chary
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=200908061248.40340.danny.kukawka@web.de \
--to=danny.kukawka@web.de \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=hal@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=sourcejedi.lkml@googlemail.com \
/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