From: Bharat Bhushan <Bharat.Bhushan@nxp.com>
To: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
oss@buserror.net, galak@kernel.crashing.org,
mark.rutland@arm.com, kstewart@linuxfoundation.org,
gregkh@linuxfoundation.org, devicetree@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: robh@kernel.org, keescook@chromium.org,
tyreld@linux.vnet.ibm.com, joe@perches.com,
Bharat Bhushan <Bharat.Bhushan@nxp.com>
Subject: [RFC 0/5] powerpc/mpic: Add non-contiguous interrupt sources
Date: Fri, 27 Jul 2018 15:17:56 +0530 [thread overview]
Message-ID: <1532684881-19310-1-git-send-email-Bharat.Bhushan@nxp.com> (raw)
Freescale MPIC h/w may not support all interrupt sources reported
by hardware or "last-interrupt-source" or platform. On these platforms
a misconfigured device tree that assigns one of the reserved
interrupts leaves a non-functioning system without warning.
First Patch just moves the last-irq calculation logic to a function,
Second patch reworks same logic, While I feel that device-tree should
get precedence over platform provided last-irq, but in this series
I have not changed this logic.
Third and fourth patch add non-contiguous interrupt sources support
Fifth patch enables this for P2020RDB-PC for now.
Bharat Bhushan (5):
powerpc/mpic: move last irq logic to function
powerpc/mpic: Rework last source irq calculation logic
powerpc/mpic: Add support for non-contiguous irq ranges
powerpc/mpic: Boot print supported interrupt ranges
powerpc/fsl: Add supported-irq-ranges for P2020
.../devicetree/bindings/powerpc/fsl/mpic.txt | 8 +
arch/powerpc/boot/dts/fsl/p2020si-post.dtsi | 3 +
arch/powerpc/include/asm/mpic.h | 9 +
arch/powerpc/platforms/85xx/mpc85xx_rdb.c | 5 +
arch/powerpc/sysdev/mpic.c | 184 ++++++++++++++++++---
5 files changed, 182 insertions(+), 27 deletions(-)
--
1.9.3
next reply other threads:[~2018-07-27 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 9:47 Bharat Bhushan [this message]
2018-07-27 9:47 ` [RFC 1/5] powerpc/mpic: move last irq logic to function Bharat Bhushan
2018-07-27 9:47 ` [RFC 2/5] powerpc/mpic: Rework last source irq calculation logic Bharat Bhushan
2018-07-27 9:47 ` [RFC 3/5] powerpc/mpic: Add support for non-contiguous irq ranges Bharat Bhushan
2018-08-07 18:09 ` Rob Herring
2018-08-07 21:03 ` Scott Wood
2018-08-08 3:37 ` Bharat Bhushan
2018-08-08 5:50 ` Scott Wood
2018-08-08 5:57 ` Bharat Bhushan
2018-07-27 9:48 ` [RFC 4/5] powerpc/mpic: Boot print supported interrupt ranges Bharat Bhushan
2018-07-27 9:48 ` [RFC 5/5] powerpc/fsl: Add supported-irq-ranges for P2020 Bharat Bhushan
2018-08-07 21:13 ` Scott Wood
2018-08-08 3:44 ` Bharat Bhushan
2018-08-08 5:55 ` Scott Wood
2018-08-08 6:28 ` Bharat Bhushan
2018-08-08 17:57 ` Scott Wood
2018-08-09 3:28 ` Bharat Bhushan
2018-08-09 6:11 ` Scott Wood
2018-08-09 7:04 ` Bharat Bhushan
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=1532684881-19310-1-git-send-email-Bharat.Bhushan@nxp.com \
--to=bharat.bhushan@nxp.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=tyreld@linux.vnet.ibm.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).