All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Porsch <marco.porsch@etit.tu-chemnitz.de>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ath9k] mesh powersave hardware sleep + wakeup
Date: Fri, 27 Apr 2012 17:53:00 +0200	[thread overview]
Message-ID: <4F9AC0DC.9030304@etit.tu-chemnitz.de> (raw)
In-Reply-To: <4F856449.3000804@etit.tu-chemnitz.de>

On 04/11/12 13:00, Marco Porsch wrote:
> On 03/16/12 23:09, Marco Porsch wrote:
>>> On Fri, Mar 16, 2012 at 10:42:02AM +0100, Marco Porsch wrote:
>>>> I am trying to implement the IEEE 802.11s power save schemes in mac80211.
>
> I did some hacking and can now answer part one of my question:
> yes, beaconing and power save are not mutually exclusive with ath9k.
>
> Second question: what about power save doze and waking up for _multiple_
> neighbors' beacons?

I've again done some hacking: now waking up for multiple neighbor 
beacons in mesh mode seems to work experimentally [1].

Next step is the mesh awake window i.e. just keep awake for a specified 
time after beacon TX.
Is it possible to configure the hardware accordingly?


There are some settings concerning ad-hoc's ATIM window in 
ath9k_hw_beaconinit that look like it should be possible to use hardware 
timers for that. Unfortunately, I had no success on these. Maybe it 
requires ATIM frames (-> AR_TXCFG_ADHOC_BEACON_ATIM_TX_POLICY)?

Regards,
Marco


[1]
I maintain a list of wakeup events stored as ath9k_beacon_state. When 
doing ath9k_ps_restore, I re-configure the hardware with a slightly 
modified version of ath9k_hw_set_sta_beacon_timers to expect the next 
wakeup event.
Actually seems to work.

      parent reply	other threads:[~2012-04-27 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16  9:42 [ath9k] mesh powersave hardware sleep + wakeup Marco Porsch
2012-03-16 20:45 ` Luis R. Rodriguez
2012-03-16 22:09   ` Marco Porsch
2012-04-11 11:00     ` [Greenmesh] " Marco Porsch
2012-04-12  4:05       ` Johannes Berg
2012-04-12  7:41         ` Marco Porsch
2012-04-18  2:02           ` Johannes Berg
2012-04-18 14:56             ` Javier Cardona
2012-04-18 15:05               ` Johannes Berg
2012-04-18 15:16                 ` Javier Cardona
2012-04-19  2:41                   ` Yeoh Chun-Yeow
2012-04-19  2:51                     ` Javier Cardona
2012-04-27 15:53       ` Marco Porsch [this message]

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=4F9AC0DC.9030304@etit.tu-chemnitz.de \
    --to=marco.porsch@etit.tu-chemnitz.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rodrigue@qca.qualcomm.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 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.