From: Zhu Yi <yi.zhu@intel.com>
To: linux-wireless@vger.kernel.org
Subject: Question on rfkill double block
Date: Wed, 02 Jul 2008 15:03:28 +0800 [thread overview]
Message-ID: <1214982208.14590.473.camel@debian.sh.intel.com> (raw)
Hi,
Quote from Documentation/rfkill.txt:
"
The driver should implement the toggle_radio() hook, that:
=2E..
3. Deactivates the soft rfkill line if none of the hardware rfkill line=
s
are active and the caller asked for RFKILL_STATE_UNBLOCKED.
"
It doesn't say what to do if both the hardware and software rfkill line=
s
are active when RFKILL_STATE_UNBLOCKED is asked. Should we deactivate
the software rfkill in this case? Otherwise below usage won't turn on
the radio:
hardware rfkill activate
software rfkill activate
RFKILL_STATE_UNBLOCKED request
hardware rfkill deactivate
=46urthermore, if we permit double block, what should get_state() retur=
n?
Shouldn't rfkill_state =EF=BB=BFbe bitmap instead of enum?
Thanks,
-yi
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-07-02 7:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 7:03 Zhu Yi [this message]
2008-07-02 17:03 ` Question on rfkill double block Dan Williams
2008-07-04 19:55 ` Henrique de Moraes Holschuh
2008-07-07 17:11 ` Dan Williams
2008-07-07 19:48 ` Fabien Crespel
2008-07-07 20:47 ` Henrique de Moraes Holschuh
2008-07-08 5:12 ` Andy Lutomirski
2008-07-08 15:05 ` Henrique de Moraes Holschuh
2008-07-02 19:32 ` Henrique de Moraes Holschuh
2008-07-05 21:28 ` Tomas Winkler
2008-07-06 0:20 ` Henrique de Moraes Holschuh
2008-07-07 4:44 ` Andy Lutomirski
2008-07-07 16:56 ` Henrique de Moraes Holschuh
2008-07-07 18:47 ` Andrew Lutomirski
2008-07-07 19:18 ` Andrew Lutomirski
2008-07-07 21:09 ` Andrew Lutomirski
2008-07-07 21:21 ` Henrique de Moraes Holschuh
2008-07-07 20:59 ` Henrique de Moraes Holschuh
2008-07-07 17:02 ` Dan Williams
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=1214982208.14590.473.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=linux-wireless@vger.kernel.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.