From: Stefan Wahren <wahrenst@gmx.net>
To: "Maíra Canal" <mcanal@igalia.com>,
"Ulf Hansson" <ulfh@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>
Cc: linux-pm@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kernel-dev@igalia.com
Subject: Re: [PATCH] pmdomain: bcm: bcm2835-power: Raise ASB poll timeout to 100us
Date: Sun, 31 May 2026 12:41:07 +0200 [thread overview]
Message-ID: <deecc409-02c1-4393-bc06-1852fc06e4d1@gmx.net> (raw)
In-Reply-To: <20260530204636.1115120-1-mcanal@igalia.com>
Hi Maíra,
Am 30.05.26 um 22:46 schrieb Maíra Canal:
> Commit 18605b1b936b ("pmdomain: bcm: bcm2835-power: Increase ASB control
> timeout") raised the ASB handshake polling budget from 1us to 5us.
> Surveying the pmdomain subsystem, 5us is still one of the smallest polling
> budgets by a wide margin. Comparable handshakes in other drivers use:
>
> - 100us : starfive jh71xx-pmu, apple pmgr-pwrstate
> - 1ms : renesas rcar-sysc, rmobile-sysc (power-on)
> - 10ms : renesas rcar-gen4-sysc, sunxi sun55i-pck600
> - 1s : mediatek mtk-pm-domains, mtk-scpsys
>
> Raise the BCM2835 timeout to 100us, matching analogous drivers. 100us is
> still negligible relative to a power-domain transition and gives the V3D
> master ASB substantially more headroom to drain under heavy workloads,
> assuring us that the timeout is enough for any scenario.
tbh I'm not convinced by this explanation. Starting with a timeout
comparison across different pmdomain driver looks strange to me.
My expectation that the reason for such a patch is that there is some
kind of scenario to trigger unexpected timeouts.
If this is the case, please provide more information about the scenario
(specific platform, scenario, link to the bug report).
I'm not against the change in general, but please start your commit
message with the problem and not with the solution.
A related question, does it make sense to add an error message here for
the timeout case just like in the rest of the driver?
Best regards
>
> Signed-off-by: Maíra Canal <mcanal@igalia.com>
> ---
> drivers/pmdomain/bcm/bcm2835-power.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pmdomain/bcm/bcm2835-power.c b/drivers/pmdomain/bcm/bcm2835-power.c
> index b76d74e3849b..d507bb675e29 100644
> --- a/drivers/pmdomain/bcm/bcm2835-power.c
> +++ b/drivers/pmdomain/bcm/bcm2835-power.c
> @@ -175,7 +175,7 @@ static int bcm2835_asb_control(struct bcm2835_power *power, u32 reg, bool enable
> writel(PM_PASSWORD | val, base + reg);
>
> if (readl_poll_timeout_atomic(base + reg, val,
> - !!(val & ASB_ACK) != enable, 0, 5))
> + !!(val & ASB_ACK) != enable, 0, 100))
> return -ETIMEDOUT;
>
> return 0;
next prev parent reply other threads:[~2026-05-31 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 20:46 [PATCH] pmdomain: bcm: bcm2835-power: Raise ASB poll timeout to 100us Maíra Canal
2026-05-31 10:41 ` Stefan Wahren [this message]
2026-05-31 12:18 ` Maíra Canal
2026-06-19 13:57 ` Maíra Canal
2026-06-21 20:13 ` Florian Fainelli
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=deecc409-02c1-4393-bc06-1852fc06e4d1@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=kernel-dev@igalia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mcanal@igalia.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=ulfh@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