From: Kukjin Kim <kgene.kim@samsung.com>
To: "'Chander Kashyap'" <k.chander@samsung.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, nicolas.pitre@linaro.org
Cc: linux-arm-kernel@lists.infradead.org, daniel.lezcano@linaro.org,
lorenzo.pieralisi@arm.com, rjw@rjwysocki.net,
tomasz.figa@gmail.com
Subject: RE: [Patch v7 0/6] add cpuidle support for Exynos5420
Date: Tue, 01 Jul 2014 20:52:21 +0900 [thread overview]
Message-ID: <03d501cf9522$eaf67200$c0e35600$@samsung.com> (raw)
In-Reply-To: <1402914383-20471-1-git-send-email-k.chander@samsung.com>
Chander Kashyap wrote:
>
> Exynos5420 is a big-little Soc from Samsung. It has 4 A15 and 4 A7 cores.
>
> This patchset adds cpuidle support for Exynos5420 SoC based on
> generic big.little cpuidle driver.
>
> Tested on SMDK5420.
> Rebased on 3.16-rc1
>
> Changelog is in respective patches.
> Chander Kashyap (5):
> driver: cpuidle-big-little: add of_device_id structure
> arm: exynos: add generic function to calculate cpu number
> cpuidle: config: Add ARCH_EXYNOS entry to select cpuidle-big-little
> driver
> driver: cpuidle: cpuidle-big-little: init driver for Exynos5420
> exynos: cpuidle: do not allow cpuidle registration for Exynos5420
> mcpm: exynos: populate suspend and powered_up callbacks
>
> arch/arm/mach-exynos/exynos.c | 4 +++-
> arch/arm/mach-exynos/mcpm-exynos.c | 36 ++++++++++++++++++++++++++++++++++
> arch/arm/mach-exynos/regs-pmu.h | 9 +++++++++
> drivers/cpuidle/Kconfig.arm | 2 +-
> drivers/cpuidle/cpuidle-big_little.c | 12 +++++++++++-
> 5 files changed, 60 insertions(+), 3 deletions(-)
>
+ Nicolas
Hi,
This series looks good to me and I asked Chander to test this series with
Nico's mcpm patches on smdk5420 and he said it works fine. So I will apply
this into samsung tree if Nicolas has no objection on 6/6.
BTW, one more, there are duplicated sign-off from Chander with different
e-mail address, I'm not sure it should be fine or not because I didn't see
same thing before.
Thanks,
Kukjin
prev parent reply other threads:[~2014-07-01 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 10:26 [Patch v7 0/6] add cpuidle support for Exynos5420 Chander Kashyap
2014-06-16 10:26 ` [Patch v7 1/6] driver: cpuidle-big-little: add of_device_id structure Chander Kashyap
2014-06-16 10:26 ` [Patch v7 2/6] arm: exynos: add generic function to calculate cpu number Chander Kashyap
2014-06-16 10:26 ` [Patch v7 3/6] cpuidle: config: Add ARCH_EXYNOS entry to select cpuidle-big-little driver Chander Kashyap
2014-06-16 10:26 ` [Patch v7 4/6] driver: cpuidle: cpuidle-big-little: init driver for Exynos5420 Chander Kashyap
2014-06-16 10:26 ` [Patch v7 5/6] exynos: cpuidle: do not allow cpuidle registration " Chander Kashyap
2014-06-16 10:26 ` [Patch v7 6/6] mcpm: exynos: populate suspend and powered_up callbacks Chander Kashyap
2014-07-01 11:52 ` Kukjin Kim [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='03d501cf9522$eaf67200$c0e35600$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=daniel.lezcano@linaro.org \
--cc=k.chander@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=tomasz.figa@gmail.com \
/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