From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: zynq: wfi exit on same cpu is valid
Date: Tue, 04 Jun 2013 13:58:31 +0200 [thread overview]
Message-ID: <51ADD667.3010203@linaro.org> (raw)
In-Reply-To: <CAP245DUsRcomDaNKbxYry39ZLCrR33SDRRAhNCdR91e17sHF-A@mail.gmail.com>
On 06/04/2013 01:39 PM, Amit Kucheria wrote:
> On Mon, Jun 3, 2013 at 6:13 PM, Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>> On 06/03/2013 11:51 AM, Michal Simek wrote:
>>> Hi,
>>>
>>> On 06/03/2013 10:14 AM, Daniel Lezcano wrote:
>>>> On 05/31/2013 12:44 PM, Sanjay Singh Rawat wrote:
>>>>> The current code considers every wakeup as spurious, which is not
>>>>> correct. Handle the same way as other arm platforms are doing.
>>>>>
>>>>> Signed-off-by: Sanjay Singh Rawat <sanjay.rawat@linaro.org>
>>>> Reviewed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>>>
>>>>
>>>>> ---
>>>>> arch/arm/mach-zynq/hotplug.c | 7 +++++++
>>>>> 1 file changed, 7 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm/mach-zynq/hotplug.c b/arch/arm/mach-zynq/hotplug.c
>>>>> index c89672b..a1ab22c 100644
>>>>> --- a/arch/arm/mach-zynq/hotplug.c
>>>>> +++ b/arch/arm/mach-zynq/hotplug.c
>>>>> @@ -67,6 +67,13 @@ static inline void zynq_platform_do_lowpower(unsigned int cpu, int *spurious)
>>>>> dsb();
>>>>> wfi();
>>>>>
>>>>> + if (pen_release == cpu_logical_map(cpu)) {
>>>>> + /*
>>>>> + * OK, proper wakeup, we're done
>>>>> + */
>>>>> + break;
>>>>> + }
>>>>> +
>>> what pen_release stands for?
>>> I have looked at it and others platform are also using it in platsmp
>>> code which is not zynq case.
>>> How is it supposed to work and how this variable should be used?
>>
>> This variable is used to serialize the secondary cpus boot process.
>
> I'm curious why it is called pen_release. :) Is there some historical
> link to some HW lines?
I tried to figure out the same but I did not found any information on
that. I assumed the name could be referring to a simplified mutual
exclusion algorithm from the 'Dining philosophers problem' [1] where the
fork is a pen.
But maybe I am totally wrong :)
[1] http://en.wikipedia.org/wiki/Dining_philosophers_problem
--
<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-06-04 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 10:44 [PATCH] ARM: zynq: wfi exit on same cpu is valid Sanjay Singh Rawat
2013-06-03 8:14 ` Daniel Lezcano
2013-06-03 9:51 ` Michal Simek
2013-06-03 12:43 ` Daniel Lezcano
2013-06-04 7:29 ` Michal Simek
2013-06-04 12:40 ` Daniel Lezcano
2013-06-04 13:09 ` Michal Simek
2013-06-04 13:25 ` Daniel Lezcano
2013-06-04 11:39 ` Amit Kucheria
2013-06-04 11:58 ` Daniel Lezcano [this message]
2013-06-04 14:10 ` Russell King - ARM Linux
2013-06-04 14:17 ` Russell King - ARM Linux
2013-06-05 9:34 ` Daniel Lezcano
2013-06-05 10:47 ` Michal Simek
2013-06-05 11:29 ` Russell King - ARM Linux
2013-06-05 12:54 ` Michal Simek
[not found] ` <OFF951DD26.F13B5CB1-ON48257B81.003EE068-48257B81.003F07FB@spreadtrum.com>
2013-06-05 12:07 ` Michal Simek
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=51ADD667.3010203@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).