From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: Kuogee Hsieh <quic_khsieh@quicinc.com>,
<freedreno@lists.freedesktop.org>, <quic_sbillaka@quicinc.com>,
<andersson@kernel.org>, <dri-devel@lists.freedesktop.org>,
<dianders@chromium.org>, <vkoul@kernel.org>, <agross@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <dmitry.baryshkov@linaro.org>,
<quic_jesszhan@quicinc.com>, <swboyd@chromium.org>,
<sean@poorly.run>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 7/8] drm/msm/dpu: add DSC 1.2 hw blocks for relevant chipsets
Date: Thu, 18 May 2023 12:00:22 -0700 [thread overview]
Message-ID: <a89169b0-159d-486d-996c-897e3a0048a4@quicinc.com> (raw)
In-Reply-To: <xvcl5ojsrifi26trso6nvvfsimtijygp3iizhl4djdrerc5lej@xrwsawvb3k4t>
On 5/18/2023 12:05 AM, Marijn Suijten wrote:
> On 2023-05-17 16:22:37, Abhinav Kumar wrote:
> <snip>
>>>> @@ -529,6 +539,19 @@ static const struct dpu_pingpong_sub_blks sc7280_pp_sblk = {
>>>> .features = _features, \
>>>> }
>>>>
>>>> +/*
>>>> + * NOTE: Each display compression engine (DCE) contains dual hard
>>>> + * slice DSC encoders so both share same base address but with
>>>> + * its own different sub block address.
>>>> + */
>>>
>>> I still think this comment is superfluous (and doesn't even apply
>>> generically, see i.e. sc7280) and should best be kept exclusively in the
>>> SoC-specific catalog files.
>>>
>>> - Marijn
>>>
>>
>> sc7280 is the only exception as it has only one encoder. But, by and
>> large, for all other chipsets this is true and hence kept here.
>>
>> The main reason for this comment is people should not get confused that
>> how come two DSC encoders have the same base address.
>
> And that's why the comment is already placed in the SoC-specific catalog
> files where a duplicate base address is visible. It is not visible
> here.
>
> - Marijn
>
ok, if kuogee pushes a v11, we can drop it.
>>>> +#define DSC_BLK_1_2(_name, _id, _base, _len, _features, _sblk) \
>>>> + {\
>>>> + .name = _name, .id = _id, \
>>>> + .base = _base, .len = _len, \
>>>> + .features = BIT(DPU_DSC_HW_REV_1_2) | _features, \
>>>> + .sblk = &_sblk, \
>>>> + }
>>>> +
>>>> /*************************************************************
>>>> * INTF sub blocks config
>>>> *************************************************************/
>>>> --
>>>> 2.7.4
>>>>
next prev parent reply other threads:[~2023-05-18 19:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 22:01 [PATCH v10 0/8] add DSC 1.2 dpu supports Kuogee Hsieh
2023-05-17 22:01 ` [PATCH v10 1/8] drm/msm/dpu: add dsc blocks to the catalog of MSM8998 and SC8180X Kuogee Hsieh
2023-05-17 22:14 ` Marijn Suijten
2023-05-17 22:01 ` [PATCH v10 2/8] drm/msm/dpu: add DPU_PINGPONG_DSC feature bit for DPU < 7.0.0 Kuogee Hsieh
2023-05-17 22:01 ` [PATCH v10 3/8] drm/msm/dpu: Guard PINGPONG DSC ops behind DPU_PINGPONG_DSC bit Kuogee Hsieh
2023-05-18 0:29 ` Dmitry Baryshkov
2023-05-17 22:01 ` [PATCH v10 4/8] drm/msm/dpu: Introduce PINGPONG_NONE to disconnect DSC from PINGPONG Kuogee Hsieh
2023-05-17 22:01 ` [PATCH v10 5/8] drm/msm/dpu: add support for DSC encoder v1.2 engine Kuogee Hsieh
2023-05-17 22:22 ` Marijn Suijten
2023-05-18 0:32 ` Dmitry Baryshkov
2023-05-17 22:01 ` [PATCH v10 6/8] drm/msm/dpu: separate DSC flush update out of interface Kuogee Hsieh
2023-05-17 22:31 ` Marijn Suijten
2023-05-18 22:09 ` Kuogee Hsieh
2023-05-18 22:40 ` Dmitry Baryshkov
2023-05-19 12:04 ` Marijn Suijten
2023-05-18 0:35 ` Dmitry Baryshkov
2023-05-18 7:03 ` Marijn Suijten
2023-05-17 22:01 ` [PATCH v10 7/8] drm/msm/dpu: add DSC 1.2 hw blocks for relevant chipsets Kuogee Hsieh
2023-05-17 22:47 ` Marijn Suijten
2023-05-17 23:22 ` Abhinav Kumar
2023-05-18 7:05 ` Marijn Suijten
2023-05-18 19:00 ` Abhinav Kumar [this message]
2023-05-17 22:01 ` [PATCH v10 8/8] drm/msm/dpu: tear down DSC data path when DSC disabled Kuogee Hsieh
2023-05-17 22:53 ` 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=a89169b0-159d-486d-996c-897e3a0048a4@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.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=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®