From: Jes Sorensen <jes.sorensen@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Alan Jenkins <sourcejedi.lkml@googlemail.com>,
linux-acpi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
lenb@kernel.org
Subject: Re: [PATCH] Toshiba Bluetooth enabler (rfkill)
Date: Tue, 08 Dec 2009 16:50:06 +0100 [thread overview]
Message-ID: <4B1E75AE.5050901@gmail.com> (raw)
In-Reply-To: <20091208154738.GC26435@srcf.ucam.org>
On 12/08/09 16:47, Matthew Garrett wrote:
> On Tue, Dec 08, 2009 at 04:45:05PM +0100, Jes Sorensen wrote:
>> I believe I can call into BTST and determine whether the switch is set
>> to on or not. It's quite easy to add this to the resume handler and only
>> call if it's set to on.
>
> Right, but in normal use it's an issue. Unless we get notifications for
> both types of state change, we can't add an rfkill device.
>
Understand, not sure how to go about this. It doesn't seem to generate
an APIC event on off, it just pulls the USB device out of it's plug. Not
sure if it would be possible to plug into the USB unplug event?
Cheers,
Jes
next prev parent reply other threads:[~2009-12-08 15:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 15:38 [PATCH] Toshiba Bluetooth enabler (rfkill) Jes Sorensen
2009-12-08 10:05 ` Alan Jenkins
2009-12-08 12:55 ` Matthew Garrett
2009-12-08 15:45 ` Jes Sorensen
2009-12-08 15:47 ` Matthew Garrett
2009-12-08 15:50 ` Jes Sorensen [this message]
2009-12-08 15:51 ` Matthew Garrett
2009-12-08 21:30 ` Alan Jenkins
2009-12-08 16:58 ` Toshiba Bluetooth enabler (v2) (was: Re: [PATCH] Toshiba Bluetooth enabler (rfkill)) Jes Sorensen
2009-12-09 13:17 ` Alan Jenkins
2009-12-10 13:27 ` Dan Carpenter
2009-12-10 13:47 ` Alan Jenkins
2009-12-10 15:27 ` PATCH: Toshiba Bluetooth enabler (v3) Jes Sorensen
2009-12-10 17:00 ` Alan Jenkins
2009-12-11 10:51 ` Jes Sorensen
2009-12-11 13:08 ` Alan Jenkins
2009-12-16 17:06 ` Len Brown
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=4B1E75AE.5050901@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=sourcejedi.lkml@googlemail.com \
/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