linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Vikash Garodia <quic_vgarodia@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v2 1/3] arm64: dts: qcom: sm8750: Add Iris VPU v3.5
Date: Tue, 12 Aug 2025 16:54:06 +0200	[thread overview]
Message-ID: <fb8f154b-3da4-4bee-82e1-3a1597a35c46@kernel.org> (raw)
In-Reply-To: <1292b023-e575-4270-9cbe-8943ab137eb5@kernel.org>

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

  reply	other threads:[~2025-08-12 14:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 12:38 [PATCH RFC v2 0/3] arm64: dts: qcom: sm8750: Add Iris VPU v3.5 Krzysztof Kozlowski
2025-08-06 12:38 ` [PATCH RFC v2 1/3] " Krzysztof Kozlowski
2025-08-12 14:21   ` Konrad Dybcio
2025-08-12 14:24     ` Krzysztof Kozlowski
2025-08-12 14:26       ` Konrad Dybcio
2025-08-12 14:39         ` Krzysztof Kozlowski
2025-08-12 14:45           ` Krzysztof Kozlowski
2025-08-12 14:54             ` Krzysztof Kozlowski [this message]
2025-08-12 14:39     ` Dmitry Baryshkov
2025-08-12 15:31       ` Vikash Garodia
2025-08-13 18:41         ` Dmitry Baryshkov
2025-08-14  5:19           ` Vikash Garodia
2025-08-06 12:38 ` [PATCH DO NOT MERGE RFC v2 2/3] arm64: dts: qcom: sm8750-mtp: Enable Iris codec Krzysztof Kozlowski
2025-08-09  9:42   ` Dmitry Baryshkov
2025-08-11 16:10     ` Bjorn Andersson
2025-08-06 12:38 ` [PATCH DO NOT MERGE RFC v2 3/3] arm64: dts: qcom: sm8750-qrd: " Krzysztof Kozlowski
2025-08-06 14:40 ` [PATCH RFC v2 0/3] arm64: dts: qcom: sm8750: Add Iris VPU v3.5 Rob Herring (Arm)
2025-08-11 16:15   ` Bjorn Andersson
2025-08-11 17:27     ` Neil Armstrong

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=fb8f154b-3da4-4bee-82e1-3a1597a35c46@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_vgarodia@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 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).