From: Ian Molton <ian.molton@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: EMEV2: debugging a Strange IRQ issue on SMP
Date: Tue, 23 Jul 2013 12:34:24 +0000 [thread overview]
Message-ID: <51EE7850.6010002@codethink.co.uk> (raw)
In-Reply-To: <51ED68B8.3070302@codethink.co.uk>
Update 2:
The problem appears to have been "fixed" by adding a small (5, thus far)
value to the next timer event to be set, in the sti timer code.
With this hack, I get reliable timer IRQs. I will investigate further
and submit a patch shortly.
-Ian
next prev parent reply other threads:[~2013-07-23 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 17:15 EMEV2: debugging a Strange IRQ issue on SMP Ian Molton
2013-07-23 10:53 ` Ian Molton
2013-07-23 12:34 ` Ian Molton [this message]
2013-07-24 3:23 ` Magnus Damm
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=51EE7850.6010002@codethink.co.uk \
--to=ian.molton@codethink.co.uk \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.