From: "Heiko Stübner" <heiko@sntech.de>
To: linux-kernel@vger.kernel.org,
Detlev Casanova <detlev.casanova@collabora.com>,
Elaine Zhang <zhangqing@rock-chips.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Detlev Casanova <detlev.casanova@collabora.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Finley Xiao <finley.xiao@rock-chips.com>,
Jagan Teki <jagan@edgeble.ai>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/3] soc: rockchip: power-domain: Add power domain support for rk3576
Date: Mon, 05 Aug 2024 11:36:40 +0200 [thread overview]
Message-ID: <12859392.hYdu0Ggh8K@diego> (raw)
In-Reply-To: <20240802151647.294307-4-detlev.casanova@collabora.com>
Hi Detlev,
Am Freitag, 2. August 2024, 17:15:00 CEST schrieb Detlev Casanova:
> From: Finley Xiao <finley.xiao@rock-chips.com>
with the power-domains now living somewhere else, the patch will need
a different subject I think.
>
> This driver is modified to support RK3576 SoCs and lists the power domains.
>
> Signed-off-by: Finley Xiao <finley.xiao@rock-chips.com>
> Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> @@ -552,7 +574,10 @@ static int rockchip_pd_power(struct rockchip_pm_domain *pd, bool power_on)
> /* if powering up, leave idle mode */
> rockchip_pmu_set_idle_request(pd, false);
>
> - rockchip_pmu_restore_qos(pd);
> + if (pd->info->delay_us)
> + udelay(pd->info->delay_us);
> + else
> + rockchip_pmu_restore_qos(pd);
the whole delay thing needs its own patch please. I.e. you're changing
the inner workings of the driver here by not handling the qos settings
and just waiting for a specific time.
So I expect a lot more explanation on why that is the case and needed
instead of it just happening when adding the soc-specific pieces.
Does the rk3576 not have those qos settings and if so, why is there a delay
necessary.
This is not meant to disallow it, just that it needs its own commit with its
own descriptive commit message :-)
Heiko
prev parent reply other threads:[~2024-08-05 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 15:14 [PATCH 0/3] Add power-controller support for rk3576 Detlev Casanova
2024-08-02 15:14 ` [PATCH 1/3] dt-bindings: pinctrl: Add rk3576 power-controller bindings Detlev Casanova
2024-08-02 15:14 ` [PATCH 2/3] dt-bindings: Add power-domain header for RK3576 SoCs Detlev Casanova
2024-08-04 9:56 ` Krzysztof Kozlowski
2024-08-06 16:34 ` Detlev Casanova
2024-08-08 7:54 ` Heiko Stübner
2024-08-08 16:43 ` Dragan Simic
2024-08-08 16:46 ` Heiko Stübner
2024-08-02 15:15 ` [PATCH 3/3] soc: rockchip: power-domain: Add power domain support for rk3576 Detlev Casanova
2024-08-05 1:22 ` zhangqing
2024-08-05 9:36 ` Heiko Stübner [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=12859392.hYdu0Ggh8K@diego \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=geert+renesas@glider.be \
--cc=jagan@edgeble.ai \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=zhangqing@rock-chips.com \
/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).