Re: [PATCH 0/7] soc: brcmstb: add system suspend support for STB SoCs
From: Gregory Fong
Date: Thu Jun 18 2015 - 23:21:41 EST
On Thu, Jun 18, 2015 at 5:11 PM, Brian Norris
> This patch set introduces system suspend/resume support for Broadcom STB SoCs.
> There are two suspend modes (S2 and S3) as well as a related low-power shutdown
> mode (S5).
> Along with the core PM support, include a driver for the wakeup-timer, which
> allows for simple testing of suspend/resume wakeup cycles.
> Brian Norris (7):
> Documentation: dt: brcmstb: add system PM bindings
> Documentation: dt: brcmstb: add waketimer documentation
> soc: add stubs for brcmstb SoC's
> soc: brcmstb: add PM suspend/resume support (S2/S3/S5)
> soc: brcmstb: add wake-timer driver
> ARM: brcmstb: mask GIC IRQs on suspend
> ARM: dts: brcmstb: add BCM7445 system PM DT nodes
I tested this series two ways: with the device tree built into the
bootloader (BOLT) on BCM7445 and by using
With the device tree from BOLT, everything works fine. Tested the
waketimer for S2, S3, and S5.
With the device tree in arch/arm/boot/dts/bcm7445-bcm97445svmb.dts, S2
works, but S3 and S5 do not. It comes back up but doesn't reach the
[ 6.050808] PM: suspend of devices complete after 1.425 msecs
[ 6.051760] PM: late suspend of devices complete after 0.947 msecs
[ 6.052535] PM: noirq suspend of devices complete after 0.770 msecs
[ 6.052537] Disabling non-boot CPUs ...
[ 6.053005] CPU1: shutdown
[ 6.065914] CPU2: shutdown
[ 6.080756] CPU3: shutdown
[ 6.095214] Enabling non-boot CPUs ...
[ 6.111496] CPU1 is up
[ 6.126934] CPU2 is up
[ 6.142511] CPU3 is up
[ 6.145308] PM: noirq resume of devices complete after 2.772 msecs
[ 6.148022] PM: early resume of devices complete after 2.626 msecs
[ 6.151017] PM: resume of devices complete after 2.976 msecs
[ 6.212771] Restarting tasks ... done.
[[[ output stops here ]]]
I suspect there might be an issue somewhere in
[PATCH 7/7] ARM: dts: brcmstb: add BCM7445 system PM DT nodes.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/