From: Kukjin Kim <kgene.kim@samsung.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Chander Kashyap <chander.kashyap@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, lorenzo.pieralisi@arm.com,
daniel.lezcano@linaro.org, kgene.kim@samsung.com
Subject: Re: [Patch v2 0/4] add cpuidle support for Exynos5420
Date: Thu, 24 Apr 2014 00:42:11 +0900 [thread overview]
Message-ID: <5357DF53.4010806@samsung.com> (raw)
In-Reply-To: <4517423.BmCv8cudjC@vostro.rjw.lan>
On 04/23/14 19:18, Rafael J. Wysocki wrote:
> On Wednesday, April 23, 2014 02:55:50 PM 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.
>>
>> This patch set depends on:
>> 1. [PATCH 0/5] MCPM backend for Exynos5420
>> http://www.spinics.net/lists/arm-kernel/msg321666.html
>>
>> 2. [PATCH v4] arm: exynos: generalize power register address calculation
>> http://www.spinics.net/lists/arm-kernel/msg324024.html
>>
>> Changelog is in respective patches.
>> Chander Kashyap (4):
>> cpuidle: config: Add SOC_EXYNOS5420 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/cpuidle.c | 3 ++
>> arch/arm/mach-exynos/mcpm-exynos.c | 53 ++++++++++++++++++++++++++++++++++
>> drivers/cpuidle/Kconfig.arm | 2 +-
>> drivers/cpuidle/cpuidle-big_little.c | 3 +-
>> 4 files changed, 59 insertions(+), 2 deletions(-)
>
> I'm assuming that the Exynos maintainers will take care of this, correct?
>
Yeah, I will if you have any objection :-)
BTW, I need to look at the dependent patches.
- Kukjin
next prev parent reply other threads:[~2014-04-23 15:42 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 11:49 [PATCH 0/4] add cpuidle support for Exynos5420 Chander Kashyap
2014-04-21 11:49 ` [PATCH 1/4] cpuidle: config: Add SOC_EXYNOS5420 entry to select cpuidle-big-little driver Chander Kashyap
2014-04-22 10:42 ` Daniel Lezcano
2014-04-23 6:20 ` Chander Kashyap
2014-04-21 11:49 ` [PATCH 2/4] driver: cpuidle: cpuidle-big-little: init driver for Exynos5420 Chander Kashyap
2014-04-22 10:39 ` Daniel Lezcano
2014-04-22 11:12 ` Daniel Lezcano
2014-04-21 11:49 ` [PATCH 3/4] exynos: cpuidle: do not allow cpuidle registration " Chander Kashyap
2014-04-22 10:38 ` Daniel Lezcano
2014-04-21 11:49 ` [PATCH 4/4] mcpm: exynos: populate suspend and powered_up callbacks Chander Kashyap
2014-04-22 10:51 ` Daniel Lezcano
2014-04-23 8:22 ` Chander Kashyap
2014-04-23 9:25 ` [Patch v2 0/4] add cpuidle support for Exynos5420 Chander Kashyap
2014-04-23 9:25 ` [Patch v2 1/4] cpuidle: config: Add SOC_EXYNOS5420 entry to select cpuidle-big-little driver Chander Kashyap
2014-04-23 9:25 ` [Patch v2 2/4] driver: cpuidle: cpuidle-big-little: init driver for Exynos5420 Chander Kashyap
2014-04-23 16:32 ` Lorenzo Pieralisi
2014-04-24 7:47 ` Chander Kashyap
2014-04-23 9:25 ` [Patch v2 3/4] exynos: cpuidle: do not allow cpuidle registration " Chander Kashyap
2014-04-23 9:25 ` [Patch v2 4/4] mcpm: exynos: populate suspend and powered_up callbacks Chander Kashyap
2014-04-23 16:02 ` Lorenzo Pieralisi
2014-04-24 7:44 ` Chander Kashyap
2014-04-23 10:18 ` [Patch v2 0/4] add cpuidle support for Exynos5420 Rafael J. Wysocki
2014-04-23 15:42 ` Kukjin Kim [this message]
2014-05-05 8:27 ` [PATCH v3 0/5] " Chander Kashyap
2014-05-05 8:27 ` [Patch v3 1/5] driver: cpuidle-big-little: add of_device_id structure Chander Kashyap
2014-05-05 8:27 ` [Patch v3 2/5] cpuidle: config: Add ARCH_EXYNOS entry to select cpuidle-big-little driver Chander Kashyap
2014-05-05 8:59 ` Andreas Färber
2014-05-05 9:09 ` Chander Kashyap
2014-05-05 9:27 ` [PATCH v4 0/5] add cpuidle support for Exynos5420 Chander Kashyap
2014-05-05 9:27 ` [Patch v4 1/5] driver: cpuidle-big-little: add of_device_id structure Chander Kashyap
2014-05-05 9:27 ` [Patch v4 2/5] cpuidle: config: Add ARCH_EXYNOS entry to select cpuidle-big-little driver Chander Kashyap
2014-05-05 9:27 ` [Patch v4 3/5] driver: cpuidle: cpuidle-big-little: init driver for Exynos5420 Chander Kashyap
2014-05-05 9:27 ` [Patch v4 4/5] exynos: cpuidle: do not allow cpuidle registration " Chander Kashyap
2014-05-05 9:27 ` [Patch v4 5/5] mcpm: exynos: populate suspend and powered_up callbacks Chander Kashyap
2014-05-09 15:32 ` Lorenzo Pieralisi
2014-05-13 11:43 ` Chander Kashyap
2014-05-13 17:14 ` Lorenzo Pieralisi
2014-05-14 2:52 ` Chander Kashyap
2014-05-05 8:27 ` [Patch v3 3/5] driver: cpuidle: cpuidle-big-little: init driver for Exynos5420 Chander Kashyap
2014-05-05 8:27 ` [Patch v3 4/5] exynos: cpuidle: do not allow cpuidle registration " Chander Kashyap
2014-05-05 8:27 ` [Patch v3 5/5] mcpm: exynos: populate suspend and powered_up callbacks Chander Kashyap
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=5357DF53.4010806@samsung.com \
--to=kgene.kim@samsung.com \
--cc=chander.kashyap@linaro.org \
--cc=daniel.lezcano@linaro.org \
--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=rjw@rjwysocki.net \
/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