From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Purna Chandra Mandal
<purna.mandal-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 2/2] spi: pic32-sqi: add SPI driver for PIC32 SQI controller.
Date: Fri, 15 Apr 2016 10:35:35 +0100 [thread overview]
Message-ID: <20160415093535.GD3217@sirena.org.uk> (raw)
In-Reply-To: <57108A63.50803-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On Fri, Apr 15, 2016 at 11:59:55AM +0530, Purna Chandra Mandal wrote:
> On 04/14/2016 11:25 AM, Mark Brown wrote:
> > On Wed, Apr 13, 2016 at 06:52:58PM +0530, Purna Chandra Mandal wrote:
> >> + enable = readl(sqi->regs + PESQI_INT_ENABLE_REG);
> >> + status = readl(sqi->regs + PESQI_INT_STAT_REG);
> >> + if (!status)
> >> + return IRQ_NONE;
> > For robustness the check should be if there was anything handled, not if
> > there was anything set.
> In PESQI controller INT_STAT_REG specifies interrupting reason(s) as usual,
> but mostly to confirm completion of on-going DMA operation. It is sticky,
> no way to acknowledge the interrupt source except masking the source.
> In short, whole interrupt logic is mere extension of status polling logic.
> And in driver isr logic is completely depended on the INT_STAT_REG; if status
> is zero no handling can be done and is unexpected!
That's fine, if something goes wrong there's error handling in genirq
which will notice that the interrupt is screaming and disable it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-04-15 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 13:22 [PATCH v2 1/2] spi: pic32-sqi: add binding document for PIC32 Quad-SPI driver Purna Chandra Mandal
2016-04-13 13:22 ` [PATCH v2 2/2] spi: pic32-sqi: add SPI driver for PIC32 SQI controller Purna Chandra Mandal
[not found] ` <1460553778-1662-2-git-send-email-purna.mandal-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2016-04-14 5:55 ` Mark Brown
[not found] ` <20160414055546.GA18024-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-04-15 6:29 ` Purna Chandra Mandal
[not found] ` <57108A63.50803-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2016-04-15 9:35 ` Mark Brown [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=20160415093535.GD3217@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=purna.mandal-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.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).