public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: on radio_enabled
Date: Thu, 23 Apr 2009 00:39:35 +0200	[thread overview]
Message-ID: <1240439975.30082.66.camel@johannes.local> (raw)

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

Hi!

So I was looking through various drivers, and not all of them are able
to handle radio_enabled gracefully.

iwlwifi, for instance, turns off the radio but then is unable to fulfil
any configuration requests coming in while the radio is disabled.

The same is true, if I remember correctly what Ivo told me, for rt2x00.

It is not true for b43/legacy, for example, which leaves the MAC running
and thus can configure everything even if the radio is disabled.
Similarly for Atheros hw, I think.

Now, if we're going to use radio_enabled more, I wonder whether we
should completely deconfigure the hardware when we want to turn off
radio_enabled, and then completely reconfigure it once we enable the
radio again.

Pros:
 * configures all hardware correctly without the driver needing to do
   everything by itself
 * works with all hardware for sure

Cons:
 * higher latency

Also, sometimes we may want to disable the radio for just short periods
of time, I think, for regulatory compliance? 11h or so? How's that
handled, or rather supposed to be?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2009-04-22 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 22:39 Johannes Berg [this message]
2009-04-22 22:46 ` on radio_enabled Gábor Stefanik
2009-04-24  6:24 ` Kalle Valo
2009-04-24 10:26   ` Johannes Berg
2009-04-24 14:10     ` Kalle Valo

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=1240439975.30082.66.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox