From: Stefan Wahren <wahrenst@gmx.net>
To: Russell King <linux@armlinux.org.uk>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Vinod Koul <vkoul@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Minas Harutyunyan <hminas@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lukas Wunner <lukas@wunner.de>,
Peter Robinson <pbrobinson@gmail.com>,
linux-arm-kernel@lists.infradead.org,
kernel-list@raspberrypi.com,
bcm-kernel-feedback-list@broadcom.com, dmaengine@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH V4 0/9] ARM: bcm2835: Implement initial S2Idle for Raspberry Pi
Date: Thu, 24 Oct 2024 22:21:57 +0200 [thread overview]
Message-ID: <66100833-88a1-454a-9061-282a91fd559b@gmx.net> (raw)
In-Reply-To: <20241024201837.79927-1-wahrenst@gmx.net>
Am 24.10.24 um 22:18 schrieb Stefan Wahren:
> This series implement the initial S2Idle support for
> the Raspberry Pi, which was a long time on my TODO list [1]. The
> changes allow to suspend and resume the Raspberry Pi via debug UART.
> The focus is on the BCM2835 SoC, because it's less complex than its
> successors and have enough documentation.
>
> Now the VC4 part has been split from the series [4], because of some issues
> in that part.
>
> Cherry-picking of patches should be fine.
>
> Test steps:
> - configure debug console (pl011 or mini UART) as wakeup source
> - send system to idle state
>
> echo freeze > /sys/power/state
>
> - wakeup system by console traffic
>
> The clock gating must be restored, because otherwise we have a
> regression on Raspberry Pi 3 B+ . Luckily the disabling of clock gating
> isn't necessary anymore. Thanks to the rest of the DWC2 patches which
> based on an idea of Doug Anderson. The USB domain is now powered down
> and the USB devices are still usable after resume. There might be room
> for improvements, but at least the system won't freeze forever as before.
>
> Here are some figures for the Raspberry Pi 1 (without any
> devices connected except of a debug UART):
>
> running but CPU idle = 1.67 W
> S2Idle = 1.33 W
>
> In comparison with HDMI & USB keyboard connected (but neither active
> nor wakeup source):
>
> running but CPU idle = 1.82 W
> S2Idle = 1.33 W
>
> The series has been successfully tested on the following platforms:
> Raspberry Pi 1 B
> Raspberry Pi 3 B+
>
> Changes in V4:
> - added Reviewed-by from Doug
> - dropped applied VC4 improvement patches
> - fix DWC2 register backup
> - add revert because of Raspberry Pi 3B+ regression
> - add suspend/resume support for DMA & eMMC to be on the safe side
Sorry, i missed the version in the other patches :-(
prev parent reply other threads:[~2024-10-24 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 20:18 [PATCH V4 0/9] ARM: bcm2835: Implement initial S2Idle for Raspberry Pi Stefan Wahren
2024-10-24 20:18 ` [PATCH 1/9] Revert "usb: dwc2: Skip clock gating on Broadcom SoCs" Stefan Wahren
2024-10-24 20:18 ` [PATCH 2/9] dmaengine: bcm2835-dma: add suspend/resume pm support Stefan Wahren
2024-10-24 20:18 ` [PATCH 3/9] mmc: bcm2835: Fix type of current clock speed Stefan Wahren
2024-10-24 20:18 ` [PATCH 4/9] mmc: bcm2835: Introduce proper clock handling Stefan Wahren
2024-10-24 20:18 ` [PATCH 5/9] mmc: bcm2835: add suspend/resume pm support Stefan Wahren
2024-10-24 20:18 ` [PATCH 6/9] usb: dwc2: gadget: Introduce register restore flags Stefan Wahren
2024-10-24 20:18 ` [PATCH 7/9] usb: dwc2: Refactor backup/restore of registers Stefan Wahren
2024-10-24 20:18 ` [PATCH 8/9] usb: dwc2: Implement recovery after PM domain off Stefan Wahren
2024-10-24 20:18 ` [PATCH 9/9] ARM: bcm2835_defconfig: Enable SUSPEND Stefan Wahren
2024-10-24 20:21 ` Stefan Wahren [this message]
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=66100833-88a1-454a-9061-282a91fd559b@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dmaengine@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lukas@wunner.de \
--cc=pbrobinson@gmail.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@kernel.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