public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: on radio_enabled
Date: Fri, 24 Apr 2009 09:24:56 +0300	[thread overview]
Message-ID: <87tz4ed0w7.fsf@litku.valot.fi> (raw)
In-Reply-To: <1240439975.30082.66.camel@johannes.local> (Johannes Berg's message of "Thu\, 23 Apr 2009 00\:39\:35 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

> 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.

I assume that you mean op_stop() and op_start() here.

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

>From stlc45xx and wl12xx perspective I would like to have low latency as
possible for the radio on/off case. This is what I had in mind:

interface down:

o chip is powered off while down
o ifup uploads firmware and initialises it
o ifup might take hundreds of milliseconds, at least with 1271

radio off:

o chip is powered on
o firmware possibly sleeping/hibernating
o radios turned off
o very low latency (<5 ms) to wakeup
o small power consuption during radio off

This way it would be possible to have a bit faster scans when not
associated (with radio off), but still have a possibility to completely
turn of chip from user space for a longer periods of time (with
interface down).

-- 
Kalle Valo

  parent reply	other threads:[~2009-04-24  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 22:39 on radio_enabled Johannes Berg
2009-04-22 22:46 ` Gábor Stefanik
2009-04-24  6:24 ` Kalle Valo [this message]
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=87tz4ed0w7.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=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