From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Copeland Date: Mon, 6 Apr 2015 07:17:04 -0400 Subject: [ath9k-devel] ar9330 autosleep In-Reply-To: <21791.20943.459772.965935@gargle.gargle.HOWL> References: <20150402181745.GB2953@localhost> <21789.63534.378525.962484@gargle.gargle.HOWL> <20150403114859.GA6339@localhost> <21791.20943.459772.965935@gargle.gargle.HOWL> Message-ID: <20150406111704.GA2829@localhost> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Sat, Apr 04, 2015 at 08:21:59AM +0530, Sujith Manoharan wrote: > Bob Copeland wrote: > > So I'm still missing the part where we wake hardware up on this version. > > It seemed to work for me though. > > Sorry, I was referring to the PS mechanism on chips which don't > support autosleep. > > For autosleep, no special handling in the driver is required > except the initial duration programming done in > ath9k_hw_set_sta_beacon_timers(). The HW wakes up to receive > every beacon and automatically goes back to network sleep. Ok, got it, so if I have a need to wake up for beacons from multiple APs with different TSFs, then autosleep probably wouldn't work for me? (I already implemented what I need with the TIM_TIMER on these chips, just asking to confirm my understanding.) -- Bob Copeland %% http://bobcopeland.com/