From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Philip Langdale <philipl@overt.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
toshiba_acpi@memebeam.org, randy.dunlap@oracle.com
Subject: Re: [PATCH] toshiba_acpi: Add support for bluetooth toggling through rfkill
Date: Tue, 22 Jul 2008 08:25:46 -0300 [thread overview]
Message-ID: <20080722112546.GD15136@khazad-dum.debian.net> (raw)
In-Reply-To: <48855FFB.40808@overt.org>
On Mon, 21 Jul 2008, Philip Langdale wrote:
> Henrique de Moraes Holschuh wrote:
>> Please consider updating your patch to the new style rfkill class. A quick
>> look at your patch shows that it would benefit from the new
>> RFKILL_STATE_HARD_BLOCKED, and maybe to some rework to separate the
>> bluetooth rfkill controller and the input device switch better. Depending
>> on the existence of ACPI GPE events when the switch changes state on
>> Toshibas, you may even be able to get rid of some of the polling...
>
> Well, if I can find said GPE, I'll certainly use it. A cursory glance through
> the dis-assembled AML didn't reveal anything obvious. Is there a way to log
> every single acpi event? I though acpid would receive them but it doesn't
> appear to.
Yes, one of the ACPI debug options plus a magic echo to procfs/sysfs. I
don't remember which :-( But it is there, you will just need to search for
it, unless someone else replies with the exact one.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
prev parent reply other threads:[~2008-07-22 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 21:04 Philip Langdale
2008-07-20 13:52 ` Henrique de Moraes Holschuh
2008-07-22 4:20 ` Philip Langdale
2008-07-22 11:25 ` Henrique de Moraes Holschuh [this message]
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=20080722112546.GD15136@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=philipl@overt.org \
--cc=randy.dunlap@oracle.com \
--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
Powered by JetHome