From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Michael Buesch <mb@bu3sch.de>,
Adel Gadllah <adel.gadllah@gmail.com>,
linux-wireless@vger.kernel.org, stefano.brivio@polimi.it,
"John W. Linville" <linville@tuxdriver.com>,
Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [PATCH/RFC] b43: remove input device usage for rfkill
Date: Tue, 01 Jul 2008 12:14:29 -0500 [thread overview]
Message-ID: <486A65F5.5030909@lwfinger.net> (raw)
In-Reply-To: <1214931676.3462.5.camel@johannes.berg>
Johannes Berg wrote:
> On Tue, 2008-07-01 at 13:50 -0300, Henrique de Moraes Holschuh wrote:
>> On Tue, 01 Jul 2008, Johannes Berg wrote:
>>>> 1. It has an input pin that sometimes people connect buttons/switches
>>>> to.
>>>>
>>>> Does that input pin act as an input for a FLIP-FLOP (and that flip-flop
>>>> output is the hardware rfkill line), or is it the hardware rfkill line
>>>> itself?
>>> Neither. It's not hw kill, but it's not just edge detect either, it does
>>> have 'kill' and 'not kill' states.
>> What exactly the input pin does? what exactly the hardware does when
>> the input pin state changes?
>
> The hardware does nothing, it just sets a bit high or low depending on
> the input pin.
On my HP laptop using the RFKILL code currently in wireless-testing,
sliding the "Wireless switch" results in b43_rfkill_poll being called.
It then issues KEY_WLAN press and release events. This changes the
state of the wireless light and the contents of a read-only bit in the
status register of the device. I believe that if this bit is off, the
radio is blocked by the hardware.
Larry
next prev parent reply other threads:[~2008-07-01 17:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 9:55 [PATCH/RFC] b43: remove input device usage for rfkill Adel Gadllah
2008-07-01 9:58 ` Johannes Berg
2008-07-01 10:05 ` [PATCH/RFC v2] " Adel Gadllah
2008-07-01 10:08 ` Johannes Berg
2008-07-01 10:19 ` [PATCH/RFC v3] " Adel Gadllah
2008-07-01 10:23 ` Johannes Berg
2008-07-01 10:31 ` drago01
2008-07-01 10:29 ` Michael Buesch
2008-07-01 10:34 ` drago01
2008-07-01 10:29 ` Ivo van Doorn
2008-07-01 10:27 ` [PATCH/RFC] " Michael Buesch
2008-07-01 10:33 ` drago01
2008-07-01 10:38 ` Michael Buesch
2008-07-01 14:34 ` Henrique de Moraes Holschuh
2008-07-01 14:38 ` Johannes Berg
2008-07-01 16:50 ` Henrique de Moraes Holschuh
2008-07-01 17:01 ` Johannes Berg
2008-07-01 17:14 ` Larry Finger [this message]
2008-07-01 17:35 ` Henrique de Moraes Holschuh
2008-07-01 18:21 ` Larry Finger
2008-07-01 21:20 ` Dan Williams
2008-07-02 2:45 ` Larry Finger
2008-07-01 17:33 ` Henrique de Moraes Holschuh
2008-07-01 18:01 ` Johannes Berg
2008-07-01 18:41 ` Henrique de Moraes Holschuh
2008-07-01 18:44 ` Johannes Berg
2008-07-01 22:52 ` Henrique de Moraes Holschuh
2008-07-01 22:56 ` Johannes Berg
2008-07-01 23:57 ` Henrique de Moraes Holschuh
2008-07-02 2:43 ` Larry Finger
2008-07-02 7:21 ` Johannes Berg
2008-07-02 7:31 ` Johannes Berg
2008-07-02 16:02 ` Henrique de Moraes Holschuh
2008-07-02 13:16 ` Dmitry Torokhov
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=486A65F5.5030909@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=adel.gadllah@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=stefano.brivio@polimi.it \
/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).