From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: linux@maxim.org.za, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org, patches@linaro.org,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
thomas.petazzoni@free-electrons.com, b.zolnierkie@samsung.com
Subject: Re: [PATCH V2 1/2] ARM: at91: cpuidle: convert to platform driver
Date: Tue, 15 Oct 2013 08:16:31 +0200 [thread overview]
Message-ID: <525CDDBF.3060500@linaro.org> (raw)
In-Reply-To: <20131014232539.GM11420@ns203013.ovh.net>
On 10/15/2013 01:25 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 22:15 Mon 14 Oct , Daniel Lezcano wrote:
>> Using the platform driver model is a good way to separate the cpuidle specific
>> code from the low level pm code. It allows to remove the dependency between
>> these two components.
>>
>> The platform_device is located in the pm code and a 'set' function has been
>> added to set the standby function from the AT91_SOC_START initialization
>> function. Each SoC with a cpuidle driver will set the standby function in the
>> platform_data field at init time. Then pm code will register the cpuidle
>> platform device.
>>
>> The cpuidle driver will register the platform_driver and use the device's
>> platform_data as a standby callback in the idle path.
>
> I've an issue while re-reading the pm code
>
> we use the xx_standby for 2 drivers cpuidle and suspend/resume
>
> with all the cpu_is_xxxx
>
> so you need to do one more step in this series
> by cleaning up the PM_SUSPEND_STANDBY to as you put a function pointer with
> the correct one in pm.c
I was plannning to send it as a separate patch.
> otherwise looks good
Cool. Thanks for the review.
-- Daniel
[ ... ]
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2013-10-15 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 20:15 [PATCH V2 1/2] ARM: at91: cpuidle: convert to platform driver Daniel Lezcano
2013-10-14 20:15 ` [PATCH V2 2/2] ARM: at91: cpuidle: Move driver to drivers/cpuidle Daniel Lezcano
2013-10-14 23:25 ` [PATCH V2 1/2] ARM: at91: cpuidle: convert to platform driver Jean-Christophe PLAGNIOL-VILLARD
2013-10-15 6:16 ` Daniel Lezcano [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=525CDDBF.3060500@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=patches@linaro.org \
--cc=plagnioj@jcrosoft.com \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).