From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dikshita Agarwal <quic_dikshita@quicinc.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] media: iris: Add support for SM8750 (VPU v3.5)
Date: Thu, 17 Jul 2025 14:34:27 +0200 [thread overview]
Message-ID: <cd51f5ee-8f2c-486f-9ab1-526088b17127@linaro.org> (raw)
In-Reply-To: <fedee429-fad8-ab4c-7e8a-91ac13232501@quicinc.com>
On 17/07/2025 14:22, Dikshita Agarwal wrote:
>
>
> On 7/17/2025 4:24 PM, Krzysztof Kozlowski wrote:
>> On 17/07/2025 12:50, Dikshita Agarwal wrote:
>>>>>>>> + for (i = 0; i < core->iris_platform_data->num_vpp_pipe; i++) {
>>>>>>>> + ret = readl_poll_timeout(core->reg_base + VCODEC_SS_IDLE_STATUSN + 4 * i,
>>>>>>>> + val, val & 0x400000, 2000, 20000);
>>>>>>>> + if (ret)
>>>>>>>> + goto disable_power;
>>>>>>>> + }
>>>>>>>> +
>>>>>>>> + ret = readl_poll_timeout(core->reg_base + AON_WRAPPER_MVP_NOC_LPI_STATUS,
>>>>>>>> + val, val & BIT(0), 200, 2000);
>>>>>>> what are you polling here for?
>>>>>>
>>>>>>
>>>>>> This is not different than existing code. I don't understand why you are
>>>>>> commenting on something which is already there.
>>>>>
>>>>> Which code are you referring to?
>>>>
>>>> To the existing vpu33 which had Reviewed-by: Vikash Garodia
>>>> <quic_vgarodia@quicinc.com>
>>>>
>>>> You understand that everything here is the same, everything is a copy
>>>> while adding just few more things?
>>>>
>>>> My patch is not doing in this respect anything different that what you
>>>> reviewed.
>>>>
>>>
>>> It seems to have been missed in vpu33 power off sequence as well and should
>>> be fixed.
>>>
>>> Still, as mentioned earlier as well, your reference should be
>>> HPG/downstream driver of SM8750 not the previous generation (SM8650).
>>
>> Yes and partially no, because we write upstream code matching or
>> extending existing upstream driver. As you said earlier, downstream is
>> not the truth always:
>
> You're writing the power sequence for a new generation, so referencing the
> previous generation is totally wrong. Power sequences can vary between
No. I am extending existing source code in hopefully compatible or
matching style.
We do not follow here downstream approaches of reimplementing everything
from scratch on every new generation.
> generations — that's precisely why HPG exists.
>
> I've already pointed this out multiple times, but let me reiterate one last
> time:
> The current power sequence code is incomplete.
> Copying the SM8650 code to SM8750 is not appropriate — it's the wrong
> reference.
You only pointed out missing AON_WRAPPER_MVP_NOC_LPI_CONTROL, so
"multiple times" is not accurate.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-17 12:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 13:41 [PATCH 0/3] media: iris: Add support for SM8750 (VPU v3.5) Krzysztof Kozlowski
2025-07-14 13:41 ` [PATCH 1/3] media: dt-bindings: qcom,sm8550-iris: Add SM8750 video codec Krzysztof Kozlowski
2025-07-15 3:47 ` Rob Herring
2025-07-14 13:41 ` [PATCH 2/3] media: iris: Split power on per variants Krzysztof Kozlowski
2025-07-14 13:41 ` [PATCH 3/3] media: iris: Add support for SM8750 (VPU v3.5) Krzysztof Kozlowski
2025-07-16 9:10 ` Dikshita Agarwal
2025-07-16 9:28 ` Krzysztof Kozlowski
2025-07-17 7:37 ` Dikshita Agarwal
2025-07-17 9:34 ` Krzysztof Kozlowski
2025-07-17 10:50 ` Dikshita Agarwal
2025-07-17 10:54 ` Krzysztof Kozlowski
2025-07-17 12:02 ` Vikash Garodia
2025-07-17 12:38 ` Krzysztof Kozlowski
2025-07-17 12:22 ` Dikshita Agarwal
2025-07-17 12:34 ` Krzysztof Kozlowski [this message]
2025-07-17 9:49 ` Krzysztof Kozlowski
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=cd51f5ee-8f2c-486f-9ab1-526088b17127@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abhinav.kumar@linux.dev \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_dikshita@quicinc.com \
--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).