From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] spi: bcm2835aux: ensure interrupts are enabled for shared handler
Date: Thu, 03 May 2018 14:15:32 -0700 [thread overview]
Message-ID: <87efiso2yz.fsf@anholt.net> (raw)
In-Reply-To: <20180503180945.3502-1-robh@kernel.org>
Rob Herring <robh@kernel.org> writes:
> The BCM2835 AUX SPI has a shared interrupt line (with AUX UART).
> Downstream fixes this with an AUX irqchip to demux the IRQ sources and a
> DT change which breaks compatibility with older kernels. The AUX irqchip
> was already rejected for upstream[1] and the DT change would break
> working systems if the DTB is updated to a newer one. The latter issue
> was brought to my attention by Alex Graf.
>
> The root cause however is a bug in the shared handler. Shared handlers
> must check that interrupts are actually enabled before servicing the
> interrupt. Add a check that the TXEMPTY or IDLE interrupts are enabled.
It looks to me like we'd only return IRQ_HANDLED if we did work that
needed doing. Is this check effectively doing some interlock to make
sure that we've already started bcm2835aux_spi_transfer_one_irq() and
aren't just racing against transaction setup?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180503/566dc920/attachment.sig>
next prev parent reply other threads:[~2018-05-03 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 18:09 [PATCH] spi: bcm2835aux: ensure interrupts are enabled for shared handler Rob Herring
2018-05-03 18:31 ` Stefan Wahren
2018-05-03 21:15 ` Eric Anholt [this message]
2018-05-03 22:06 ` Rob Herring
2018-05-03 22:36 ` Eric Anholt
2018-05-03 23:06 ` Mark Brown
2018-05-03 23:19 ` Applied "spi: bcm2835aux: ensure interrupts are enabled for shared handler" to the spi tree Mark Brown
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=87efiso2yz.fsf@anholt.net \
--to=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.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