public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabien Crespel <fabien-czgx1wgAc3rR7s880joybQ@public.gmane.org>
To: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
Cc: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Dmitry Torokhov
	<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 2/2] asus-laptop add kill switch support
Date: Wed, 20 Feb 2008 00:38:11 +0100	[thread overview]
Message-ID: <47BB6863.7050208@crespel.net> (raw)
In-Reply-To: <1203349001.6019.85.camel-X8wR35IVlAxolqkO4TVVkw@public.gmane.org>

Thomas Renninger wrote :
> Hi,
>
> On Thu, 2008-02-07 at 19:06 +0100, Fabien Crespel wrote:
>> Basically:
>> - there is now a killswitch file in /sys/devices/platform/asus-laptop/ to report 
>> the KS status (read from HWRS)
>>     
> Not sure, but:
> Shouldn't this one register against a general kill-switch interface?
> E.g. include/linux/rfkill.h
> instead of starting an own interface...
>
>    Thomas
>   
Hello,

after looking at the rfkill interface, it doesn't seem to have the same 
purpose here : rfkill seems to be here to allow toggling radio frequency 
of devices in response to a key or another *software* generated event, 
while the "killswitch" sysfs file in my patch simply provides a way to 
read whether the *hardware* kill switch is ON (and not write or toggle 
anything, since it's completely out of software control).

My intention when adding this interface was to allow userspace tools 
like Lapsus to know when WLAN/Bluetooth are completely *disabled* (and 
not simply "off"). I don't think the rfkill interface provides a way to 
know that, or I missed it..? if it doesn't, wouldn't it be interesting 
to add it?

The rfkill interface seems interesting to support the Fn+F2 key though 
(WLAN/Bluetooth toggle), since currently it doesn't work on all models.

- Fabien.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-02-19 23:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 15:57 [PATCH 2/2] asus-laptop add kill switch support Corentin CHARY
     [not found] ` <200801161657.50967.corentincj-EjuBZuxMvz2sTnJN9+BGXg@public.gmane.org>
2008-01-17 10:52   ` Len Brown
2008-01-17 11:15     ` Corentin CHARY
2008-02-07  5:40   ` Len Brown
2008-02-07 18:06     ` Fabien Crespel
     [not found]       ` <1203349001.6019.85.camel@queen.suse.de>
     [not found]         ` <1203349001.6019.85.camel-X8wR35IVlAxolqkO4TVVkw@public.gmane.org>
2008-02-19 23:38           ` Fabien Crespel [this message]
     [not found]             ` <47BB6863.7050208-czgx1wgAc3rR7s880joybQ@public.gmane.org>
2008-02-22 10:03               ` Thomas Renninger

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=47BB6863.7050208@crespel.net \
    --to=fabien-czgx1wgac3rr7s880joybq@public.gmane.org \
    --cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=trenn-l3A5Bk7waGM@public.gmane.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