From: Christian Lamparter <chunkeey@googlemail.com>
To: "David H. Lynch Jr." <dhlii@dlasys.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: CARL9170
Date: Tue, 15 Jun 2010 00:32:53 +0200 [thread overview]
Message-ID: <201006150032.54095.chunkeey@googlemail.com> (raw)
In-Reply-To: <4C169610.5020907@dlasys.net>
On Monday 14 June 2010 22:50:24 David H. Lynch Jr. wrote:
> Many routines are coded to look like interrupt handlers, but the
> code seems to be entirely polled ?
Hardware design decision.
(See "AR9170 STA Programming Guide" - Paragraph 3-3.)
> Am I correct there ? If so do you know if the AR9170-fw code or
> something else might show an example of interrupt handling for the
> AR9170. I must have tx complete interrupts.
Well you have to "poll" the MAC's WLAN Status Registers (0x1c3510?) for
BIT(0)=TX COMP (and BIT(2) = TX FAIL) changes...
Or, if you are only sending one frame at a time, you might be able to poll
0x1c36d4 instead. Also you could decrease the maximum pending tx "interrupt"
timeout in 0x1c3d7c etc...
But if that does not satisfy your need for "real-time responsiveness", you
should contact Stephen Chen @ Atheros directly, maybe he knows a undocumented
feature register which enables real-time interrupt processing.
> Next there are remarks throught the driver and firmware regarding
> cookies.
> I think a cookie is a u8 that uniquely identifies a packet - is
> that correct ?
>
> In the firmware there is a remark somewhere that suguests that the
> cookie AND something else are needed - is that correct or is the cookie
> sufficient ?
This is because of historic reasons. In ar9170usb the driver had
use dirty tricks to get the AC_ID into the firmware's tx report.
So it could do some primitive frame lookup.
carl9170 driver still needs the AC_ID (but now) to reduce the frame lookup cost.
This is somewhat necessary because tx feedback is usually processed in a
critical section and when aggregation is enabled, it can be up to 16 frames
at any time...
regards,
Chr
next prev parent reply other threads:[~2010-06-14 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 20:50 CARL9170 David H. Lynch Jr.
2010-06-14 22:32 ` Christian Lamparter [this message]
2010-07-27 19:25 ` CARL9170 Ignacy Gawedzki
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=201006150032.54095.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=dhlii@dlasys.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;
as well as URLs for NNTP newsgroup(s).