From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Sekhar Nori <nsekhar@ti.com>,
Peter Hurley <peter@hurleysoftware.com>,
John Ogness <john.ogness@linutronix.de>,
Tony Lindgren <tony@atomide.com>
Cc: gregkh@linuxfoundation.org, vinod.koul@intel.com,
dan.j.williams@intel.com, peter.ujfalusi@ti.com,
dmaengine@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] serial: omap: robustify for high speed transfers
Date: Wed, 24 Feb 2016 16:46:34 +0100 [thread overview]
Message-ID: <56CDD05A.7050402@linutronix.de> (raw)
In-Reply-To: <56CDCE2A.30809@ti.com>
On 02/24/2016 04:37 PM, Sekhar Nori wrote:
> I don't see the error interrupt count in /proc/interrupts go up although
> the code is returning IRQ_NONE when this happens. I initially thought
> that must be because of the interrupt being IRQF_SHARED. But getting rid
> of IRQF_SHARED still does not lead to error count going up. I need to
> spend some more time to see what is going on.
that error counter goes up if the interrupt controller can not find an
interrupt number. That means a HW interrupt was raised but after
checking the interrupt source (by the GIC) there is none. In this case
we have one: the UART.
> Regards,
> Sekhar
Sebastian
next prev parent reply other threads:[~2016-02-24 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 10:27 [PATCH 0/4] serial: omap: robustify for high speed transfers John Ogness
2016-01-25 18:56 ` Peter Hurley
2016-01-29 16:35 ` John Ogness
2016-02-03 1:21 ` Peter Hurley
2016-02-11 12:02 ` John Ogness
2016-02-11 21:00 ` Tony Lindgren
2016-02-22 15:30 ` John Ogness
2016-02-22 19:38 ` Tony Lindgren
2016-02-23 9:59 ` Sekhar Nori
2016-02-23 12:43 ` Sebastian Andrzej Siewior
2016-02-23 16:56 ` Andy Shevchenko
2016-02-24 3:20 ` Peter Hurley
2016-02-24 15:37 ` Sekhar Nori
2016-02-24 15:46 ` Sebastian Andrzej Siewior [this message]
2016-03-07 20:23 ` Peter Hurley
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=56CDD05A.7050402@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=peter@hurleysoftware.com \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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).