From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: qcom: sa8775p: add support for video node
Date: Tue, 18 Mar 2025 15:33:21 +0100 [thread overview]
Message-ID: <9940290b-6b97-4339-848d-ea95a365f74c@oss.qualcomm.com> (raw)
In-Reply-To: <8f7c1c08-6776-968c-530e-b640ded940b3@quicinc.com>
On 3/18/25 3:24 PM, Vikash Garodia wrote:
>
> On 3/15/2025 7:13 PM, Konrad Dybcio wrote:
>> On 3/11/25 1:03 PM, Vikash Garodia wrote:
>>> Video node enables video on Qualcomm SA8775P platform.
>>>
>>> Signed-off-by: Vikash Garodia <quic_vgarodia@quicinc.com>
>>> ---
>>> arch/arm64/boot/dts/qcom/sa8775p.dtsi | 67 +++++++++++++++++++++++++++++++++++
>>> 1 file changed, 67 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/qcom/sa8775p.dtsi b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
>>> index 3394ae2d13003417a15e64c9e47833725ec779e6..09db8e2eb578f1cada0f4a15e3f844dc097bd46d 100644
>>> --- a/arch/arm64/boot/dts/qcom/sa8775p.dtsi
>>> +++ b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
>>> @@ -10,6 +10,7 @@
>>> #include <dt-bindings/clock/qcom,sa8775p-dispcc.h>
>>> #include <dt-bindings/clock/qcom,sa8775p-gcc.h>
>>> #include <dt-bindings/clock/qcom,sa8775p-gpucc.h>
>>> +#include <dt-bindings/clock/qcom,sa8775p-videocc.h>
>>> #include <dt-bindings/dma/qcom-gpi.h>
>>> #include <dt-bindings/interconnect/qcom,sa8775p-rpmh.h>
>>> #include <dt-bindings/mailbox/qcom-ipcc.h>
>>> @@ -3783,6 +3784,72 @@ llcc: system-cache-controller@9200000 {
>>> interrupts = <GIC_SPI 580 IRQ_TYPE_LEVEL_HIGH>;
>>> };
>>>
>>> + iris: video-codec@aa00000 {
>>> + compatible = "qcom,sa8775p-iris";
>>> +
>>> + reg = <0 0x0aa00000 0 0xf0000>;
>>> + interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
>>> +
>>> + power-domains = <&videocc VIDEO_CC_MVS0C_GDSC>,
>>> + <&videocc VIDEO_CC_MVS0_GDSC>,
>>> + <&rpmhpd SA8775P_MXC>,
>>> + <&rpmhpd SA8775P_MMCX>;
>>> + power-domain-names = "venus",
>>> + "vcodec0",
>>> + "mx",
>>> + "mmcx";
>>> + operating-points-v2 = <&iris_opp_table>;
>>> +
>>> + clocks = <&gcc GCC_VIDEO_AXI0_CLK>,
>>> + <&videocc VIDEO_CC_MVS0C_CLK>,
>>> + <&videocc VIDEO_CC_MVS0_CLK>;
>>> + clock-names = "iface",
>>> + "core",
>>> + "vcodec0_core";
>>> +
>>> + interconnects = <&gem_noc MASTER_APPSS_PROC QCOM_ICC_TAG_ALWAYS
>>> + &config_noc SLAVE_VENUS_CFG QCOM_ICC_TAG_ALWAYS>,
>>
>> This path should use QCOM_ICC_TAG_ACTIVE_ONLY on both endpoints
> What is the advantage of "ALWAYS" vs "ACTIVE_ONLY". Thinking of a possibility of
> APSS power collapsed, while video hardware is processing a frame ?
That's totally okay, I'm requesting ACTIVE_ONLY just on the cpu-cfg path,
which must not be used if APSS if offline anyway
Konrad
next prev parent reply other threads:[~2025-03-18 14:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 12:03 [PATCH 0/4] media: qcom: iris: add support for SA8775P Vikash Garodia
2025-03-11 12:03 ` [PATCH 1/4] dt-bindings: media: qcom,sm8550-iris: update power domain name Vikash Garodia
2025-03-11 14:52 ` Rob Herring (Arm)
2025-03-11 15:07 ` Dmitry Baryshkov
2025-03-11 15:11 ` Vikash Garodia
2025-03-11 15:35 ` Dmitry Baryshkov
2025-03-11 19:19 ` Vikash Garodia
2025-03-11 22:13 ` Dmitry Baryshkov
2025-03-11 16:24 ` Konrad Dybcio
2025-03-11 17:33 ` Krzysztof Kozlowski
2025-03-11 17:47 ` Vikash Garodia
2025-03-12 8:44 ` Krzysztof Kozlowski
2025-03-12 12:55 ` Vikash Garodia
2025-03-11 12:03 ` [PATCH 2/4] dt-bindings: media: qcom,sm8550-iris: document SA8775p IRIS accelerator Vikash Garodia
2025-03-11 15:31 ` Dmitry Baryshkov
2025-03-12 8:07 ` Vikash Garodia
2025-03-12 8:51 ` Dmitry Baryshkov
2025-03-11 17:35 ` Krzysztof Kozlowski
2025-03-11 17:57 ` Vikash Garodia
2025-03-12 8:42 ` Krzysztof Kozlowski
2025-03-11 12:03 ` [PATCH 3/4] arm64: dts: qcom: sa8775p: add support for video node Vikash Garodia
2025-03-15 13:43 ` Konrad Dybcio
2025-03-15 14:04 ` Konrad Dybcio
2025-03-15 18:32 ` Dmitry Baryshkov
2025-03-17 6:00 ` Vikash Garodia
2025-03-17 11:29 ` Dmitry Baryshkov
2025-03-18 14:24 ` Vikash Garodia
2025-03-18 14:33 ` Konrad Dybcio [this message]
2025-03-18 15:38 ` Vikash Garodia
2025-03-17 11:31 ` Dmitry Baryshkov
2025-03-18 12:22 ` Konrad Dybcio
2025-03-18 13:43 ` Vikash Garodia
2025-03-11 12:03 ` [PATCH 4/4] media: iris: add compatible string for sa8775p Vikash Garodia
2025-03-11 15:32 ` Dmitry Baryshkov
2025-03-11 17:34 ` 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=9940290b-6b97-4339-848d-ea95a365f74c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@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=quic_abhinavk@quicinc.com \
--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
all inboxes | Powered by JetHome®