[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1416902662-19281-1-git-send-email-yingjoe.chen@mediatek.com>
Date: Tue, 25 Nov 2014 16:04:18 +0800
From: Yingjoe Chen <yingjoe.chen@...iatek.com>
To: Mark Rutland <mark.rutland@....com>,
Jason Cooper <jason@...edaemon.net>,
Thomas Gleixner <tglx@...utronix.de>,
Jiang Liu <jiang.liu@...ux.intel.com>,
Marc Zyngier <marc.zyngier@....com>
CC: Boris BREZILLON <boris.brezillon@...e-electrons.com>,
Russell King <linux@....linux.org.uk>,
Pawel Moll <pawel.moll@....com>, <devicetree@...r.kernel.org>,
<hc.yen@...iatek.com>, <srv_heupstream@...iatek.com>,
<yh.chen@...iatek.com>, <linux-kernel@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
Yijing Wang <wangyijing@...wei.com>,
Rob Herring <robh+dt@...nel.org>, <nathan.chung@...iatek.com>,
<yingjoe.chen@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Yingjoe Chen <yingjoe.chen@...iatek.com>,
<eddie.huang@...iatek.com>, Bjorn Helgaas <bhelgaas@...gle.com>,
Sascha Hauer <kernel@...gutronix.de>,
<linux-arm-kernel@...ts.infradead.org>
Subject: [PATCH v8 0/4] ARM: mediatek: Add support for interrupt polarity
This series is 8th version of interrupt polarity support for MediaTek SoCs.
I rebased previous version to latest tip/irq/irqdomain, and fix issues
raised by Marc & Mark. The interrupt & irq free work fine on mt8135 board.
Simplified block diagram for interrupt on my system:
+-------+ +-------+
---| SYSIRQ|------|ARM GIC|
---| |------| |
---| |------| |
---| |------| |
---| |------| |
+-------+ +-------+
In device tree, interrupt-parent for other devices is sysirq, child of gic.
This describe HW better and allow device to specify polarity as it is sent
by the device.
When using hierarchy irq domain, gic will use irq_domain_add_linear to
create irqdomain and all interrupt numbers must come from device tree. My
/proc/interrupts looks like this now:
# cat /proc/interrupts
CPU0
16: 149578 MT_SYSIRQ 113 mtk_timer
20: 1082 MT_SYSIRQ 54 serial
Changes in v8:
- Rebased to new tip/irq/irqdomain
- Update mediatek,sysirq.txt bindinds to document interrupt-cells format
and interrupt-parents
- Change interrupt-cells format check in mtk_sysirq.
- Minor coding style fix
Changes in v7:
- Discussed in [1]
- Rebased to tip/irq/irqdomain
- In mtk_sysirq_domain_alloc, use copy of irq_data to workaound of_node
check in gic_irq_domain_xlate.
Changes in v6:
- Discussed in [2]
- Rebased to tip/irq/irqdomain
Changes in v5:
- Discussed in [3]
- Fix bug on mt6589 reported by Matthias
- Fix bug for irq_find_mapping in irq_create_of_mapping
- Merge Marc's change to proper handle non-DT case in gic_init_bases
Changes in v4:
- Discussed in [4]
- Remove arm,hierarchy-irq-domain. When GIC is probed by DT, it will
support hierarchy irqdomain.
Changes in v3:
- Discussed in [5]
- First implementation using hierarchy irqdomain
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/304119.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/302221.html
[3] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/298161.html
[4] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/296911.html
[5] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/293766.html
Yingjoe Chen (4):
irqchip: gic: Support hierarchy irq domain.
ARM: mediatek: Add sysirq interrupt polarity support
ARM: mediatek: Add sysirq in mt6589/mt8135/mt8127 dtsi
dt-bindings: add bindings for mediatek sysirq
.../bindings/arm/mediatek/mediatek,sysirq.txt | 28 ++++
arch/arm/boot/dts/mt6589.dtsi | 14 +-
arch/arm/boot/dts/mt8127.dtsi | 14 +-
arch/arm/boot/dts/mt8135.dtsi | 14 +-
drivers/irqchip/Kconfig | 1 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-gic.c | 77 +++++++---
drivers/irqchip/irq-mtk-sysirq.c | 163 +++++++++++++++++++++
8 files changed, 282 insertions(+), 30 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,sysirq.txt
create mode 100644 drivers/irqchip/irq-mtk-sysirq.c
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists