From: Philip Langdale <philipl@overt.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
toshiba_acpi@memebeam.org, Ivo van Doorn <ivdoorn@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2)
Date: Mon, 11 Aug 2008 09:41:32 -0700 [thread overview]
Message-ID: <48A06BBC.7060007@overt.org> (raw)
In-Reply-To: <20080807134530.GB17062@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
>
> Hmm? UNBLOCKED means it is not being rfkilled. Why is not working? Put
> some debug printks on your toggle_radio callback, that might help fix the
> issue...
>
Well, what I see is this:
At modprobe, I get an explicit unblock request. When I modify 'state' in sysfs,
I see appropriate requests to soft block and unblock. When I activate the hardware
kill switch, the rfkill state goes to hard_block but no one calls toggle_radio
and when I release the kill switch, the state goes to soft_block and no one
calls toggle_radio.
--phil
next prev parent reply other threads:[~2008-08-11 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 19:12 [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill (v2) Philip Langdale
2008-08-03 4:26 ` Henrique de Moraes Holschuh
2008-08-04 1:10 ` Philip Langdale
2008-08-05 21:24 ` Henrique de Moraes Holschuh
2008-08-06 3:33 ` Philip Langdale
2008-08-06 12:26 ` Henrique de Moraes Holschuh
2008-08-06 12:45 ` Henrique de Moraes Holschuh
2008-08-07 4:40 ` Philip Langdale
2008-08-07 13:45 ` Henrique de Moraes Holschuh
2008-08-11 16:41 ` Philip Langdale [this message]
2008-08-13 9:29 ` Henrique de Moraes Holschuh
2008-08-14 6:58 ` Philip Langdale
2008-08-16 19:22 ` 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=48A06BBC.7060007@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.