From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
freedreno@lists.freedesktop.org, Rob Clark <robdclark@gmail.com>,
Sean Paul <sean@poorly.run>, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, quic_jesszhan@quicinc.com,
marijn.suijten@somainline.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] drm/msm/dpu: remove DPU_DSPP_IGC handling in dspp flush
Date: Thu, 27 Apr 2023 18:56:35 +0300 [thread overview]
Message-ID: <3e0b8680-4722-7e5a-a75b-acba1940aa1a@linaro.org> (raw)
In-Reply-To: <20230426192246.5517-2-quic_abhinavk@quicinc.com>
On 26/04/2023 22:22, Abhinav Kumar wrote:
> Inverse gamma correction blocks (IGC) are not used today so lets
> remove the usage of DPU_DSPP_IGC in the dspp flush to make it easier
> to remove IGC from the catalog.
>
> We can add this back when IGC is properly supported in DPU with
> one of the standard DRM properties.
>
> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-04-27 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 19:22 [PATCH v2 1/4] drm/msm/dpu: remove DPU_DSPP_GC " Abhinav Kumar
2023-04-26 19:22 ` [PATCH v2 2/4] drm/msm/dpu: remove DPU_DSPP_IGC " Abhinav Kumar
2023-04-27 15:56 ` Dmitry Baryshkov [this message]
2023-04-27 20:23 ` Marijn Suijten
2023-04-26 19:22 ` [PATCH v2 3/4] drm/msm/dpu: remove GC related code from dpu catalog Abhinav Kumar
2023-04-27 15:57 ` Dmitry Baryshkov
2023-04-27 20:20 ` Abhinav Kumar
2023-04-27 20:26 ` Marijn Suijten
2023-04-26 19:22 ` [PATCH v2 4/4] drm/msm/dpu: drop DSPP_MSM8998_MASK from hw catalog Abhinav Kumar
2023-04-27 15:57 ` Dmitry Baryshkov
2023-04-27 20:24 ` Marijn Suijten
2023-04-27 20:22 ` [PATCH v2 1/4] drm/msm/dpu: remove DPU_DSPP_GC handling in dspp flush 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=3e0b8680-4722-7e5a-a75b-acba1940aa1a@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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®