From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL v2] Renesas ARM Based SoC DT PM Updates for v3.20
Date: Tue, 13 Jan 2015 00:21:08 +0000 [thread overview]
Message-ID: <20150113002105.GA27284@verge.net.au> (raw)
In-Reply-To: <20150112224859.GM22090@quad.lixom.net>
On Mon, Jan 12, 2015 at 02:48:59PM -0800, Olof Johansson wrote:
> Hi Simon,
>
> On Mon, Jan 05, 2015 at 12:52:15PM +0900, Simon Horman wrote:
> > Hi Olof, Hi Kevin, Hi Arnd,
> >
> > Please consider these Renesas ARM based SoC DT PM updates for v3.20.
> >
> >
> > As requested by Geert Uytterhoeven I have dropped
> > "ARM: shmobile: R-Mobile: Enable module clocks if !CONFIG_PM_RUNTIME"
> > from v2 of this pull-request.
> >
> >
> > The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
> >
> > Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-dt-pm-for-v3.20
> >
> > for you to fetch changes up to b21cadc64dc34fb531ad49d462021c2b6a14cfff:
> >
> > ARM: shmobile: r8a7740 dtsi: Add PM domain support (2014-12-31 15:28:31 +0900)
> >
> > ----------------------------------------------------------------
> > Renesas ARM Based SoC DT PM Updates for v3.20
> >
> > * DT support from PM domains
> > * Enable DT support for PM domains on r8a7740
> >
> > ----------------------------------------------------------------
> > Geert Uytterhoeven (5):
> > PM / Domains: Add DT bindings for the R-Mobile System Controller
> > ARM: shmobile: R-Mobile: Use generic_pm_domain.attach_dev() for pm_clk setup
> > ARM: shmobile: R-Mobile: Store SYSC base address in rmobile_pm_domain
> > ARM: shmobile: R-Mobile: Add DT support for PM domains
> > ARM: shmobile: r8a7740 dtsi: Add PM domain support
> >
> > .../bindings/power/renesas,sysc-rmobile.txt | 98 ++++++++
> > arch/arm/boot/dts/r8a7740.dtsi | 99 ++++++++
> > arch/arm/mach-shmobile/Kconfig | 3 +-
> > arch/arm/mach-shmobile/pm-r8a7740.c | 14 ++
> > arch/arm/mach-shmobile/pm-rmobile.c | 273 +++++++++++++++++++--
> > arch/arm/mach-shmobile/pm-rmobile.h | 3 +-
> > arch/arm/mach-shmobile/pm-sh7372.c | 11 +
>
> I think the dts change and the binding change here should go in a dt
> branch, and the rest should probably to in an SoC branch.
>
> Would you mind respinning, or should I cherry-pick them between the branches
> here?
Thanks, I can respin.
prev parent reply other threads:[~2015-01-13 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 3:52 [GIT PULL v2] Renesas ARM Based SoC DT PM Updates for v3.20 Simon Horman
2015-01-05 3:52 ` [PATCH 1/5] PM / Domains: Add DT bindings for the R-Mobile System Controller Simon Horman
2015-01-05 3:52 ` [PATCH 2/5] ARM: shmobile: R-Mobile: Use generic_pm_domain.attach_dev() for pm_clk setup Simon Horman
2015-01-05 3:52 ` [PATCH 3/5] ARM: shmobile: R-Mobile: Store SYSC base address in rmobile_pm_domain Simon Horman
2015-01-05 3:52 ` [PATCH 4/5] ARM: shmobile: R-Mobile: Add DT support for PM domains Simon Horman
2015-01-05 3:52 ` [PATCH 5/5] ARM: shmobile: r8a7740 dtsi: Add PM domain support Simon Horman
2015-01-12 22:48 ` [GIT PULL v2] Renesas ARM Based SoC DT PM Updates for v3.20 Olof Johansson
2015-01-13 0:21 ` Simon Horman [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=20150113002105.GA27284@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).