From: Jason Cooper <jason@lakedaemon.net>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Pankaj Dubey <pankaj.dubey@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/2] irqchip: Move Exynos PM to use stacked domains
Date: Sun, 15 Mar 2015 01:31:31 +0000 [thread overview]
Message-ID: <20150315013131.GC4463@io.lakedaemon.net> (raw)
In-Reply-To: <1426088693-15724-1-git-send-email-marc.zyngier@arm.com>
Marc,
On Wed, Mar 11, 2015 at 03:44:51PM +0000, 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 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(-)
Applied to irqchip/stacked-exynos to give the series some time in -next.
thx,
Jason.
prev parent reply other threads:[~2015-03-15 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 15:44 [PATCH v6 0/2] irqchip: Move Exynos PM to use stacked domains Marc Zyngier
2015-03-11 15:44 ` [PATCH v6 1/2] ARM: exynos4/5: convert pmu wakeup to " Marc Zyngier
2015-03-11 15:44 ` [PATCH v6 2/2] DT: exynos: update PMU binding Marc Zyngier
2015-03-15 1:31 ` Jason Cooper [this message]
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=20150315013131.GC4463@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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