From: "Heiko Stübner" <heiko@sntech.de>
To: linux-kernel@vger.kernel.org,
Detlev Casanova <detlev.casanova@collabora.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>,
Finley Xiao <finley.xiao@rock-chips.com>,
Jagan Teki <jagan@edgeble.ai>, Arnd Bergmann <arnd@arndb.de>,
Elaine Zhang <zhangqing@rock-chips.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-pm@vger.kernel.org,
kernel@collabora.com
Subject: Re: [PATCH v2 2/2] pmdomain: rockchip: Add support for rk3576 SoC
Date: Thu, 08 Aug 2024 19:59:59 +0200 [thread overview]
Message-ID: <2449940.aKNjEaI27c@diego> (raw)
In-Reply-To: <5805279.DvuYhMxLoT@trenzalore>
Hi Detlev,
Am Donnerstag, 8. August 2024, 19:53:20 CEST schrieb Detlev Casanova:
> On Thursday, 8 August 2024 12:41:05 EDT Heiko Stübner wrote:
> > > @@ -552,7 +575,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);
> >
> > I still want this behaviour change in a separate patch with adequate
> > commit message please.
> >
> > Going from always handling qos to allowing to just wait a specific time
> > needs explanation and is not part of "just" adding rk3576 support.
>
> You are right, I didn't takle this issue.
> This is actually a bug, the else is not supposed to be there, it should only
> be an added delay for some PDs.
>
> Unfortunately, I'm not sure why that delay is needed exactly, so I'm willing
> to remove it for now (only used by nputop and vop, both unsupported) and come
> back to it if needed when VOP/NPU support is added.
>
> Would that work for this upstream ?
that would work. The whole delay thing is not part of the dt-binding
which would be more critical to get right in the first round.
So as long as your "add rk3576 support" patch really only adds the
rk3576-specific data, but does not change how the shared code
behaves, we should be fine and can find out about that delay later.
Heiko
next prev parent reply other threads:[~2024-08-08 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240808163451.80750-1-detlev.casanova@collabora.com>
[not found] ` <20240808163451.80750-3-detlev.casanova@collabora.com>
2024-08-08 16:41 ` [PATCH v2 2/2] pmdomain: rockchip: Add support for rk3576 SoC Heiko Stübner
[not found] ` <5805279.DvuYhMxLoT@trenzalore>
2024-08-08 17:59 ` Heiko Stübner [this message]
[not found] ` <20240808163451.80750-2-detlev.casanova@collabora.com>
2024-08-09 14:59 ` [PATCH v2 1/2] dt-bindings: power: Add support for RK3576 SoC Conor Dooley
[not found] ` <2276665.iZASKD2KPV@trenzalore>
2024-08-12 16:19 ` Conor Dooley
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=2449940.aKNjEaI27c@diego \
--to=heiko@sntech.de \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=jagan@edgeble.ai \
--cc=kernel@collabora.com \
--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=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).