Linux wireless drivers development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Vasanthakumar Thiagarajan <vasanth@atheros.com>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Jouni Malinen <Jouni.Malinen@Atheros.com>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH] Ath9k: Add RF kill support.
Date: Mon, 08 Sep 2008 07:22:20 +0200	[thread overview]
Message-ID: <1220851340.6714.132.camel@californication> (raw)
In-Reply-To: <20080908045926.GA28149@vasanth-lnx.users.atheros.com>

Hi Vasanthakumar,

> > > CONFIG_ATH9K_RFKILL needs to be set
> > > to enable this support.
> > 
> > why do we have to introduce yet another config option for this? What is
> > the advantage of disabling RFKILL support? I really don't see it and all
> > these extra config options are rather confusing than useful.
> Normally home users may not hit a situation where they have to
> disable the radio, so they can compile out the rf kill support
> and essentially disable the periodic run of the work queue 
> (rfkill_poll ,runs for every 2 secs).If this does not make 
> any sense, I will remove this config option.

I don't know about the actual implementation, but if you use a polling
mechanism then it is wrong. Can't you make this interrupt driven.

The desktop use case needs RFKILL support, because that will be used for
switching off the radio. Just think about the flight mode case. So the
only case where disabling RFKILL support makes sense would be an
embedded system with specific constraints. However even in the embedded
case, I don't see that usefulness.

Regards

Marcel



  reply	other threads:[~2008-09-08  5:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 12:38 [PATCH] Ath9k: Add RF kill support Vasanthakumar Thiagarajan
2008-09-06 17:15 ` Marcel Holtmann
2008-09-06 17:19   ` Johannes Berg
2008-09-06 17:23     ` Johannes Berg
2008-09-07  1:00       ` Marcel Holtmann
2008-09-07  7:17         ` Johannes Berg
2008-09-07 11:56           ` Henrique de Moraes Holschuh
2008-09-07 12:40             ` Johannes Berg
2008-09-07  0:57     ` Marcel Holtmann
2008-09-08  4:59   ` Vasanthakumar Thiagarajan
2008-09-08  5:22     ` Marcel Holtmann [this message]
2008-09-08  5:38       ` Vasanthakumar Thiagarajan
2008-09-08 15:10     ` Henrique de Moraes Holschuh
2008-09-09  7:53       ` vasanthakumar thiagarajan
2008-09-07 12:09 ` Henrique de Moraes Holschuh
2008-09-08  5:20   ` Vasanthakumar Thiagarajan
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09  5:33 Mats Johannesson
2008-09-09 15:34 [PATCH] ath9k: " Vasanthakumar Thiagarajan
2008-09-09 15:42 ` Johannes Berg
2008-09-09 16:22   ` vasanthakumar thiagarajan
2008-09-09 15:46 ` Johannes Berg
2008-09-09 16:02   ` vasanthakumar thiagarajan
2008-09-09 16:15     ` Henrique de Moraes Holschuh
2008-09-09 16:15       ` vasanthakumar thiagarajan
2008-09-09 16:19 ` 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=1220851340.6714.132.camel@californication \
    --to=marcel@holtmann.org \
    --cc=Jouni.Malinen@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Vasanth.Thiagarajan@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=vasanth@atheros.com \
    /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