From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64
Date: Mon, 23 Jun 2025 14:00:20 +0200 [thread overview]
Message-ID: <aFlB1Ae6ZRPX_TM5@linaro.org> (raw)
In-Reply-To: <4b3cd0a9-ef63-4adc-b2c2-52fde30fed83@oss.qualcomm.com>
On Wed, Jun 11, 2025 at 10:46:17PM +0200, Konrad Dybcio wrote:
> On 6/11/25 10:43 PM, Konrad Dybcio wrote:
> > On 6/2/25 10:09 AM, Stephan Gerhold wrote:
> >> On Sat, May 31, 2025 at 02:27:18PM +0200, Konrad Dybcio wrote:
> >>> Sparked by <20250530-add-venus-for-qcs615-v8-0-c0092ac616d0@quicinc.com>
> >>>
> >>> No external dependencies
> >>>
> >>
> >> Are you sure?
> >>
> >>> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> >>> ---
> >>> Konrad Dybcio (5):
> >>> arm64: dts: qcom: msm8916: Add Venus OPP table
> >>> arm64: dts: qcom: msm8996: Add Venus OPP table
> >>> arm64: dts: qcom: msm8998: Add Venus OPP table
> >>> arm64: dts: qcom: sdm630: Add Venus OPP table
> >>
> >> None of these platforms has a power domain that supports performance
> >> states specified in the venus node of the DT, and the venus GDSC does
> >> not have any parent either. I think you will need to update the venus
> >> bindings and add
> >>
> >> .opp_pmdomain = (const char *[]) { "cx" /*???*/ },
> >>
> >> for all these in the venus driver (plus backwards compat if not already
> >> there). And then add that power domain additionally in the DT.
> >
> > Making use of these tables would certainly be welcome.. This patchset
> > was aimed at pushing them to fdt, so that we can debate dropping the
> > hardcoded values in the driver in the future.
>
> I don't think we can just plug them in to the driver right now, as
> it would also happen to break backwards compat (since
> devm_pm_domain_attach_list() seems to not be particularly happy about
> missing resources) - though arguments can be made both ways: "it
> could have never *really* worked" vs "don't poke at the old driver for
> old hardware too much, as it's gonna break"
>
You could just make it ignore the returned error for the call to
ret = devm_pm_domain_attach_list(dev, &opp_pd_data, &core->opp_pmdomain);
? Perhaps with some extra flag that only enables that for the older
platforms.
I suppose having the DT complete is also helpful, even without the
driver changes. But at the end this would be untested "dead" properties
that may turn out being subtly wrong when someone tries to actually
enable it. So having it properly enabled and tested would be good,
especially since the required changes don't sound too massive and
intrusive to me.
Thanks,
Stephan
next prev parent reply other threads:[~2025-06-23 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 12:27 [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64 Konrad Dybcio
2025-05-31 12:27 ` [PATCH 1/5] arm64: dts: qcom: msm8916: Add Venus OPP table Konrad Dybcio
2025-06-01 7:43 ` Dmitry Baryshkov
2025-05-31 12:27 ` [PATCH 2/5] arm64: dts: qcom: msm8996: " Konrad Dybcio
2025-06-01 7:43 ` Dmitry Baryshkov
2025-05-31 12:27 ` [PATCH 3/5] arm64: dts: qcom: msm8998: " Konrad Dybcio
2025-06-01 7:45 ` Dmitry Baryshkov
2025-05-31 12:27 ` [PATCH 4/5] arm64: dts: qcom: sdm630: " Konrad Dybcio
2025-06-01 7:40 ` Dmitry Baryshkov
2025-05-31 12:27 ` [PATCH 5/5] arm64: dts: qcom: sdm845: Fix Venus OPP entries Konrad Dybcio
2025-06-01 7:38 ` Dmitry Baryshkov
2025-06-02 8:09 ` [PATCH 0/5] Add missing OPP tables for Venus on qcom/arm64 Stephan Gerhold
2025-06-11 20:43 ` Konrad Dybcio
2025-06-11 20:46 ` Konrad Dybcio
2025-06-23 12:00 ` Stephan Gerhold [this message]
2025-06-02 12:26 ` Rob Herring (Arm)
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=aFlB1Ae6ZRPX_TM5@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_rjendra@quicinc.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.