From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: ux500:mach-ux500/cpuidle.c spinlock dis-matching
Date: Sun, 06 Jan 2013 17:23:26 +0100 [thread overview]
Message-ID: <50E9A4FE.6090807@linaro.org> (raw)
In-Reply-To: <CAKvkGKdoWxmnRbNvn_SikRhzsyyzqEC99XtSM9ZeaVGjEA_Ydw@mail.gmail.com>
On 12/28/2012 08:06 AM, steve.zhan wrote:
> Hi Daniel,
Hi Steve,
sorry I missed your email.
>
> I think we must unlock the master spinlock even
> prcmu_gic_decouple function now always return 0.
> Could you give some infos about this?
I agree, that would be cleaner.
AFAICS, your patch does not solve the problem because 'recouple' will be
false if prcmu_gic_decouple fails, so the lock will never be release.
That will be simpler to do:
if (prcmu_gic_decouple()) {
spin_unlock(&master);
goto out;
}
no ?
> Thanks.
>
> diff --git a/arch/arm/mach-ux500/cpuidle.c b/arch/arm/mach-ux500/cpuidle.c
> index b54884bd..b0759ce 100644
> --- a/arch/arm/mach-ux500/cpuidle.c
> +++ b/arch/arm/mach-ux500/cpuidle.c
> @@ -29,6 +29,7 @@ static inline int ux500_enter_idle(struct cpuidle_device *dev,
> {
> int this_cpu = smp_processor_id();
> bool recouple = false;
> + bool locked = false;
>
> clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_ENTER, &this_cpu);
>
> @@ -39,6 +40,8 @@ static inline int ux500_enter_idle(struct cpuidle_device *dev,
> if (!spin_trylock(&master_lock))
> goto wfi;
>
> + locked = true;
> +
> /* decouple the gic from the A9 cores */
> if (prcmu_gic_decouple())
> goto out;
> @@ -76,7 +79,7 @@ static inline int ux500_enter_idle(struct cpuidle_device *dev,
> /* When we switch to retention, the prcmu is in charge
> * of recoupling the gic automatically */
> recouple = false;
> -
> + locked = false;
> spin_unlock(&master_lock);
> }
> wfi:
> @@ -86,7 +89,8 @@ out:
>
> if (recouple) {
> prcmu_gic_recouple();
> - spin_unlock(&master_lock);
> + if (locked)
> + spin_unlock(&master_lock);
> }
>
> clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_EXIT, &this_cpu);
>
>
>
> Steve Zhan
>
--
<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
next prev parent reply other threads:[~2013-01-06 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 7:06 [PATCH 1/1] ARM: ux500:mach-ux500/cpuidle.c spinlock dis-matching steve.zhan
2012-12-28 7:13 ` steve.zhan
2013-01-04 2:46 ` steve.zhan
2013-01-06 16:23 ` Daniel Lezcano [this message]
2013-01-07 5:50 ` steve.zhan
2013-01-07 8:54 ` Daniel Lezcano
2013-01-07 10:58 ` steve.zhan
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=50E9A4FE.6090807@linaro.org \
--to=daniel.lezcano@linaro.org \
--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).