From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
Matthew Garrett <mjg@redhat.com>, Dan Williams <dcbw@redhat.com>,
Thomas Renninger <trenn@suse.de>
Subject: Re: [PATCH 12/12] rfkill: document rw rfkill switches and clarify input subsystem interactions
Date: Sun, 22 Jun 2008 22:24:12 -0400 [thread overview]
Message-ID: <20080623022412.GC24992@anvil.corenet.prv> (raw)
In-Reply-To: <1214149128-5913-13-git-send-email-hmh@hmh.eng.br>
Hi Henrique,
On Sun, Jun 22, 2008 at 12:38:48PM -0300, Henrique de Moraes Holschuh wrote:
> +2: Implementation details
> +
> +The rfkill class provides kernel drivers with an interface that allows them to
> +know when they should enable or disable a wireless network device transmitter.
> +
> +The rfkill-input module provides the kernel with the ability to implement
> +a basic response when the user presses a key or button (or toggles a switch)
> +related to rfkill functionality. This is optional, and can also be done in
> +userspace.
> +
> +The rfkill-input module also provides EPO (emergency power-off) functionality
> +for all wireless transmitters. This function cannot be overriden, and it is
> +always active. rfkill EPO is related to *_RFKILL_ALL input events.
> +
I think I would like to see the statement that rfkill-input is an
in-kernel implementation of default policy of reacting to Wifi-related
(in wide sense) button presses and neither mandatory nor required for
wireless drivers to operate.
--
Dmitry
next prev parent reply other threads:[~2008-06-23 2:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 15:38 [GIT PATCH] rfkill rework for 2.6.27 (v2) Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 01/12] rfkill: clarify meaning of rfkill states Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 02/12] rfkill: fix minor typo in kernel doc Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 03/12] rfkill: handle SW_RFKILL_ALL events Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 04/12] rfkill: add parameter to disable radios by default Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 05/12] rfkill: add read-write rfkill switch support Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 06/12] rfkill: add the WWAN radio type Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 07/12] rfkill: rework suspend and resume handlers Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 08/12] rfkill: add notifier chains support Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 09/12] rfkill: add type string helper Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 10/12] rfkill: add uevent notifications Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 11/12] rfkill: do not allow userspace to override ALL RADIOS OFF Henrique de Moraes Holschuh
2008-06-22 19:39 ` Fabien Crespel
2008-06-23 5:22 ` Henrique de Moraes Holschuh
[not found] ` <20080623095053.ZZRA012@mailhub.coreip.homeip.net>
2008-06-23 18:10 ` Henrique de Moraes Holschuh
2008-06-23 16:24 ` Henrique de Moraes Holschuh
2008-06-23 2:17 ` Dmitry Torokhov
2008-06-23 5:14 ` Henrique de Moraes Holschuh
2008-06-22 15:38 ` [PATCH 12/12] rfkill: document rw rfkill switches and clarify input subsystem interactions Henrique de Moraes Holschuh
2008-06-23 2:24 ` Dmitry Torokhov [this message]
2008-06-23 5:09 ` Henrique de Moraes Holschuh
-- strict thread matches above, loose matches on Subject: below --
2008-06-04 3:10 [GIT PATCH] rkfill improvements for -next Henrique de Moraes Holschuh
2008-06-04 3:10 ` [PATCH 12/12] rfkill: document rw rfkill switches and clarify input subsystem interactions Henrique de Moraes Holschuh
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=20080623022412.GC24992@anvil.corenet.prv \
--to=dmitry.torokhov@gmail.com \
--cc=dcbw@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mjg@redhat.com \
--cc=trenn@suse.de \
/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.