Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 02/24/2015 04:41 AM, Marc Zyngier wrote: On 23/02/15 20:39, Nishanth Menon wrote: On 02/23/2015 02:32 PM, Nishanth Menon wrote: On 17:44-20150223, Marc Zyngier wrote: [...] create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu delete mode 100644 include/linux/irqchip/irq-crossbar.h marc-test-irq (Applied the series to v4.0-rc1) - boot logs: 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2469913 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2469914 3: am3517-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2469915 4: am37x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2469916 5: am437x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2469917 6:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2469918 7: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2469919 8: BeagleBoard-XM: BOOT: PASS: http://paste.ubuntu.org.cn/2469920 9:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2469928 10: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2469932 11: beaglebone: BOOT: PASS: http://paste.ubuntu.org.cn/2469936 12: craneboard: BOOT: PASS: http://paste.ubuntu.org.cn/2469941 13: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2469945 14: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2469946 15: OMAP3430-Labrador(LDP): BOOT: PASS: http://paste.ubuntu.org.cn/2469947 16: n900: BOOT: PASS: http://paste.ubuntu.org.cn/2469948 17: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2469949 18: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2469950 19: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2469951 20:sdp2430: BOOT: PASS: http://paste.ubuntu.org.cn/2469952 21:sdp3430: BOOT: PASS: http://paste.ubuntu.org.cn/2469953 22:sdp4430: BOOT: PASS: http://paste.ubuntu.org.cn/2469954 TOTAL = 22 boards, Booted Boards = 22, No Boot boards = 0 (also tested beagleboard-x15 which was not on farm: http://paste.ubuntu.org.cn/2470017 - looks good as well). Noticed that I missed proper info about x15 here.. anyways.. http://paste.ubuntu.org.cn/2470017 was vanilla v4.0-rc1 http://pastebin.ubuntu.com/10377375/ is with this series applied on top. Comparative boot logs for v4.0-rc1: https://github.com/nmenon/kernel-test-logs/tree/v4.0-rc1 Will dig in detail a little later.. but nothing major stuck out to me. Excellent. Let me know if you spot anything. Can I otherwise add your Tested-by:? Yes please. Sorry that I did not respond earlier. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 2/23/2015 9:44 AM, Marc Zyngier wrote:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Based on 4.0-rc1.
* From v4: [4]
- Extracted from the full series
- Rebased on 4.0-rc1
* From v3 [3]:
- Rebased on top of the patch working around hardcoded IRQ on OMAP4/5 [4]
- Fixed more iMX6 DTs (Stephan)
- Fixed Exynos4/5 DTs
* From v2 [2]:
- Addressed numerous comments from Thierry
- Merged bug fixes from Nishanth
- Merged bug fix from Stefan
* From v1 [1]:
- Rebased on 3.19-rc3
- Fixed a number of additional platforms
- Added crossbar conversion to stacked domains
- Merged bug fixes from Nishanth
[4]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/317531.html
[3]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315385.html
[2]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/314041.html
[1]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/307338.html
Marc Zyngier (7):
genirq: Add irqchip_set_wake_parent
irqchip: crossbar: convert dra7 crossbar to stacked domains
DT: update ti,irq-crossbar binding
irqchip: GIC: get rid of routable domain
DT: arm,gic: kill arm,routable-irqs
DT: omap4/5: add binding for the wake-up generator
ARM: omap: convert wakeupgen to stacked domains
Acked-by: Santosh Shilimkar ssant...@kernel.org
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 23/02/15 23:02, Tony Lindgren wrote:
* Marc Zyngier marc.zyng...@arm.com [150223 09:48]:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Could we parse still the old binding and produce warning for the
case when a new kernel is booted with the old DT? That would make
it easier for people to debug what's going on.
There's a number of strategies:
- Looking up the default, top-level interrupt controller:
if that's the GIC, scream.
- Lookup the crossbar:
if it exists, but is not an interrupt controller, scream as well.
- Lookup the WUGEN:
if it doesn't exist, scream again.
The last one is pretty easy to implement:
diff --git a/arch/arm/mach-omap2/omap4-common.c
b/arch/arm/mach-omap2/omap4-common.c
index fba1ba7..7bb116a 100644
--- a/arch/arm/mach-omap2/omap4-common.c
+++ b/arch/arm/mach-omap2/omap4-common.c
@@ -277,6 +277,12 @@ void __init omap_gic_of_init(void)
{
struct device_node *np;
+ intc_node = of_find_matching_node(NULL, intc_match);
+ if (WARN_ON(!intc_node)) {
+ pr_err(No WUGEN found in DT, system will misbehave.\n);
+ pr_err(UPDATE YOUR DEVICE TREE!\n);
+ }
+
/* Extract GIC distributor and TWD bases for OMAP4460 ROM Errata WA */
if (!cpu_is_omap446x())
goto skip_errata_init;
This should cover both OMAP4, OMAP5 and DRA7.
What do you think?
M.
--
Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 24/02/15 03:45, Subramaniam Chanderashekarapuram wrote: Tested this on DRA7 for smp_affinity. Needs these minor fixes attached. Note: I do not have a OMAP4/5 with me now. Hope to test that tomorrow. Log for DRA7 are here: http://pastebin.ubuntu.com/10382176/ Looks good to me. I've folded that into the existing series. Thanks, M. -- Jazz is not dead. It just smells funny... -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 23/02/15 20:39, Nishanth Menon wrote:
On 02/23/2015 02:32 PM, Nishanth Menon wrote:
On 17:44-20150223, Marc Zyngier wrote:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Based on 4.0-rc1.
* From v4: [4]
- Extracted from the full series
- Rebased on 4.0-rc1
* From v3 [3]:
- Rebased on top of the patch working around hardcoded IRQ on OMAP4/5 [4]
- Fixed more iMX6 DTs (Stephan)
- Fixed Exynos4/5 DTs
* From v2 [2]:
- Addressed numerous comments from Thierry
- Merged bug fixes from Nishanth
- Merged bug fix from Stefan
* From v1 [1]:
- Rebased on 3.19-rc3
- Fixed a number of additional platforms
- Added crossbar conversion to stacked domains
- Merged bug fixes from Nishanth
[4]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/317531.html
[3]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315385.html
[2]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/314041.html
[1]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/307338.html
Marc Zyngier (7):
genirq: Add irqchip_set_wake_parent
irqchip: crossbar: convert dra7 crossbar to stacked domains
DT: update ti,irq-crossbar binding
irqchip: GIC: get rid of routable domain
DT: arm,gic: kill arm,routable-irqs
DT: omap4/5: add binding for the wake-up generator
ARM: omap: convert wakeupgen to stacked domains
Documentation/devicetree/bindings/arm/gic.txt | 6 -
.../devicetree/bindings/arm/omap/crossbar.txt | 18 +-
.../interrupt-controller/ti,omap4-wugen-mpu| 33
arch/arm/boot/dts/am4372.dtsi | 11 +-
arch/arm/boot/dts/am437x-gp-evm.dts| 1 -
arch/arm/boot/dts/am437x-sk-evm.dts| 1 -
arch/arm/boot/dts/am43x-epos-evm.dts | 1 -
arch/arm/boot/dts/am57xx-beagle-x15.dts| 3 +-
arch/arm/boot/dts/dra7-evm.dts | 2 +-
arch/arm/boot/dts/dra7.dtsi| 43 +++--
arch/arm/boot/dts/dra72-evm.dts| 1 -
arch/arm/boot/dts/dra72x.dtsi | 3 +-
arch/arm/boot/dts/dra74x.dtsi | 5 +-
arch/arm/boot/dts/omap4-duovero.dtsi | 2 -
arch/arm/boot/dts/omap4-panda-common.dtsi | 8 +-
arch/arm/boot/dts/omap4-sdp.dts| 8 +-
arch/arm/boot/dts/omap4-var-som-om44.dtsi | 2 -
arch/arm/boot/dts/omap4.dtsi | 18 +-
arch/arm/boot/dts/omap5-cm-t54.dts | 1 -
arch/arm/boot/dts/omap5-uevm.dts | 2 -
arch/arm/boot/dts/omap5.dtsi | 26 ++-
arch/arm/mach-omap2/omap-wakeupgen.c | 125 ++---
arch/arm/mach-omap2/omap-wakeupgen.h | 1 -
arch/arm/mach-omap2/omap4-common.c | 21 +--
drivers/irqchip/irq-crossbar.c | 207
-
drivers/irqchip/irq-gic.c | 59 +-
include/linux/irq.h| 1 +
include/linux/irqchip/arm-gic.h| 6 -
include/linux/irqchip/irq-crossbar.h | 11 --
kernel/irq/chip.c | 16 ++
30 files changed, 364 insertions(+), 278 deletions(-)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
delete mode 100644 include/linux/irqchip/irq-crossbar.h
marc-test-irq (Applied the series to v4.0-rc1) - boot logs:
1: am335x-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469913
2: am335x-sk: BOOT: PASS:
http://paste.ubuntu.org.cn/2469914
3: am3517-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469915
4: am37x-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469916
5: am437x-sk: BOOT: PASS:
http://paste.ubuntu.org.cn/2469917
6:am43xx-epos: BOOT: PASS:
http://paste.ubuntu.org.cn/2469918
7: am43xx-gpevm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469919
8: BeagleBoard-XM: BOOT: PASS:
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
* Marc Zyngier marc.zyng...@arm.com [150224 01:08]:
On 23/02/15 23:02, Tony Lindgren wrote:
* Marc Zyngier marc.zyng...@arm.com [150223 09:48]:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Could we parse still the old binding and produce warning for the
case when a new kernel is booted with the old DT? That would make
it easier for people to debug what's going on.
There's a number of strategies:
- Looking up the default, top-level interrupt controller:
if that's the GIC, scream.
- Lookup the crossbar:
if it exists, but is not an interrupt controller, scream as well.
- Lookup the WUGEN:
if it doesn't exist, scream again.
The last one is pretty easy to implement:
diff --git a/arch/arm/mach-omap2/omap4-common.c
b/arch/arm/mach-omap2/omap4-common.c
index fba1ba7..7bb116a 100644
--- a/arch/arm/mach-omap2/omap4-common.c
+++ b/arch/arm/mach-omap2/omap4-common.c
@@ -277,6 +277,12 @@ void __init omap_gic_of_init(void)
{
struct device_node *np;
+ intc_node = of_find_matching_node(NULL, intc_match);
+ if (WARN_ON(!intc_node)) {
+ pr_err(No WUGEN found in DT, system will misbehave.\n);
+ pr_err(UPDATE YOUR DEVICE TREE!\n);
+ }
+
/* Extract GIC distributor and TWD bases for OMAP4460 ROM Errata WA */
if (!cpu_is_omap446x())
goto skip_errata_init;
This should cover both OMAP4, OMAP5 and DRA7.
What do you think?
This should do the job for the case of old dtb and people trying to
suspend the device.
Thanks,
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Based on 4.0-rc1.
* From v4: [4]
- Extracted from the full series
- Rebased on 4.0-rc1
* From v3 [3]:
- Rebased on top of the patch working around hardcoded IRQ on OMAP4/5 [4]
- Fixed more iMX6 DTs (Stephan)
- Fixed Exynos4/5 DTs
* From v2 [2]:
- Addressed numerous comments from Thierry
- Merged bug fixes from Nishanth
- Merged bug fix from Stefan
* From v1 [1]:
- Rebased on 3.19-rc3
- Fixed a number of additional platforms
- Added crossbar conversion to stacked domains
- Merged bug fixes from Nishanth
[4]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/317531.html
[3]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315385.html
[2]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/314041.html
[1]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/307338.html
Marc Zyngier (7):
genirq: Add irqchip_set_wake_parent
irqchip: crossbar: convert dra7 crossbar to stacked domains
DT: update ti,irq-crossbar binding
irqchip: GIC: get rid of routable domain
DT: arm,gic: kill arm,routable-irqs
DT: omap4/5: add binding for the wake-up generator
ARM: omap: convert wakeupgen to stacked domains
Documentation/devicetree/bindings/arm/gic.txt | 6 -
.../devicetree/bindings/arm/omap/crossbar.txt | 18 +-
.../interrupt-controller/ti,omap4-wugen-mpu| 33
arch/arm/boot/dts/am4372.dtsi | 11 +-
arch/arm/boot/dts/am437x-gp-evm.dts| 1 -
arch/arm/boot/dts/am437x-sk-evm.dts| 1 -
arch/arm/boot/dts/am43x-epos-evm.dts | 1 -
arch/arm/boot/dts/am57xx-beagle-x15.dts| 3 +-
arch/arm/boot/dts/dra7-evm.dts | 2 +-
arch/arm/boot/dts/dra7.dtsi| 43 +++--
arch/arm/boot/dts/dra72-evm.dts| 1 -
arch/arm/boot/dts/dra72x.dtsi | 3 +-
arch/arm/boot/dts/dra74x.dtsi | 5 +-
arch/arm/boot/dts/omap4-duovero.dtsi | 2 -
arch/arm/boot/dts/omap4-panda-common.dtsi | 8 +-
arch/arm/boot/dts/omap4-sdp.dts| 8 +-
arch/arm/boot/dts/omap4-var-som-om44.dtsi | 2 -
arch/arm/boot/dts/omap4.dtsi | 18 +-
arch/arm/boot/dts/omap5-cm-t54.dts | 1 -
arch/arm/boot/dts/omap5-uevm.dts | 2 -
arch/arm/boot/dts/omap5.dtsi | 26 ++-
arch/arm/mach-omap2/omap-wakeupgen.c | 125 ++---
arch/arm/mach-omap2/omap-wakeupgen.h | 1 -
arch/arm/mach-omap2/omap4-common.c | 21 +--
drivers/irqchip/irq-crossbar.c | 207 -
drivers/irqchip/irq-gic.c | 59 +-
include/linux/irq.h| 1 +
include/linux/irqchip/arm-gic.h| 6 -
include/linux/irqchip/irq-crossbar.h | 11 --
kernel/irq/chip.c | 16 ++
30 files changed, 364 insertions(+), 278 deletions(-)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
delete mode 100644 include/linux/irqchip/irq-crossbar.h
--
2.1.4
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 02/23/2015 02:32 PM, Nishanth Menon wrote:
On 17:44-20150223, Marc Zyngier wrote:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Based on 4.0-rc1.
* From v4: [4]
- Extracted from the full series
- Rebased on 4.0-rc1
* From v3 [3]:
- Rebased on top of the patch working around hardcoded IRQ on OMAP4/5 [4]
- Fixed more iMX6 DTs (Stephan)
- Fixed Exynos4/5 DTs
* From v2 [2]:
- Addressed numerous comments from Thierry
- Merged bug fixes from Nishanth
- Merged bug fix from Stefan
* From v1 [1]:
- Rebased on 3.19-rc3
- Fixed a number of additional platforms
- Added crossbar conversion to stacked domains
- Merged bug fixes from Nishanth
[4]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/317531.html
[3]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315385.html
[2]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/314041.html
[1]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/307338.html
Marc Zyngier (7):
genirq: Add irqchip_set_wake_parent
irqchip: crossbar: convert dra7 crossbar to stacked domains
DT: update ti,irq-crossbar binding
irqchip: GIC: get rid of routable domain
DT: arm,gic: kill arm,routable-irqs
DT: omap4/5: add binding for the wake-up generator
ARM: omap: convert wakeupgen to stacked domains
Documentation/devicetree/bindings/arm/gic.txt | 6 -
.../devicetree/bindings/arm/omap/crossbar.txt | 18 +-
.../interrupt-controller/ti,omap4-wugen-mpu| 33
arch/arm/boot/dts/am4372.dtsi | 11 +-
arch/arm/boot/dts/am437x-gp-evm.dts| 1 -
arch/arm/boot/dts/am437x-sk-evm.dts| 1 -
arch/arm/boot/dts/am43x-epos-evm.dts | 1 -
arch/arm/boot/dts/am57xx-beagle-x15.dts| 3 +-
arch/arm/boot/dts/dra7-evm.dts | 2 +-
arch/arm/boot/dts/dra7.dtsi| 43 +++--
arch/arm/boot/dts/dra72-evm.dts| 1 -
arch/arm/boot/dts/dra72x.dtsi | 3 +-
arch/arm/boot/dts/dra74x.dtsi | 5 +-
arch/arm/boot/dts/omap4-duovero.dtsi | 2 -
arch/arm/boot/dts/omap4-panda-common.dtsi | 8 +-
arch/arm/boot/dts/omap4-sdp.dts| 8 +-
arch/arm/boot/dts/omap4-var-som-om44.dtsi | 2 -
arch/arm/boot/dts/omap4.dtsi | 18 +-
arch/arm/boot/dts/omap5-cm-t54.dts | 1 -
arch/arm/boot/dts/omap5-uevm.dts | 2 -
arch/arm/boot/dts/omap5.dtsi | 26 ++-
arch/arm/mach-omap2/omap-wakeupgen.c | 125 ++---
arch/arm/mach-omap2/omap-wakeupgen.h | 1 -
arch/arm/mach-omap2/omap4-common.c | 21 +--
drivers/irqchip/irq-crossbar.c | 207
-
drivers/irqchip/irq-gic.c | 59 +-
include/linux/irq.h| 1 +
include/linux/irqchip/arm-gic.h| 6 -
include/linux/irqchip/irq-crossbar.h | 11 --
kernel/irq/chip.c | 16 ++
30 files changed, 364 insertions(+), 278 deletions(-)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
delete mode 100644 include/linux/irqchip/irq-crossbar.h
marc-test-irq (Applied the series to v4.0-rc1) - boot logs:
1: am335x-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469913
2: am335x-sk: BOOT: PASS:
http://paste.ubuntu.org.cn/2469914
3: am3517-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469915
4: am37x-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469916
5: am437x-sk: BOOT: PASS:
http://paste.ubuntu.org.cn/2469917
6:am43xx-epos: BOOT: PASS:
http://paste.ubuntu.org.cn/2469918
7: am43xx-gpevm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469919
8: BeagleBoard-XM: BOOT: PASS:
http://paste.ubuntu.org.cn/2469920
9:
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
On 17:44-20150223, Marc Zyngier wrote:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Based on 4.0-rc1.
* From v4: [4]
- Extracted from the full series
- Rebased on 4.0-rc1
* From v3 [3]:
- Rebased on top of the patch working around hardcoded IRQ on OMAP4/5 [4]
- Fixed more iMX6 DTs (Stephan)
- Fixed Exynos4/5 DTs
* From v2 [2]:
- Addressed numerous comments from Thierry
- Merged bug fixes from Nishanth
- Merged bug fix from Stefan
* From v1 [1]:
- Rebased on 3.19-rc3
- Fixed a number of additional platforms
- Added crossbar conversion to stacked domains
- Merged bug fixes from Nishanth
[4]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/317531.html
[3]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/315385.html
[2]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/314041.html
[1]:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/307338.html
Marc Zyngier (7):
genirq: Add irqchip_set_wake_parent
irqchip: crossbar: convert dra7 crossbar to stacked domains
DT: update ti,irq-crossbar binding
irqchip: GIC: get rid of routable domain
DT: arm,gic: kill arm,routable-irqs
DT: omap4/5: add binding for the wake-up generator
ARM: omap: convert wakeupgen to stacked domains
Documentation/devicetree/bindings/arm/gic.txt | 6 -
.../devicetree/bindings/arm/omap/crossbar.txt | 18 +-
.../interrupt-controller/ti,omap4-wugen-mpu| 33
arch/arm/boot/dts/am4372.dtsi | 11 +-
arch/arm/boot/dts/am437x-gp-evm.dts| 1 -
arch/arm/boot/dts/am437x-sk-evm.dts| 1 -
arch/arm/boot/dts/am43x-epos-evm.dts | 1 -
arch/arm/boot/dts/am57xx-beagle-x15.dts| 3 +-
arch/arm/boot/dts/dra7-evm.dts | 2 +-
arch/arm/boot/dts/dra7.dtsi| 43 +++--
arch/arm/boot/dts/dra72-evm.dts| 1 -
arch/arm/boot/dts/dra72x.dtsi | 3 +-
arch/arm/boot/dts/dra74x.dtsi | 5 +-
arch/arm/boot/dts/omap4-duovero.dtsi | 2 -
arch/arm/boot/dts/omap4-panda-common.dtsi | 8 +-
arch/arm/boot/dts/omap4-sdp.dts| 8 +-
arch/arm/boot/dts/omap4-var-som-om44.dtsi | 2 -
arch/arm/boot/dts/omap4.dtsi | 18 +-
arch/arm/boot/dts/omap5-cm-t54.dts | 1 -
arch/arm/boot/dts/omap5-uevm.dts | 2 -
arch/arm/boot/dts/omap5.dtsi | 26 ++-
arch/arm/mach-omap2/omap-wakeupgen.c | 125 ++---
arch/arm/mach-omap2/omap-wakeupgen.h | 1 -
arch/arm/mach-omap2/omap4-common.c | 21 +--
drivers/irqchip/irq-crossbar.c | 207
-
drivers/irqchip/irq-gic.c | 59 +-
include/linux/irq.h| 1 +
include/linux/irqchip/arm-gic.h| 6 -
include/linux/irqchip/irq-crossbar.h | 11 --
kernel/irq/chip.c | 16 ++
30 files changed, 364 insertions(+), 278 deletions(-)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/ti,omap4-wugen-mpu
delete mode 100644 include/linux/irqchip/irq-crossbar.h
marc-test-irq (Applied the series to v4.0-rc1) - boot logs:
1: am335x-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469913
2: am335x-sk: BOOT: PASS:
http://paste.ubuntu.org.cn/2469914
3: am3517-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469915
4: am37x-evm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469916
5: am437x-sk: BOOT: PASS:
http://paste.ubuntu.org.cn/2469917
6:am43xx-epos: BOOT: PASS:
http://paste.ubuntu.org.cn/2469918
7: am43xx-gpevm: BOOT: PASS:
http://paste.ubuntu.org.cn/2469919
8: BeagleBoard-XM: BOOT: PASS:
http://paste.ubuntu.org.cn/2469920
9:beagleboard-vanilla: BOOT: PASS:
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
* Marc Zyngier marc.zyng...@arm.com [150223 09:48]:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Could we parse still the old binding and produce warning for the
case when a new kernel is booted with the old DT? That would make
it easier for people to debug what's going on.
Regards,
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v5 0/7] irqchip: Move OMAP{4,5}/DRA7 to use stacked domains
* Tony Lindgren t...@atomide.com [150223 15:10]:
* Marc Zyngier marc.zyng...@arm.com [150223 09:48]:
This series is extracted from [4], which is trying to remove all
traces of gic_arch_extn from the tree. As some maintainers are more
responsive than others (understatement of the year...), I've decided
to split it per sub-arch, and get it moving, at least partially.
This series addresses OMAP{4,5} by converting the WUGEN to stacked
domains. The DRA7 crossbar gets the same treatment.
It is worth realizing that:
- I haven't been able to test this as much as I would have wanted to
(it's only been tested on omap4 and omap5).
- This actively *breaks* existing setups. Once you boot a new kernel
with an old DT, suspend/resume *will* be broken. Old kernels on a
new DT won't even boot! You've been warned. This really outline the
necessity of actually describing the HW in device trees...
Could we parse still the old binding and produce warning for the
case when a new kernel is booted with the old DT? That would make
it easier for people to debug what's going on.
Other than that, this series seems to behave for me. Please feel
free to add Acked-by: Tony Lindgren t...@atomide.com. It Looks
like this series should be applied into an immutable branch
against v4.0-rc1 that I can pull in as needed to avoid merge
conflicts with the dts files.
Regards,
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
