From: Bruno Randolf <br1@einfach.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"adrian@freebsd.org" <adrian@freebsd.org>,
Vasanth Thiagarajan <Vasanth.Thiagarajan@atheros.com>
Subject: Re: [ath5k-devel] [PATCH 3/5] ath9k: Use common cycle counters
Date: Wed, 6 Oct 2010 10:10:46 +0900 [thread overview]
Message-ID: <201010061010.46430.br1@einfach.org> (raw)
In-Reply-To: <20101005201407.GI11831@tux>
On Wed October 6 2010 05:14:07 Luis R. Rodriguez wrote:
> On Tue, Oct 05, 2010 at 02:55:21AM -0700, Bruno Randolf wrote:
> > Update ath9k to use the common cycle counters.
> >
> > This also includes other changes from Felix Fietkaus "[PATCH 2/4]
> > ath9k_hw: merge codepaths that access the cycle counter registers".
> >
> > Compile tested only. ath9k team please review...
>
> Can you move locking to be specific to the core part of
> the driver instead of the ath9k_hw ?
i'm not sure if i understand what you mean. locking is now implemented in
ath_common.
> We try to avoid locking
> all over the hardware code. Even ath9k_iowrite32() and
> ath9k_ioread32() are core driver helpers, not part of the
> hw code.
but, we need to make sure the cycle counters are always accessed exclusively.
e.g. ANI runs from a timer (in ath9k, afaik), and updates the cycle counters.
at the same time a user might issue a survey, or your debug print may be
executed, which would want to access the same counters. we need to make sure
the counters are not updated while they are read, etc...
bruno
next prev parent reply other threads:[~2010-10-06 1:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 9:55 [PATCH 1/5] ath: Add common function for reading cycle counters Bruno Randolf
2010-10-05 9:55 ` [PATCH 2/5] ath5k: Use common cycle counters for ANI Bruno Randolf
2010-10-05 9:55 ` [PATCH 3/5] ath9k: Use common cycle counters Bruno Randolf
2010-10-05 20:14 ` [ath5k-devel] " Luis R. Rodriguez
2010-10-06 1:10 ` Bruno Randolf [this message]
2010-10-06 1:13 ` Luis R. Rodriguez
2010-10-06 1:18 ` Luis R. Rodriguez
2010-10-06 2:00 ` Bruno Randolf
2010-10-06 2:15 ` [ath5k-devel] " Luis R. Rodriguez
2010-10-05 9:55 ` [PATCH 4/5] nl80211/mac80211: Add channel utilization to survey Bruno Randolf
2010-10-05 22:36 ` Luis R. Rodriguez
2010-10-06 2:35 ` Bruno Randolf
2010-10-06 9:54 ` Helmut Schaa
2010-10-07 1:03 ` Bruno Randolf
2010-10-07 3:02 ` [ath5k-devel] " Luis R. Rodriguez
2010-10-07 6:51 ` Helmut Schaa
2010-10-07 7:06 ` Bruno Randolf
2010-10-07 7:35 ` Jonathan Guerin
2010-10-07 7:44 ` Helmut Schaa
2010-10-07 7:52 ` Johannes Berg
2010-10-08 17:41 ` Helmut Schaa
2010-10-05 9:55 ` [PATCH 5/5] ath5k: Add busy ratios to survey data Bruno Randolf
2010-10-05 22:38 ` Luis R. Rodriguez
2010-10-06 2:25 ` Bruno Randolf
2010-10-06 2:45 ` Felix Fietkau
2010-10-06 2:50 ` Bruno Randolf
2010-10-06 14:13 ` Luis R. Rodriguez
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=201010061010.46430.br1@einfach.org \
--to=br1@einfach.org \
--cc=Vasanth.Thiagarajan@atheros.com \
--cc=adrian@freebsd.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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 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).