From: Marc Gonzalez <mgonzalez@freebox.fr>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: DT <devicetree@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Pierre-Hugues Husson <phh@phh.me>
Subject: Re: [RFC WIP PATCH] venus: add qcom,no-low-power property
Date: Mon, 26 Feb 2024 14:09:19 +0100 [thread overview]
Message-ID: <33382ecb-8a73-4d2f-96b1-8048df7a6414@freebox.fr> (raw)
In-Reply-To: <d5abf142-3a2b-454c-660a-249c0fb25208@quicinc.com>
On 23/02/2024 14:48, Vikash Garodia wrote:
> On 2/20/2024 8:15 PM, Marc Gonzalez wrote:
>
>> On 20/02/2024 14:53, Vikash Garodia wrote:
>>
>>> msm8998 supports configuring the VCodec (venus core0) GDSC in HW power control
>>> mode. Could you please check and confirm if the driver is configuring only the
>>> VCodec GDSC and not the venus GDSC. Look for the attribute
>>> "qcom,support-hw-trigger" in vendor dt file.
>>
>> [ Vendor DTS for easy reference: ]
>> [ https://git.codelinaro.org/clo/la/kernel/msm-4.4/-/blob/caf_migration/kernel.lnx.4.4.r38-rel/arch/arm/boot/dts/qcom/msm8998.dtsi ]
>>
>> In the queue, we have a patch enabling the Venus Decoder (VDEC) in mainline.
>> (It is using the previously proposed "qcom,no-low-power" mechanism, but that
>> might not be necessary, if I understand correctly?)
>>
>>
>> diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi b/arch/arm64/boot/dts/qcom/msm8998.dtsi
>> index 2793cc22d381a..5084191be1446 100644
>> --- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
>> @@ -3000,6 +3000,56 @@ mdss_dsi1_phy: phy@c996400 {
>> };
>> };
>>
>> + venus: video-codec@cc00000 {
>> + compatible = "qcom,msm8998-venus";
>> + reg = <0x0cc00000 0xff000>;
>> + interrupts = <GIC_SPI 287 IRQ_TYPE_LEVEL_HIGH>;
>> + power-domains = <&mmcc VIDEO_TOP_GDSC>;
>> + clocks = <&mmcc VIDEO_CORE_CLK>,
>> + <&mmcc VIDEO_AHB_CLK>,
>> + <&mmcc VIDEO_AXI_CLK>,
>> + <&mmcc VIDEO_MAXI_CLK>;
>> + clock-names = "core", "iface", "bus", "mbus";
>> + iommus = <&mmss_smmu 0x400>,
>> + <&mmss_smmu 0x401>,
>> + <&mmss_smmu 0x40a>,
>> + <&mmss_smmu 0x407>,
>> + <&mmss_smmu 0x40e>,
>> + <&mmss_smmu 0x40f>,
>> + <&mmss_smmu 0x408>,
>> + <&mmss_smmu 0x409>,
>> + <&mmss_smmu 0x40b>,
>> + <&mmss_smmu 0x40c>,
>> + <&mmss_smmu 0x40d>,
>> + <&mmss_smmu 0x410>,
>> + <&mmss_smmu 0x411>,
>> + <&mmss_smmu 0x421>,
>> + <&mmss_smmu 0x428>,
>> + <&mmss_smmu 0x429>,
>> + <&mmss_smmu 0x42b>,
>> + <&mmss_smmu 0x42c>,
>> + <&mmss_smmu 0x42d>,
>> + <&mmss_smmu 0x411>,
>> + <&mmss_smmu 0x431>;
>> + memory-region = <&venus_mem>;
>> + status = "disabled";
>> + qcom,no-low-power; /*** WORK AROUND LOW-POWER ISSUE ***/
>> +
>> + video-decoder {
>> + compatible = "venus-decoder";
>> + clocks = <&mmcc VIDEO_SUBCORE0_CLK>;
>> + clock-names = "core";
>> + power-domains = <&mmcc VIDEO_SUBCORE0_GDSC>;
>> + };
>> +
>> + video-encoder {
>> + compatible = "venus-encoder";
>> + clocks = <&mmcc VIDEO_SUBCORE1_CLK>;
>> + clock-names = "core";
>> + power-domains = <&mmcc VIDEO_SUBCORE1_GDSC>;
>> + };
>> + };
>> +
>> mmss_smmu: iommu@cd00000 {
>> compatible = "qcom,msm8998-smmu-v2", "qcom,smmu-v2";
>> reg = <0x0cd00000 0x40000>;
>> diff --git a/drivers/media/platform/qcom/venus/core.c b/drivers/media/platform/qcom/venus/core.c
>> index a712dd4f02a5b..ad1705e510312 100644
>> --- a/drivers/media/platform/qcom/venus/core.c
>> +++ b/drivers/media/platform/qcom/venus/core.c
>> @@ -585,6 +585,43 @@ static const struct venus_resources msm8996_res = {
>> .fwname = "qcom/venus-4.2/venus.mbn",
>> };
>>
>> +static const struct freq_tbl msm8998_freq_table[] = {
>> + { 1944000, 520000000 }, /* 4k UHD @ 60 (decode only) */
>> + { 972000, 520000000 }, /* 4k UHD @ 30 */
>> + { 489600, 346666667 }, /* 1080p @ 60 */
>> + { 244800, 150000000 }, /* 1080p @ 30 */
>> + { 108000, 75000000 }, /* 720p @ 30 */
>> +};
>> +
>> +static const struct reg_val msm8998_reg_preset[] = {
>> + { 0x80124, 0x00000003 },
>> + { 0x80550, 0x01111111 },
>> + { 0x80560, 0x01111111 },
>> + { 0x80568, 0x01111111 },
>> + { 0x80570, 0x01111111 },
>> + { 0x80580, 0x01111111 },
>> + { 0xe2010, 0x00000000 },
>> +};
>> +
>> +static const struct venus_resources msm8998_res = {
>> + .freq_tbl = msm8998_freq_table,
>> + .freq_tbl_size = ARRAY_SIZE(msm8998_freq_table),
>> + .reg_tbl = msm8998_reg_preset,
>> + .reg_tbl_size = ARRAY_SIZE(msm8998_reg_preset),
>> + .clks = {"core", "iface", "bus", "mbus"},
>> + .clks_num = 4,
>> + .vcodec0_clks = { "core" },
>> + .vcodec1_clks = { "core" },
>> + .vcodec_clks_num = 1,
>> + .max_load = 2563200,
>> + .hfi_version = HFI_VERSION_3XX,
>> + .vmem_id = VIDC_RESOURCE_NONE,
>> + .vmem_size = 0,
>> + .vmem_addr = 0,
>> + .dma_mask = 0xddc00000 - 1,
>> + .fwname = "qcom/venus-4.4/venus.mbn",
>> +};
>> +
>> static const struct freq_tbl sdm660_freq_table[] = {
>> { 979200, 518400000 },
>> { 489600, 441600000 },
>> @@ -891,6 +928,7 @@ static const struct venus_resources sc7280_res = {
>> static const struct of_device_id venus_dt_match[] = {
>> { .compatible = "qcom,msm8916-venus", .data = &msm8916_res, },
>> { .compatible = "qcom,msm8996-venus", .data = &msm8996_res, },
>> + { .compatible = "qcom,msm8998-venus", .data = &msm8998_res, },
>> { .compatible = "qcom,sdm660-venus", .data = &sdm660_res, },
>> { .compatible = "qcom,sdm845-venus", .data = &sdm845_res, },
>> { .compatible = "qcom,sdm845-venus-v2", .data = &sdm845_res_v2, },
>>
>>
>>
>> @Vikash, are you saying that perhaps the DTS for video-codec@cc00000
>> needs to be written slightly differently?
>
>
> Certainly yes. For ex, in the clock list, i do not see the core clocks listed
> i.e clk_mmss_video_subcore0_clk and clk_mmss_video_subcore1_clk. You can refer
> the downstream video DT node [1] and then align it as per venus driver
> [1]
> https://git.codelinaro.org/clo/la/kernel/msm-4.4/-/blob/caf_migration/kernel.lnx.4.4.r38-rel/arch/arm/boot/dts/qcom/msm8998-vidc.dtsi
If I understand correctly (which is far from certain),
we should base the "qcom,msm8998-venus" DT node on
"qcom,sdm845-venus-v2" rather than "qcom,msm8996-venus" ?
Regards
next prev parent reply other threads:[~2024-02-26 13:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 17:18 [RFC WIP PATCH] venus: add qcom,no-low-power property Marc Gonzalez
2024-02-19 17:28 ` Konrad Dybcio
2024-02-19 17:44 ` Dmitry Baryshkov
2024-02-19 19:24 ` Bryan O'Donoghue
2024-02-20 10:56 ` Marc Gonzalez
2024-02-20 11:21 ` Bryan O'Donoghue
2024-02-20 11:37 ` Krzysztof Kozlowski
2024-02-20 12:34 ` Marc Gonzalez
2024-02-20 13:27 ` Krzysztof Kozlowski
2024-02-20 13:53 ` Vikash Garodia
2024-02-20 14:45 ` Marc Gonzalez
2024-02-23 13:48 ` Vikash Garodia
2024-02-26 13:09 ` Marc Gonzalez [this message]
2024-02-26 14:30 ` Vikash Garodia
2024-02-26 15:55 ` Marc Gonzalez
2024-02-27 6:55 ` Vikash Garodia
2024-02-27 16:11 ` Marc Gonzalez
2024-02-29 15:32 ` Vikash Garodia
2024-02-29 16:24 ` Marc Gonzalez
2024-02-29 16:47 ` Jeffrey Hugo
2024-03-12 18:39 ` Konrad Dybcio
2024-04-10 10:24 ` Vikash Garodia
2024-04-08 15:39 ` Marc Gonzalez
2024-04-09 11:27 ` Bryan O'Donoghue
2024-04-09 14:09 ` Marc Gonzalez
2024-04-09 16:53 ` Marc Gonzalez
2024-04-10 8:17 ` Bryan O'Donoghue
2024-04-10 10:34 ` Vikash Garodia
2024-04-10 12:23 ` Marc Gonzalez
2024-04-10 13:14 ` Bryan O'Donoghue
2024-04-10 13:18 ` Marc Gonzalez
2024-04-10 13:29 ` Bryan O'Donoghue
2024-04-10 13:31 ` Bryan O'Donoghue
2024-04-11 9:02 ` Bryan O'Donoghue
2024-04-25 16:43 ` Marc Gonzalez
2024-04-30 16:13 ` venus decoder hangs at EOF Marc Gonzalez
2024-02-19 18:33 ` [RFC WIP PATCH] venus: add qcom,no-low-power property Rob Herring
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=33382ecb-8a73-4d2f-96b1-8048df7a6414@freebox.fr \
--to=mgonzalez@freebox.fr \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=phh@phh.me \
--cc=quic_vgarodia@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=stanimir.k.varbanov@gmail.com \
/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