From: Johannes Engel <j-engel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Integrate asus_acpi LED's with new LED subsystem
Date: Mon, 24 Jul 2006 23:24:53 +0200 [thread overview]
Message-ID: <ea3dr9$q5t$1@sea.gmane.org> (raw)
In-Reply-To: <20060707012025.GB8900@phoenix>
Thomas Tuttle schrieb:
> Here is a patch to the asus_acpi driver that links the Asus laptop LED's
> into the new LED subsystem. It creates LED class devices named
> asus:mail, asus:wireless, and asus:touchpad, depending on if the laptop
> supports the mled, wled, and tled LED's.
>
> Since it's so new, I added a config option to turn it on and off. It's
> worked for me, though I have an Asus M2N, which only has the mail and
> wireless LED's.
>
> Signed-off-by: Thomas Tuttle <thinkinginbinary@gmail.com>
>
>
> I believe I've fixed everything you asked about, plus a few things
> Richard Purdie (the LED subsystem guy) suggested.
>
Thanks, Thomas, for your patch. It works well for me (ASUS V6V).
There is only one thing I want to remark: Since the most recent BIOS
ASUS changed the behaviour of the touchpad LED, it is inverted now.
Until now I got around this in userspace (adapting the handler script).
But with the new led class it seems to me, we will have to deal with
that in the kernel module.
My suggestion is a new flag (tled_inv) which has to be set for every
model (always use most recent BIOS). What do you think about this?
Greetings, Johannes
next prev parent reply other threads:[~2006-07-24 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 19:31 [PATCH] Integrate asus_acpi LED's with new LED subsystem Thomas Tuttle
2006-07-06 22:39 ` Richard Purdie
2006-07-07 1:11 ` Thomas Tuttle
2006-07-06 22:49 ` Andrew Morton
2006-07-07 1:20 ` Thomas Tuttle
2006-07-07 8:46 ` Richard Purdie
2006-07-24 21:24 ` Johannes Engel [this message]
2006-07-06 23:50 ` Pavel Machek
2006-07-07 1:44 ` Thomas Tuttle
2006-07-07 9:38 ` Pavel Machek
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='ea3dr9$q5t$1@sea.gmane.org' \
--to=j-engel@gmx.de \
--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