From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: tegra30: fix power up sequence for boot_secondary
Date: Thu, 20 Dec 2012 09:55:38 -0700 [thread overview]
Message-ID: <50D3430A.4020901@wwwdotorg.org> (raw)
In-Reply-To: <1355970603-28531-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 12/19/2012 07:30 PM, Joseph Lo wrote:
> The power up sequence is different on the cold boot CPU and the CPU
> that resumed from the hotplug. For the cold boot CPU, it was been power
> gated as default. To power up the cold boot CPU, the power should be
> un-gated by un toggling the power gate register manually.
>
> For the CPU that resumed from the hotplug, after un-halted the CPU. The
> flow controller will un-gate the power of the CPU. No need to manually
> control, just wait the power be resumed and continue the power up
> sequence after the CPU power is ready.
I'd like Peter to review this too (CC'd). I guess it looks OK...
> diff --git a/arch/arm/mach-tegra/platsmp.c b/arch/arm/mach-tegra/platsmp.c
> @@ -72,7 +75,27 @@ static int tegra30_power_up_cpu(unsigned int cpu)
> if (pwrgateid < 0)
> return pwrgateid;
>
> - /* If this is the first boot, toggle powergates directly. */
> + /*
> + * If the CPU had booted and went through here after CPU
> + * had been already un-gated by flow controller. Wait
> + * for confirmation that the CPU is powered then remove
> + * the IO clamps. On the cold boot entry, do not wait.
> + */
That comment is quite unclear. In particular the first sentence says "if
something" rather than "if something then something". Can you please
re-write it?
Also, it'd be good to explain (or at least briefly reference) the boot
path for a cold-boot CPU and a warm boot CPU; I assume that somehow a
cold boot CPU doesn't execute tegra_secondary_init(), but a warm boot
CPU does?
> + if (cpumask_test_cpu(cpu, &tegra_cpu_init_mask)) {
> + timeout = jiffies + 5;
Are the units/frequency of the jiffies variable always constant? Should
"5" be not a constant, but instead a calculation involving HZ or
msecs_to_jiffies()? Certainly, the few other uses of time_before() I
looked at use HZ or msecs_to_jiffies().
next prev parent reply other threads:[~2012-12-20 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 2:30 [PATCH] ARM: tegra30: fix power up sequence for boot_secondary Joseph Lo
[not found] ` <1355970603-28531-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-20 16:55 ` Stephen Warren [this message]
[not found] ` <50D3430A.4020901-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-21 8:07 ` Joseph Lo
[not found] ` <1356077271.26029.81.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2012-12-21 21:12 ` Stephen Warren
2013-01-02 12:15 ` Peter De Schrijver
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=50D3430A.4020901@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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).