[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1532684881-19310-1-git-send-email-Bharat.Bhushan@nxp.com>
Date: Fri, 27 Jul 2018 15:17:56 +0530
From: Bharat Bhushan <Bharat.Bhushan@....com>
To: benh@...nel.crashing.org, paulus@...ba.org, mpe@...erman.id.au,
oss@...error.net, galak@...nel.crashing.org, mark.rutland@....com,
kstewart@...uxfoundation.org, gregkh@...uxfoundation.org,
devicetree@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org
Cc: robh@...nel.org, keescook@...omium.org, tyreld@...ux.vnet.ibm.com,
joe@...ches.com, Bharat Bhushan <Bharat.Bhushan@....com>
Subject: [RFC 0/5] powerpc/mpic: Add non-contiguous interrupt sources
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
Powered by blists - more mailing lists