public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Vroon <tony@linx.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: linux-acpi@vger.kernel.org, jwoithe@physics.adelaide.edu.au
Subject: Fuijtsu Lifebook RFKILL support
Date: Thu, 11 Dec 2008 01:05:06 +0000	[thread overview]
Message-ID: <1228957506.4045.11.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Good morning,

There is preliminary code ready to implement RFKILL support on Fujitsu
laptops. Unfortunately, I can't see how to express this specific switch
type within the existing framework.
The laptop has one "big" kill switch that kills everything,
WLAN/Bluetooth/3G, you name it. I have no means to turn individual
radios on or off, all I'll get is a big notifier (from which I can fire
up a query to see whether the kill switch state got changed).

As such, I have 1 rfkill interface that I'd like to call "all", which
supports states RFKILL_STATE_HARD_BLOCKED and RFKILL_STATE_UNBLOCKED. I
can implement get_state, but toggle_radio is marked mandatory.

I can't do anything meaningful in response to toggle_radio, but I could
unconditionally report failure. Ivo, does that violate the spirit of the
interface? To me it seems useful to have the notifiers, but I figured
I'd ask the subsystem maintainer first.

Jonathan, if you have DSDTs for machines other then a Lifebook S6410,
S6420 or E8410 could you please e-mail these to me. I would like to see
whether the callbacks I'm using are present.

Regards,
Tony V.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-12-11  1:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  1:05 Tony Vroon [this message]
2008-12-11  1:20 ` Fuijtsu Lifebook RFKILL support Jonathan Woithe
2008-12-11  1:31   ` Tony Vroon
2008-12-11  1:44     ` Jonathan Woithe
2008-12-11 16:52 ` Henrique de Moraes Holschuh
2008-12-11 17:33   ` Tony Vroon
2008-12-11 19:47     ` Henrique de Moraes Holschuh
2008-12-12  1:50       ` Tony Vroon
2008-12-12 19:53         ` Henrique de Moraes Holschuh
2008-12-12 20:33           ` Len Brown
2008-12-13 12:47             ` Tony Vroon
2008-12-13 13:28               ` Henrique de Moraes Holschuh
2008-12-13 17:57                 ` Matthew Garrett
2008-12-13 20:55                   ` Tony Vroon
2008-12-13 21:24                     ` Matthew Garrett
2008-12-14  3:13                   ` Henrique de Moraes Holschuh
2008-12-14 17:05                 ` Dan Williams
2008-12-15 11:53                   ` Henrique de Moraes Holschuh
     [not found]                     ` <20081215115336.GD17648-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2008-12-15 15:19                       ` Dan Williams
2008-12-15 17:14                         ` Tony Vroon
2008-12-15 17:59                           ` Dan Williams
2008-12-16 13:50                             ` Tony Vroon
2008-12-16 15:23                               ` Dan Williams
2008-12-15 23:42                           ` Jonathan Woithe
2008-12-15 23:48                             ` Tony Vroon
2008-12-16  0:02                               ` Jonathan Woithe

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=1228957506.4045.11.camel@localhost \
    --to=tony@linx.net \
    --cc=ivdoorn@gmail.com \
    --cc=jwoithe@physics.adelaide.edu.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox