From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Shutdown problem in SMP system happened on Tegra20
Date: Fri, 24 Aug 2012 19:21:33 +0100 [thread overview]
Message-ID: <20120824182133.GB18957@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <A7051F87A141B744BCAF487D48E5B3BDF5BA982848@HKMAIL02.nvidia.com>
On Fri, Aug 24, 2012 at 04:23:39PM +0800, Bill Huang wrote:
> When doing shutdown on Tegra20/Tegra30, we need to read/write PMIC
> registers through I2C to perform the power off sequence. Unfortunately,
> sometimes we'll fail to shutdown due to I2C timeout on Tegra20. And the
> cause of the timeout is due to the CPU which I2C controller IRQ affined
> to will have chance to be offlined without migrating all irqs affined
> to it, so the following I2C transactions will fail (no any CPU will
> handle that interrupt since then).
> Some snippet of the shutdown codes:
>
> void kernel_power_off(void)
> {
> kernel_shutdown_prepare(SYSTEM_POWER_OFF);
> :
> disable_nonboot_cpus();
> :
> machine_power_off();
> }
>
> void machine_power_off(void)
> {
> machine_shutdown();
> if (pm_power_off)
> pm_power_off(); /* this is where we send I2C write to shutdown */
> }
>
> void machine_shutdown(void)
> {
> #ifdef CONFIG_SMP
> smp_send_stop();
> #endif
> }
>
> In "smp_send_stop()", it will send "IPI_CPU_STOPS" to offline other cpus except
> current cpu (smp_processor_id()), however, current cpu will not always be cpu0 at
> least at Tegra20, that said for example cpu1 might be the current cpu and cpu0 will
> be offlined and this is the case why the I2C transaction will timeout.
>
> For normal case, "disable_nonboot_cpus()" call will disable all other Cpus except
> cpu0, that means we won't hit the problem mentioned here since cpu0 will always be
> the current cpu in the call "smp_send_stop", but the call to "disable_nonboot_cpus"
> will happen only when "CONFIG_PM_SLEEP_SMP" is enabled which is not the case for
> Tegra20/Tegra30, we don't support suspend yet so this can't be enabled.
So what you're asking for is a feature to do what CONFIG_PM_SLEEP_SMP
does, but without CONFIG_PM_SLEEP_SMP enabled?
Why not just ensure that CONFIG_PM_SLEEP_SMP is enabled if your platform
requires that the lowest CPU number be the CPU dealing with reboot?
next prev parent reply other threads:[~2012-08-24 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 8:23 Shutdown problem in SMP system happened on Tegra20 Bill Huang
2012-08-24 15:19 ` Stephen Warren
2012-08-24 18:21 ` Russell King - ARM Linux [this message]
2012-08-25 0:00 ` Bill Huang
2012-08-25 7:17 ` Russell King - ARM Linux
2012-08-27 5:43 ` Bill Huang
2012-08-25 7:36 ` Shawn Guo
2012-08-25 7:52 ` Russell King - ARM Linux
2012-08-25 10:33 ` Shawn Guo
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=20120824182133.GB18957@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).