From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: vfp: Always save VFP state in vfp_pm_suspend
Date: Tue, 21 Jun 2011 13:11:34 +0800 [thread overview]
Message-ID: <BANLkTimBuz5YLto3qWsR_pL1cDh9cwSbAA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikPd5AVJa-n1V1eyqh-HBACOi-ggQ@mail.gmail.com>
this patch has been reviewed by Catalin Marinas for a long time. but
why isn't there any feedback by now?
it actually is a very useful fix to vfp PM.
2011/5/19 Barry Song <21cnbao@gmail.com>:
> Any update for this?
>
> 2011/5/10 Barry Song <21cnbao@gmail.com>:
>> From: Colin Cross <ccross@android.com>
>>
>> vfp_pm_suspend should save the VFP state any time there is
>> a last_VFP_context. ?If it only saves when the VFP is enabled,
>> the state can get lost when, on a UP system:
>> ? Thread 1 uses the VFP
>> ? Context switch occurs to thread 2, VFP is disabled but the
>> ? ? ?VFP context is not saved to allow lazy save and restore
>> ? Thread 2 initiates suspend
>> ? vfp_pm_suspend is called with the VFP disabled, but the
>> ? ? ?context has not been saved.
>>
>> Modify vfp_pm_suspend to save the VFP context whenever
>> last_VFP_context is set.
>>
>> Signed-off-by: Colin Cross <ccross@android.com>
>> Cc: Binghua Duan <binghua.duan@csr.com>
>> Signed-off-by: Rongjun Ying <rongjun.ying@csr.com>
>> Signed-off-by: Barry Song <21cnbao@gmail.com>
>> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>> ---
>> ?arch/arm/vfp/vfpmodule.c | ? ?4 ++++
>> ?1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/vfp/vfpmodule.c b/arch/arm/vfp/vfpmodule.c
>> index f746950..e6fe6ae 100644
>> --- a/arch/arm/vfp/vfpmodule.c
>> +++ b/arch/arm/vfp/vfpmodule.c
>> @@ -412,6 +412,10 @@ static int vfp_pm_suspend(struct sys_device *dev, pm_message_t state)
>>
>> ? ? ? ? ? ? ? ?/* disable, just in case */
>> ? ? ? ? ? ? ? ?fmxr(FPEXC, fmrx(FPEXC) & ~FPEXC_EN);
>> + ? ? ? } else if (last_VFP_context[ti->cpu]) {
>> + ? ? ? ? ? ? ? fmxr(FPEXC, fpexc | FPEXC_EN);
>> + ? ? ? ? ? ? ? vfp_save_state(last_VFP_context[ti->cpu], fpexc);
>> + ? ? ? ? ? ? ? fmxr(FPEXC, fpexc);
>> ? ? ? ?}
>>
>> ? ? ? ?/* clear any information we had about last context state */
>> --
>> 1.6.0.4
prev parent reply other threads:[~2011-06-21 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 21:16 [PATCH v4] ARM: vfp: Always save VFP state in vfp_pm_suspend Barry Song
2011-05-19 1:40 ` Barry Song
2011-06-21 5:11 ` Barry Song [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=BANLkTimBuz5YLto3qWsR_pL1cDh9cwSbAA@mail.gmail.com \
--to=21cnbao@gmail.com \
--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).