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 Exynos by converting its PM support to a stacked domain on top of the standard GIC. Based on 4.0-rc1. * From v5: [5] - Added a big fat warning when an old DT is detected (as requested by Jason) - Added support for Exynos3250 - Allow interrupt affinity to be changed * 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 [5]: http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/325368.html [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 (2): ARM: exynos4/5: convert pmu wakeup to stacked domains DT: exynos: update PMU binding .../devicetree/bindings/arm/samsung/pmu.txt | 17 +++ arch/arm/boot/dts/exynos3250.dtsi | 6 +- arch/arm/boot/dts/exynos4.dtsi | 4 + arch/arm/boot/dts/exynos5250.dtsi | 4 + arch/arm/boot/dts/exynos5420.dtsi | 4 + arch/arm/mach-exynos/exynos.c | 15 +-- arch/arm/mach-exynos/suspend.c | 139 ++++++++++++++++++--- 7 files changed, 164 insertions(+), 25 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |