ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: Lamar Hansford <Lamar.Hansford@maxpoint.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Interrupt issue on ARM with SMP
Date: Mon, 29 Aug 2016 15:27:09 +0000	[thread overview]
Message-ID: <F9D95AC275991E48901933FBF3337AB0A3315F75@ex-02> (raw)
In-Reply-To: <CAJ-VmonaO6M7KJt1gyMbPgj5eiZ250fkeEOX0S8MA40=o1xiQQ@mail.gmail.com>

Another error on my end.  I've ignored any interrupts which do not have async/sync cause and added a mitigation timer and interrupts are firing as expected.   Of course now the packets are getting thrown away at the DMA :).  That is likely due to a BSP issue.

Thanks for all of the help!
-Lamar

-----Original Message-----
From: adrian.chadd@gmail.com [mailto:adrian.chadd at gmail.com] On Behalf Of Adrian Chadd
Sent: Saturday, August 27, 2016 11:45 PM
To: Lamar Hansford
Cc: ath9k-devel at lists.ath9k.org
Subject: Re: [ath9k-devel] Interrupt issue on ARM with SMP

Hi,

So, interrupt handling is finnicky. It's possible there's already a posted interrupt waiting somewhere. Ideally you'd do a write-then-read in each of the interrupt blocks between your device and the CPU to ensure thing are synced. Otherwise the different frequencies in different blocks in the ARM code mean you get interrupts after you've cleared the interrupt itself, because it hasn't yet posted in that particular hardware block.

Yay, etc.



-adrian
This email and any attachments may contain private, confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please immediately delete this email and any attachments.

      reply	other threads:[~2016-08-29 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  3:50 [ath9k-devel] Interrupt issue on ARM with SMP Lamar Hansford
2016-08-25 15:48 ` Adrian Chadd
2016-08-25 18:15   ` Lamar Hansford
2016-08-26  1:33     ` Adrian Chadd
2016-08-26 14:35       ` Lamar Hansford
2016-08-28  4:44         ` Adrian Chadd
2016-08-29 15:27           ` Lamar Hansford [this message]

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=F9D95AC275991E48901933FBF3337AB0A3315F75@ex-02 \
    --to=lamar.hansford@maxpoint.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;
as well as URLs for NNTP newsgroup(s).