From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: Konrad Dybcio <konrad.dybcio@somainline.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
<dri-devel@lists.freedesktop.org>, <robdclark@gmail.com>,
<sean@poorly.run>, <swboyd@chromium.org>, <dianders@chromium.org>,
<vkoul@kernel.org>, <daniel@ffwll.ch>, <airlied@gmail.com>,
<agross@kernel.org>, <dmitry.baryshkov@linaro.org>,
<andersson@kernel.org>, <quic_jesszhan@quicinc.com>,
<quic_sbillaka@quicinc.com>, <freedreno@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v8 1/8] drm/msm/dpu: add dsc blocks for remaining chipsets in catalog
Date: Mon, 15 May 2023 14:26:59 -0700 [thread overview]
Message-ID: <d7d7cc13-25e4-5a8e-e803-e8c3cfbe22a3@quicinc.com> (raw)
In-Reply-To: <zkvmqpcdgeg3qjkddopqx2yfipmqjjyva2cnk5bq4npxzxto4v@gfgvp5hkblkm>
On 5/15/2023 2:23 PM, Marijn Suijten wrote:
> On 2023-05-15 13:58:35, Abhinav Kumar wrote:
>>
>>
>>
>> On 5/15/2023 1:07 PM, Marijn Suijten wrote:
>>> On 2023-05-15 11:20:02, Abhinav Kumar wrote:
>>>>
>>>>
>>>>
>>>> On 5/14/2023 2:39 PM, Marijn Suijten wrote:
>>>>> DSC*, and mention 1.1 explicitly (since this skips the 1.2 blocks, while
>>>>> the series is clearly aimed at 1.1...). This was done for the DSC 1.2
>>>>> HW block patch after all.
>>>>>
>>>>> in catalog -> to catalog
>>>>>
>>>>> But it's just two platforms, you can fit MSM8998 and SC8180X in the
>>>>> title.
>>>>>
>>>>> On 2023-05-12 11:00:16, Kuogee Hsieh wrote:
>>>>>>
>>>>>> From: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>>>>>
>>>>>> There are some platforms has DSC blocks but it is not declared at catalog.
>>>>>
>>>>> Some platforms have DSC blocks which have not yet been declared in the
>>>>> catalog.*
>>>>>
>>>>>> For completeness, this patch adds DSC blocks for platforms which missed
>>>>>> them.
>>>>>
>>>>> Drop "this patch":
>>>>>
>>>>> Complete DSC 1.1 support for all platforms by adding the missing
>>>>> blocks to MSM8998 and SC8180X.
>>>>>
>>>>>>
>>>>>> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>>>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>>> ---
>>>>>> drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_3_0_msm8998.h | 7 +++++++
>>>>>> drivers/gpu/drm/msm/disp/dpu1/catalog/dpu_5_1_sc8180x.h | 11 +++++++++++
>>>>>
>>>>> How about SC7180, and any other DPU 6.x revision?
>>>>>
>>>>
>>>> Will let kuogee respond to the other nits. There is no DSC in sc7180 /
>>>> sm6115 / qcm2290. So this patch is complete.
>>>
>>> Thank you for checking as I didn't have the DTS close (and it seems
>>> SC7180 would have supported this, but no). I did check other SoCs in
>>> the DPU 6.x range that are currently floating in my tree and on the
>>> list, which do need their DSC 1.1 block added (both a single block at
>>> 0x81000 downstream, 0x80000 upstream), if you can in a resend Konrad:
>>>
>>> DPU 6.4 in SM6350: https://lore.kernel.org/linux-arm-msm/20230411-topic-straitlagoon_mdss-v3-6-9837d6b3516d@linaro.org/
>>> DPU 6.9 in SM6375: https://lore.kernel.org/linux-arm-msm/20230411-topic-straitlagoon_mdss-v3-8-9837d6b3516d@linaro.org/
>>>
>>
>> If these are still on the list, can Konrad add them to his change as
>> that way his catalog change will be complete? Otherwise I would prefer
>> to add them in a follow up change because marking this change as
>> dependent on a catalog change which adds a new chipset is not right.
>
> The question was for Konrad (and I addressed him by name, not you) as
> his series is not merged and the DSC blocks can be added to it directly
> without depending on this series. DSC 1.1 is after all available for
> some time now.
>
Thanks for clarifying. Your reply was cut-off "if you can in a resend
Konrad" so not sure what you were trying to tell.
> - Marijn
next prev parent reply other threads:[~2023-05-15 21:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 18:00 [PATCH v8 0/8] add DSC 1.2 dpu supports Kuogee Hsieh
2023-05-12 18:00 ` [PATCH v8 1/8] drm/msm/dpu: add dsc blocks for remaining chipsets in catalog Kuogee Hsieh
2023-05-14 21:39 ` Marijn Suijten
2023-05-15 18:20 ` Abhinav Kumar
2023-05-15 20:07 ` Marijn Suijten
2023-05-15 20:58 ` Abhinav Kumar
2023-05-15 21:23 ` Marijn Suijten
2023-05-15 21:26 ` Abhinav Kumar [this message]
2023-05-12 18:00 ` [PATCH v8 2/8] drm/msm/dpu: add DPU_PINGPONG_DSC feature bit for DPU < 7.0.0 Kuogee Hsieh
2023-05-12 18:17 ` Dmitry Baryshkov
2023-05-13 19:26 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 3/8] drm/msm/dpu: test DPU_PINGPONG_DSC bit before assign DSC ops to PINGPONG Kuogee Hsieh
2023-05-14 21:43 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 4/8] drm/msm/dpu: Introduce PINGPONG_NONE to disconnect DSC from PINGPONG Kuogee Hsieh
2023-05-12 18:00 ` [PATCH v8 5/8] drm/msm/dpu: add support for DSC encoder v1.2 engine Kuogee Hsieh
2023-05-12 18:19 ` Dmitry Baryshkov
2023-05-12 20:48 ` Kuogee Hsieh
2023-05-12 21:04 ` Dmitry Baryshkov
2023-05-14 21:46 ` Marijn Suijten
2023-05-15 17:46 ` Kuogee Hsieh
2023-05-15 18:08 ` Dmitry Baryshkov
2023-05-15 20:11 ` Marijn Suijten
2023-05-14 22:18 ` Marijn Suijten
2023-05-15 17:06 ` Kuogee Hsieh
2023-05-15 20:17 ` Marijn Suijten
2023-05-15 17:36 ` Kuogee Hsieh
2023-05-12 18:00 ` [PATCH v8 6/8] drm/msm/dpu: separate DSC flush update out of interface Kuogee Hsieh
2023-05-12 18:21 ` Dmitry Baryshkov
2023-05-12 18:47 ` Abhinav Kumar
2023-05-12 18:50 ` Dmitry Baryshkov
2023-05-12 19:05 ` Abhinav Kumar
2023-05-15 21:52 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 7/8] drm/msm/dpu: add DSC 1.2 hw blocks for relevant chipsets Kuogee Hsieh
2023-05-15 21:21 ` Marijn Suijten
2023-05-15 22:03 ` Abhinav Kumar
2023-05-15 22:10 ` [Freedreno] " Abhinav Kumar
2023-05-15 22:23 ` Marijn Suijten
2023-05-15 23:58 ` Abhinav Kumar
2023-05-15 21:24 ` Marijn Suijten
2023-05-12 18:00 ` [PATCH v8 8/8] drm/msm/dpu: tear down DSC data path when DSC disabled Kuogee Hsieh
2023-05-14 21:31 ` [PATCH v8 0/8] add DSC 1.2 dpu supports Marijn Suijten
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=d7d7cc13-25e4-5a8e-e803-e8c3cfbe22a3@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=agross@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
--cc=vkoul@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®