All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: corentincj@iksaif.net
Cc: linux-acpi@vger.kernel.org, acpi4asus-user@lists.sourceforge.net
Subject: Re: [patch 2/7] asus-laptop: add led support
Date: Fri, 26 Jan 2007 02:43:25 -0500	[thread overview]
Message-ID: <200701260243.25372.lenb@kernel.org> (raw)
In-Reply-To: <200701251254.43674.corentincj@iksaif.net>

On Thursday 25 January 2007 06:54, Corentin CHARY wrote:
> Add led support, using generic led class.
> Thomas Tuttle's patch <http://lkml.org/lkml/2006/7/6/247> was very usefull.
> We use hotk->status to store led status because it's very hard to find acpi method
> to get the right status...
> To reduce the code, I use a lot of macro (ASUS_LED, ASUS_LED_REGISTER, etc ...), because
> the code is the same for all leds ...
> 
> Signed-off-by: Corentin Chary <corentincj@iksaif.net>
>  Kconfig       |    1
>  asus-laptop.c |  146 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 147 insertions(+)
> ---
> 
> diff -Naur a/drivers/misc/asus-laptop.c b/drivers/misc/asus-laptop.c
...
> diff -Naur a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> --- a/drivers/misc/Kconfig	2007-01-21 15:27:49.000000000 +0100
> +++ b/drivers/misc/Kconfig	2007-01-21 15:24:26.000000000 +0100
> @@ -74,6 +74,7 @@
>          depends on X86
>          depends on ACPI
>  	depends on EXPERIMENTAL && !ASUS_ACPI
> +	select LEDS_CLASS

Why isn't this depends on BACKLIGHT_CLASS_DEVICE
like msi-laptop?

>          ---help---
>  	  This is the new Linux driver for Asus laptops. It may also support some
>  	  MEDION, JVC or VICTOR laptops. It makes all the extra buttons generate
> 

  reply	other threads:[~2007-01-26  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 11:54 [patch 2/7] asus-laptop: add led support Corentin CHARY
2007-01-26  7:43 ` Len Brown [this message]
2007-01-26 13:04 ` 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=200701260243.25372.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentincj@iksaif.net \
    --cc=linux-acpi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.