From: Philip Langdale <philipl@overt.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
toshiba_acpi@memebeam.org,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Ivo van Doorn <ivdoorn@gmail.com>,
linux-wireless@vger.kernel.org
Subject: [PATCH 0/1] toshiba_acpi: Add support for bluetooth toggling through rfkill
Date: Sun, 27 Jul 2008 11:17:04 -0700 [thread overview]
Message-ID: <488CBBA0.2050106@overt.org> (raw)
As requested by Henrique, I have reworked this patch against wireless-testing
and it uses the new-style rfkill API and to report the input device as a switch.
I did some digging to try and find a usable gpe event but had only limited
success. From another look through the AML, it uses GPE08 for almost everything
- inspecting a bunch of state for each event and then sending notifications on
different objects. I couldn't find one for the hardware kill switch itself but I
did manage to find one that's emitted when the bluetooth device enters the
equivalent of the SOFT_BLOCKED state. This is useful for noticing that the
hardware switch has been released, but it also fires on transitions from UNBLOCKED
to SOFT_BLOCKED - so I had to try and avoid turning around and unblocking the
device! I'm not particularly happy with how I did it (ignore-the-next-event)
but I can't think of a better way.
--phil
next reply other threads:[~2008-07-27 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 18:17 Philip Langdale [this message]
2008-07-28 2:55 ` [PATCH 0/1] toshiba_acpi: Add support for bluetooth toggling through rfkill Henrique de Moraes Holschuh
2008-08-02 19:14 ` [PATCH 0/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2) Philip Langdale
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=488CBBA0.2050106@overt.org \
--to=philipl@overt.org \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=toshiba_acpi@memebeam.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;
as well as URLs for NNTP newsgroup(s).