From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Krishna Manikandan <quic_mkrishn@quicinc.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: [PATCH v2 07/13] drm/msm/dpu: Add SM6350 support
Date: Fri, 21 Apr 2023 01:05:05 +0200 [thread overview]
Message-ID: <4da9bd19-9403-812e-4554-847b18df78c9@linaro.org> (raw)
In-Reply-To: <fd2f43eb-aa10-eaf4-62f8-945a3152a28a@linaro.org>
On 21.04.2023 00:41, Dmitry Baryshkov wrote:
> On 21/04/2023 01:31, Konrad Dybcio wrote:
>> Add SM6350 support to the DPU1 driver to enable display output.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
[...]
>> +
>> +static const struct dpu_sspp_cfg sm6350_sspp[] = {
>> + SSPP_BLK("sspp_0", SSPP_VIG0, 0x4000, 0x1f8, VIG_SC7180_MASK,
>> + sc7180_vig_sblk_0, 0, SSPP_TYPE_VIG, DPU_CLK_CTRL_VIG0),
>> + SSPP_BLK("sspp_8", SSPP_DMA0, 0x24000, 0x1f8, DMA_SDM845_MASK,
>> + sdm845_dma_sblk_0, 1, SSPP_TYPE_DMA, DPU_CLK_CTRL_DMA0),
>> + SSPP_BLK("sspp_9", SSPP_DMA1, 0x26000, 0x1f8, DMA_CURSOR_SDM845_MASK,
>> + sdm845_dma_sblk_1, 5, SSPP_TYPE_DMA, DPU_CLK_CTRL_CURSOR0),
>
> DPU_CLK_CTRL_DMA0
>
>> + SSPP_BLK("sspp_10", SSPP_DMA2, 0x28000, 0x1f8, DMA_CURSOR_SDM845_MASK,
>> + sdm845_dma_sblk_2, 9, SSPP_TYPE_DMA, DPU_CLK_CTRL_CURSOR1),
>
> DPU_CLK_CTRL_DMA2
_DMA1?
>
>
>> +};
>> +
>> +static const struct dpu_qos_lut_entry sm6350_qos_linear_macrotile[] = {
>> + {.fl = 0, .lut = 0x0011223344556677 },
>> + {.fl = 0, .lut = 0x0011223445566777 },
>
> Do we need two equal entries here?
Hmm.. looks like the SDE driver dropped the fill level
logic in 4.19 times and that might have thrown me off
when porting this Since the [0] entry has what looks
like a lower LUT value, should I give it .fl=1?
>
> Also please push the qos to the dpu_hw_catalog.c, I want to take another look at these structures and it is easier if all of them are beneath one's eyes.
Will do.
>
>> +};
>> +
>> +static const struct dpu_perf_cfg sm6350_perf_data = {
>> + .max_bw_low = 4200000,
>> + .max_bw_high = 5100000,
>> + .min_core_ib = 2500000,
>> + .min_llcc_ib = 0,
>> + .min_dram_ib = 1600000,
>> + .min_prefill_lines = 35,
>> + /* TODO: confirm danger_lut_tbl */
>> + .danger_lut_tbl = {0xffff, 0xffff, 0x0, 0x0, 0xffff},
[...]
>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h
>> @@ -320,6 +320,8 @@ enum dpu_qos_lut_usage {
>> DPU_QOS_LUT_USAGE_LINEAR,
>> DPU_QOS_LUT_USAGE_MACROTILE,
>> DPU_QOS_LUT_USAGE_NRT,
>> + DPU_QOS_LUT_USAGE_CWB,
>> + DPU_QOS_LUT_USAGE_MACROTILE_QSEED,
>
> This should probably be removed. It would be nice to clean these things up, but not as a part of sm6350.
Well, I won't be able to fill in the danger LUT table otherwise!
Konrad
>
>> DPU_QOS_LUT_USAGE_MAX,
>> };
>> @@ -880,6 +882,7 @@ extern const struct dpu_mdss_cfg dpu_sc8180x_cfg;
>> extern const struct dpu_mdss_cfg dpu_sm8250_cfg;
>> extern const struct dpu_mdss_cfg dpu_sc7180_cfg;
>> extern const struct dpu_mdss_cfg dpu_sm6115_cfg;
>> +extern const struct dpu_mdss_cfg dpu_sm6350_cfg;
>> extern const struct dpu_mdss_cfg dpu_qcm2290_cfg;
>> extern const struct dpu_mdss_cfg dpu_sm8350_cfg;
>> extern const struct dpu_mdss_cfg dpu_sc7280_cfg;
>> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
>> index 0e7a68714e9e..46be7ad8d615 100644
>> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
>> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
>> @@ -1286,6 +1286,7 @@ static const struct of_device_id dpu_dt_match[] = {
>> { .compatible = "qcom,sc8180x-dpu", .data = &dpu_sc8180x_cfg, },
>> { .compatible = "qcom,sc8280xp-dpu", .data = &dpu_sc8280xp_cfg, },
>> { .compatible = "qcom,sm6115-dpu", .data = &dpu_sm6115_cfg, },
>> + { .compatible = "qcom,sm6350-dpu", .data = &dpu_sm6350_cfg, },
>> { .compatible = "qcom,sm8150-dpu", .data = &dpu_sm8150_cfg, },
>> { .compatible = "qcom,sm8250-dpu", .data = &dpu_sm8250_cfg, },
>> { .compatible = "qcom,sm8350-dpu", .data = &dpu_sm8350_cfg, },
>>
>
next prev parent reply other threads:[~2023-04-20 23:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 22:31 [PATCH v2 00/13] SM63(50|75) DPU support Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 01/13] dt-bindings: display/msm: dsi-controller-main: Add SM6350 Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 02/13] dt-bindings: display/msm: dsi-controller-main: Add SM6375 Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 03/13] dt-bindings: display/msm: Add SM6350 DPU Konrad Dybcio
2023-04-25 16:53 ` Rob Herring
2023-04-25 17:03 ` Rob Herring
2023-05-05 12:38 ` Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 04/13] dt-bindings: display/msm: Add SM6350 MDSS Konrad Dybcio
2023-04-21 12:56 ` Rob Herring
2023-04-20 22:31 ` [PATCH v2 05/13] dt-bindings: display/msm: Add SM6375 DPU Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 06/13] dt-bindings: display/msm: Add SM6375 MDSS Konrad Dybcio
2023-04-21 12:56 ` Rob Herring
2023-04-20 22:31 ` [PATCH v2 07/13] drm/msm/dpu: Add SM6350 support Konrad Dybcio
2023-04-20 22:41 ` Dmitry Baryshkov
2023-04-20 23:05 ` Konrad Dybcio [this message]
2023-04-20 23:06 ` Dmitry Baryshkov
2023-05-18 21:21 ` Dmitry Baryshkov
2023-04-27 15:37 ` Marijn Suijten
2023-04-27 15:48 ` Marijn Suijten
2023-04-28 12:25 ` Konrad Dybcio
2023-04-28 12:24 ` Konrad Dybcio
2023-04-28 13:03 ` Dmitry Baryshkov
2023-05-08 22:03 ` Marijn Suijten
2023-05-05 12:11 ` Dmitry Baryshkov
2023-05-08 22:04 ` Marijn Suijten
2023-04-20 22:31 ` [PATCH v2 08/13] drm/msm: mdss: " Konrad Dybcio
2023-04-20 22:43 ` Dmitry Baryshkov
2023-04-27 21:03 ` Marijn Suijten
2023-04-20 22:31 ` [PATCH v2 09/13] drm/msm/dpu: Add SM6375 support Konrad Dybcio
2023-04-20 22:48 ` Dmitry Baryshkov
2023-04-27 15:46 ` Marijn Suijten
2023-04-28 12:32 ` Konrad Dybcio
2023-04-20 22:31 ` [PATCH v2 10/13] drm/msm: mdss: " Konrad Dybcio
2023-04-20 22:49 ` Dmitry Baryshkov
2023-04-20 22:50 ` Dmitry Baryshkov
2023-04-20 23:06 ` Konrad Dybcio
2023-04-27 21:04 ` Marijn Suijten
2023-04-20 22:31 ` [PATCH v2 11/13] iommu/arm-smmu-qcom: Add SM6375 DPU compatible Konrad Dybcio
2023-04-20 22:52 ` Dmitry Baryshkov
2023-04-20 22:31 ` [PATCH v2 12/13] iommu/arm-smmu-qcom: Add SM6350 " Konrad Dybcio
2023-04-20 22:51 ` Dmitry Baryshkov
2023-04-20 22:31 ` [PATCH v2 13/13] iommu/arm-smmu-qcom: Sort the compatible list alphabetically Konrad Dybcio
2023-04-20 22:53 ` Dmitry Baryshkov
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=4da9bd19-9403-812e-4554-847b18df78c9@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_mkrishn@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sean@poorly.run \
--cc=will@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