From: lastnoname <lastnoname@163.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] How can i distinguish TXOK and TXDESC interupts
Date: Mon, 18 Jun 2012 11:57:30 +0800 [thread overview]
Message-ID: <003e01cd4d06$7c3ce300$6f00a8c0@what> (raw)
The get_isr function combines the AR_ISR_TXOK ,AR_ISR_TXERR , AR_ISR_TXEOL and AR_ISR_TXDESC interrupts as a ATH9K_INT_TX mask. so I cannot get the actual interrupts from the get_isr function.
I tried to destinguish the interrupts AR_ISR_TXOK ,AR_ISR_TXERR , AR_ISR_TXEOL and AR_ISR_TXDESC. I've tried to read the AR_ISR_S0 and AR_ISR_S1 registers, and found that the AR_ISR_TXOK interrupt always appears togerther with the AR_ISR_TXDESC interrupt, though the AR_IMR,AR_IMR_S0 and AR_IMR_S1 interrupt related bits are set. I have no idea how to distinguish the time when the frame is being transmitted(AR_ISR_TXDESC interrupt theoretically) and when the frame is acked (AR_ISR_TXOK interrupt theoretically). I just want to measure the time delay between such two events.
So, How can i distinguish TXOK and TXDESC interupts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120618/108d025a/attachment.htm
reply other threads:[~2012-06-18 3:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='003e01cd4d06$7c3ce300$6f00a8c0@what' \
--to=lastnoname@163.com \
--cc=ath9k-devel@lists.ath9k.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