[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb8f154b-3da4-4bee-82e1-3a1597a35c46@kernel.org>
Date: Tue, 12 Aug 2025 16:54:06 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Vikash Garodia <quic_vgarodia@...cinc.com>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC v2 1/3] arm64: dts: qcom: sm8750: Add Iris VPU v3.5
On 12/08/2025 16:45, Krzysztof Kozlowski wrote:
>>> Weird, there's an entry in the frequency table for it (well, * 3 the
>>> rate) and it comes out of the same PLL as other ones.. what sort of
>>
>> You mean freq_tbl in P_VIDEO_CC_PLL0_OUT_MAIN? Yeah, I also saw that.
>>
>>> opp failures do you see?
>>
>> Only:
>>
>> [ 9.306006] qcom-iris aa00000.video-codec: dev_pm_opp_set_rate:
>> failed to find OPP for freq 630000000 (-34)
>> [ 9.316078] qcom-iris aa00000.video-codec: power on failed
>> [ 9.322001] qcom-iris aa00000.video-codec: core init failed
>
> But I misunderstood you - I thought you want to replace 630, to match
> downstream driver. If just added, then it's fine.
... and to confirm: it works and I double checked it now with frequency
plans, so I will add missing 570.
Best regards,
Krzysztof
Powered by blists - more mailing lists