From: Ivo van Doorn <ivdoorn@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-kernel@vger.kernel.org, "Thomas Renninger" <trenn@suse.de>,
"Inaky Perez-Gonzalez" <inaky@linux.intel.com>,
"Iñaky Pérez-González" <inaky.perez-gonzalez@intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 09/15] rfkill: add the WWAN radio type
Date: Tue, 20 May 2008 12:08:53 +0200 [thread overview]
Message-ID: <200805201208.53740.IvDoorn@gmail.com> (raw)
In-Reply-To: <1211136485-19878-10-git-send-email-hmh@hmh.eng.br>
On Sunday 18 May 2008, Henrique de Moraes Holschuh wrote:
> Unfortunately, instead of adding a generic Wireless WAN type, a technology-
> specific type (WiMAX) was added. That's useless for other WWAN devices,
> such as EDGE, UMTS, X-RTT and other such radios.
>
> Add a WWAN rfkill type for generic wireless WAN devices. No keys are added
> as most devices really want to use KEY_WLAN for WWAN control (in a cycle of
> none, WLAN, WWAN, WLAN+WWAN) and need no specific keycode added.
>
> Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
If WiMAX is a subset of the WWAN technology, shouldn't we replace WiMAX completely
in rfkill? Otherwise people might get ideas and add the other technologies seperately as well. ;)
Other then that, the addition of WWAN is fine with me. :)
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
> Cc: Iñaky Pérez-González <inaky.perez-gonzalez@intel.com>
> Cc: Ivo van Doorn <IvDoorn@gmail.com>
> Cc: John W. Linville <linville@tuxdriver.com>
> Cc: David S. Miller <davem@davemloft.net>
> ---
> include/linux/rfkill.h | 2 ++
> net/rfkill/rfkill-input.c | 4 ++++
> net/rfkill/rfkill.c | 3 +++
> 3 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/rfkill.h b/include/linux/rfkill.h
> index 844e961..c0cab7d 100644
> --- a/include/linux/rfkill.h
> +++ b/include/linux/rfkill.h
> @@ -34,12 +34,14 @@
> * RFKILL_TYPE_BLUETOOTH: switch is on a bluetooth device.
> * RFKILL_TYPE_UWB: switch is on a ultra wideband device.
> * RFKILL_TYPE_WIMAX: switch is on a WiMAX device.
> + * RFKILL_TYPE_WWAN: switch is on a wireless WAN device.
> */
> enum rfkill_type {
> RFKILL_TYPE_WLAN ,
> RFKILL_TYPE_BLUETOOTH,
> RFKILL_TYPE_UWB,
> RFKILL_TYPE_WIMAX,
> + RFKILL_TYPE_WWAN,
> RFKILL_TYPE_MAX,
> };
>
> diff --git a/net/rfkill/rfkill-input.c b/net/rfkill/rfkill-input.c
> index 9d6c925..29c13d3 100644
> --- a/net/rfkill/rfkill-input.c
> +++ b/net/rfkill/rfkill-input.c
> @@ -101,6 +101,7 @@ static DEFINE_RFKILL_TASK(rfkill_wlan, RFKILL_TYPE_WLAN);
> static DEFINE_RFKILL_TASK(rfkill_bt, RFKILL_TYPE_BLUETOOTH);
> static DEFINE_RFKILL_TASK(rfkill_uwb, RFKILL_TYPE_UWB);
> static DEFINE_RFKILL_TASK(rfkill_wimax, RFKILL_TYPE_WIMAX);
> +static DEFINE_RFKILL_TASK(rfkill_wwan, RFKILL_TYPE_WWAN);
>
> static void rfkill_event(struct input_handle *handle, unsigned int type,
> unsigned int code, int data)
> @@ -126,6 +127,9 @@ static void rfkill_event(struct input_handle *handle, unsigned int type,
> switch (code) {
> case SW_RFKILL_ALL:
> /* EVERY radio type. data != 0 means radios ON */
> + rfkill_schedule_set(&rfkill_wwan,
> + (data)? RFKILL_STATE_ON:
> + RFKILL_STATE_OFF);
> rfkill_schedule_set(&rfkill_wimax,
> (data)? RFKILL_STATE_ON:
> RFKILL_STATE_OFF);
> diff --git a/net/rfkill/rfkill.c b/net/rfkill/rfkill.c
> index 2e19b68..c5a79ab 100644
> --- a/net/rfkill/rfkill.c
> +++ b/net/rfkill/rfkill.c
> @@ -176,6 +176,9 @@ static ssize_t rfkill_type_show(struct device *dev,
> case RFKILL_TYPE_WIMAX:
> type = "wimax";
> break;
> + case RFKILL_TYPE_WWAN:
> + type = "wwan";
> + break;
> default:
> BUG();
> }
next prev parent reply other threads:[~2008-05-20 9:55 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 18:47 [RFC] rfkill class rework Henrique de Moraes Holschuh
2008-05-18 18:47 ` [PATCH 01/15] ACPI: thinkpad-acpi: fix initialization error paths Henrique de Moraes Holschuh
2008-05-18 18:47 ` [PATCH 02/15] ACPI: thinkpad-acpi: fix LED handling on older ThinkPads Henrique de Moraes Holschuh
2008-05-18 18:47 ` [PATCH 03/15] Input: rename SW_RADIO to SW_RFKILL_ALL (v2) Henrique de Moraes Holschuh
2008-05-18 18:47 ` [PATCH 04/15] rfkill: clarify meaning of rfkill states Henrique de Moraes Holschuh
2008-05-20 10:08 ` Ivo van Doorn
2008-05-18 18:47 ` [PATCH 05/15] rfkill: fix minor typo in kernel doc Henrique de Moraes Holschuh
2008-05-20 10:08 ` Ivo van Doorn
2008-05-18 18:47 ` [PATCH 06/15] rfkill: handle SW_RFKILL_ALL events Henrique de Moraes Holschuh
2008-05-20 10:08 ` Ivo van Doorn
2008-05-18 18:47 ` [PATCH 07/15] rfkill: add parameter to disable radios by default Henrique de Moraes Holschuh
2008-05-18 18:47 ` [PATCH 08/15] rfkill: add read-write rfkill switch support Henrique de Moraes Holschuh
2008-05-20 10:08 ` Ivo van Doorn
2008-05-18 18:47 ` [PATCH 09/15] rfkill: add the WWAN radio type Henrique de Moraes Holschuh
2008-05-20 10:08 ` Ivo van Doorn [this message]
2008-05-21 1:12 ` Henrique de Moraes Holschuh
2008-05-21 3:35 ` Inaky Perez-Gonzalez
2008-05-21 3:42 ` Henrique de Moraes Holschuh
2008-05-21 6:48 ` Inaky Perez-Gonzalez
2008-05-21 14:07 ` Henrique de Moraes Holschuh
2008-05-18 18:48 ` [PATCH 10/15] rfkill: rework suspend and resume handlers Henrique de Moraes Holschuh
2008-05-20 10:08 ` Ivo van Doorn
2008-05-18 18:48 ` [PATCH 11/15] rfkill: add notifier chains support Henrique de Moraes Holschuh
2008-05-19 8:44 ` Thomas Renninger
2008-05-19 13:10 ` Henrique de Moraes Holschuh
2008-05-20 10:09 ` Ivo van Doorn
2008-05-18 18:48 ` [PATCH 12/15] rfkill: add type string helper Henrique de Moraes Holschuh
2008-05-20 10:09 ` Ivo van Doorn
2008-05-18 18:48 ` [PATCH 13/15] rfkill: add uevent notifications Henrique de Moraes Holschuh
2008-05-20 10:09 ` Ivo van Doorn
2008-05-18 18:48 ` [PATCH 14/15] rfkill: do not allow userspace to override ALL RADIOS OFF Henrique de Moraes Holschuh
2008-05-20 10:09 ` Ivo van Doorn
2008-05-22 20:51 ` Henrique de Moraes Holschuh
2008-05-23 14:15 ` Ivo van Doorn
2008-05-27 14:08 ` Henrique de Moraes Holschuh
2008-05-27 14:38 ` Ivo van Doorn
2008-05-27 17:41 ` Henrique de Moraes Holschuh
2008-05-27 18:13 ` Ivo van Doorn
2008-05-18 18:48 ` [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions Henrique de Moraes Holschuh
2008-05-19 17:51 ` Randy Dunlap
2008-05-19 22:04 ` Henrique de Moraes Holschuh
2008-05-19 22:52 ` Elias Oltmanns
2008-05-19 22:56 ` Randy Dunlap
2008-05-20 10:09 ` Ivo van Doorn
2008-05-20 15:54 ` Henrique de Moraes Holschuh
2008-05-20 17:18 ` Ivo van Doorn
2008-05-21 1:44 ` Henrique de Moraes Holschuh
2008-05-29 0:45 ` [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions (v2) Henrique de Moraes Holschuh
2008-05-29 13:02 ` Ivo van Doorn
2008-05-29 16:26 ` Henrique de Moraes Holschuh
2008-05-29 17:19 ` Ivo van Doorn
2008-05-29 17:22 ` Henrique de Moraes Holschuh
2008-05-29 17:40 ` Ivo van Doorn
2008-05-29 17:46 ` Henrique de Moraes Holschuh
2008-05-29 18:58 ` Dmitry Torokhov
2008-05-29 21:16 ` Henrique de Moraes Holschuh
2008-05-29 21:25 ` [PATCH] Input: rename SW_RADIO to SW_RFKILL_ALL (v2) Henrique de Moraes Holschuh
2008-06-04 3:11 ` [PATCH 15/15] rfkill: document rw rfkill switches and clarify input subsystem interactions (v2) 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=200805201208.53740.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=davem@davemloft.net \
--cc=hmh@hmh.eng.br \
--cc=inaky.perez-gonzalez@intel.com \
--cc=inaky@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox