From: "Éric Piel" <Eric.Piel@tremplin-utc.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
mitr@volny.cz, Ivo van Doorn <ivdoorn@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 3/5] wistron_btns: add led support
Date: Thu, 26 Apr 2007 23:25:59 +0200 [thread overview]
Message-ID: <463118E7.3030902@tremplin-utc.net> (raw)
In-Reply-To: <d120d5000704260850m788af054pba2117a002694210@mail.gmail.com>
[re-CC'ing lkml as it's back to the original topic]
26.04.2007 17:50, Dmitry Torokhov wrote/a écrit:
> On 4/26/07, akpm@linux-foundation.org <akpm@linux-foundation.org> wrote:
>> From: Eric Piel <eric.piel@tremplin-utc.net>
>>
>> Add support to wistron_btns for leds that comes with the multimedia keys.
>> Mail and wifi leds are supported, on laptops which have them.
>> Depending on
>> the laptop, wifi subsystem may control just the led, or both the led and
>> the wifi card. Wifi led interface is activated only for the former
>> type of
>> laptops, as the latter type is already managed. Leds are controled by
>> the
>> interface in /sys/class/leds.
>
> I am not sure if we want to allow controlling WIFI state via leds. I'd
> rather plug it into RFkill infrastructure once it is merged and have
> leds only reflect state of the corresponding switch.
>
Sorry if I wasn't clear. This is basically what does the driver. At
least, the led interface _do not_ control the WIFI state :-)
What I meant is that there are two kinds of laptops:
A - the one where wifi led _only_ is controlled by the wistron hardware.
Wifi card is controlled completely independently (pcmcia).
B - the one where wifi card _and_ wifi led are controlled by the wistron
hardware (they are completely bound).
So far, only B laptops were handled, à la RFkill: the button directly
modifies the wifi state and wifi led with no userspace involvement. My
patch adds wifi led interface only to A laptops, only the led is
controlled. So wifi state is never modified by led interface.
I hope I cleared up what does this patch and that it's ok with you. If
not, just let me know which behaviour you think would be more
appropriate and I'll hack a new patch :-)
See you,
Eric
parent reply other threads:[~2007-04-26 21:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <d120d5000704260850m788af054pba2117a002694210@mail.gmail.com>]
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=463118E7.3030902@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitr@volny.cz \
/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®