From: Nick Kossifidis <mickflemm@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, jirislaby@gmail.com, nbd@openwrt.org
Subject: Re: [ath5k-devel] [PATCH 4/4] ath5k: Use SWI to trigger calibration
Date: Sat, 1 Aug 2009 16:31:27 +0300 [thread overview]
Message-ID: <40f31dec0908010631x84ddfcap99a871f3513cf22b@mail.gmail.com> (raw)
In-Reply-To: <20090801132253.GB15971@hash.localnet>
2009/8/1 Bob Copeland <me@bobcopeland.com>:
> On Fri, Jul 31, 2009 at 10:52:42PM +0300, Nick Kossifidis wrote:
>> > make the above true it needs to stop the queues etc when doing
>> > calibration.
>>
>> ACK, how do we do that ?
>> ieee80211_stop_queues / ieee80211_wake_queues
>
> Yup. And disabling (at least rx and swba) interrupts on the device
> is also probably a good idea.
>
I thought about calling ath5k_hw_stop_rx_pcu but i don't think it's
necessary i mean it won't receive anyway, why mess with pcu ?
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
next prev parent reply other threads:[~2009-08-01 13:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 18:10 [PATCH 4/4] ath5k: Use SWI to trigger calibration Nick Kossifidis
2009-07-31 18:15 ` Luis R. Rodriguez
2009-07-31 18:25 ` [ath5k-devel] " Nick Kossifidis
2009-07-31 18:48 ` Luis R. Rodriguez
2009-07-31 19:09 ` Pavel Roskin
2009-07-31 19:35 ` Nick Kossifidis
2009-07-31 19:43 ` Pavel Roskin
2009-07-31 19:11 ` Bob Copeland
2009-07-31 19:52 ` Nick Kossifidis
2009-08-01 13:22 ` Bob Copeland
2009-08-01 13:31 ` Nick Kossifidis [this message]
2009-08-02 16:14 ` Bob Copeland
2009-07-31 18:34 ` Nick Kossifidis
2009-08-01 5:46 ` Nick Kossifidis
2009-08-01 8:19 ` Jiri Slaby
2009-08-01 8:21 ` Johannes Berg
2009-08-01 8:24 ` Jiri Slaby
2009-08-01 8:28 ` Johannes Berg
2009-08-01 8:31 ` [ath5k-devel] " Nick Kossifidis
2009-08-01 8:35 ` Jiri Slaby
2009-08-03 17:54 ` Nick Kossifidis
2009-08-07 14:55 ` John W. Linville
2009-08-07 19:50 ` Nick Kossifidis
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=40f31dec0908010631x84ddfcap99a871f3513cf22b@mail.gmail.com \
--to=mickflemm@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).