From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"Jay Liu (刘博)" <Jay.Liu@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"Yongqiang Niu (牛永强)" <yongqiang.niu@mediatek.com>,
"robh@kernel.org" <robh@kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"hsinyi@chromium.org" <hsinyi@chromium.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 2/7] drm/mediatek: fix CCORR mtk_ctm_s31_32_to_s1_n function issue
Date: Thu, 7 Aug 2025 11:30:59 +0000 [thread overview]
Message-ID: <5d87836c4c78f7f98233d5c304ef2770d43b0e2d.camel@mediatek.com> (raw)
In-Reply-To: <8b589879a5e4b60041bee5303697b2a6a707ee9e.camel@mediatek.com>
On Thu, 2025-08-07 at 06:19 +0000, Jay Liu (刘博) wrote:
> On Wed, 2025-08-06 at 06:37 +0000, CK Hu (胡俊光) wrote:
> > On Sun, 2025-07-27 at 15:15 +0800, Jay Liu wrote:
> > > if matrixbit is 11,
> > > The range of color matrix is from 0 to (BIT(12) - 1).
> > > Values from 0 to (BIT(11) - 1) represent positive numbers,
> > > values from BIT(11) to (BIT(12) - 1) represent negative numbers.
> > > For example, -1 need converted to 8191.
> > > so convert S31.32 to HW Q2.11 format by
> > > drm_color_ctm_s31_32_to_qm_n,
> > > and set int_bits to 2.
> >
> > You change the behavior of MT8183 CCORR and MT8192 CCORR.
> > These two SoC has work for a long time.
> > Does both SoC really have bug?
> >
> > In comment below, it shows that HW S1.n format.
> > The patch sender has much information about the hardware information.
> > Would they make mistake?
> > If only MT8196 CCORR has the format qm_n, use private data to
> > distinguish the behavior.
> >
> > Regards,
> > CK
> >
> Yes. We received an email from customer, they found that the previous
> patch failed to handle negative values correctly, so the result was not
> as expected and they would like this issue fixed in the current update.
> We also consulted with the DE; the hardware itself supports negative
> numbers and all ICs behave the same in this regard. The current patch
> converts negative values into a format that the hardware can properly
> recognize.
OK, move this patch out of this series.
Send this patch independently.
And this is a fixup patch, so Add 'Fixes' tag.
Regards,
CK
>
> Best Regards,
> Jay Liu
>
> > >
> > > Fixes: 738ed4156fba ("drm/mediatek: Add matrix_bits private data
> > > for ccorr")
> > > Reviewed-by: AngeloGioacchino Del Regno <
> > > angelogioacchino.delregno@collabora.com>
> > > Signed-off-by: Jay Liu <jay.liu@mediatek.com>
> > > Signed-off-by: 20220315152503 created <jay.liu@mediatek.com>
> > > ---
> > > drivers/gpu/drm/mediatek/mtk_disp_ccorr.c | 24 ++-----------------
> > > ----
> > > 1 file changed, 2 insertions(+), 22 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/mediatek/mtk_disp_ccorr.c
> > > b/drivers/gpu/drm/mediatek/mtk_disp_ccorr.c
> > > index 85ba109d6383..b097c20877f3 100644
> > > --- a/drivers/gpu/drm/mediatek/mtk_disp_ccorr.c
> > > +++ b/drivers/gpu/drm/mediatek/mtk_disp_ccorr.c
> > > @@ -80,27 +80,6 @@ void mtk_ccorr_stop(struct device *dev)
> > > writel_relaxed(0x0, ccorr->regs + DISP_CCORR_EN);
> > > }
> > >
> > > -/* Converts a DRM S31.32 value to the HW S1.n format. */
> > > -static u16 mtk_ctm_s31_32_to_s1_n(u64 in, u32 n)
> > > -{
> > > - u16 r;
> > > -
> > > - /* Sign bit. */
> > > - r = in & BIT_ULL(63) ? BIT(n + 1) : 0;
> > > -
> > > - if ((in & GENMASK_ULL(62, 33)) > 0) {
> > > - /* identity value 0x100000000 -> 0x400(mt8183), */
> > > - /* identity value 0x100000000 -> 0x800(mt8192), */
> > > - /* if bigger this, set it to max 0x7ff. */
> > > - r |= GENMASK(n, 0);
> > > - } else {
> > > - /* take the n+1 most important bits. */
> > > - r |= (in >> (32 - n)) & GENMASK(n, 0);
> > > - }
> > > -
> > > - return r;
> > > -}
> > > -
> > > bool mtk_ccorr_ctm_set(struct device *dev, struct drm_crtc_state
> > > *state)
> > > {
> > > struct mtk_disp_ccorr *ccorr = dev_get_drvdata(dev);
> > > @@ -109,6 +88,7 @@ bool mtk_ccorr_ctm_set(struct device *dev,
> > > struct drm_crtc_state *state)
> > > const u64 *input;
> > > uint16_t coeffs[9] = { 0 };
> > > int i;
> > > + int int_bits = 2;
> > > struct cmdq_pkt *cmdq_pkt = NULL;
> > > u32 matrix_bits = ccorr->data->matrix_bits;
> > >
> > > @@ -119,7 +99,7 @@ bool mtk_ccorr_ctm_set(struct device *dev,
> > > struct drm_crtc_state *state)
> > > input = ctm->matrix;
> > >
> > > for (i = 0; i < ARRAY_SIZE(coeffs); i++)
> > > - coeffs[i] = mtk_ctm_s31_32_to_s1_n(input[i],
> > > matrix_bits);
> > > + coeffs[i] = drm_color_ctm_s31_32_to_qm_n(input[i],
> > > int_bits, matrix_bits);
> > >
> > > mtk_ddp_write(cmdq_pkt, coeffs[0] << 16 | coeffs[1],
> > > &ccorr->cmdq_reg, ccorr->regs,
> > > DISP_CCORR_COEF_0);
> >
> >
next prev parent reply other threads:[~2025-08-07 11:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 7:15 [PATCH v2 0/7] porting pq compnent for MT8196 Jay Liu
2025-07-27 7:15 ` [PATCH v2 1/7] drm/mediatek: Add CCORR component support " Jay Liu
2025-08-04 8:57 ` AngeloGioacchino Del Regno
2025-08-06 6:24 ` CK Hu (胡俊光)
2025-07-27 7:15 ` [PATCH v2 2/7] drm/mediatek: fix CCORR mtk_ctm_s31_32_to_s1_n function issue Jay Liu
2025-08-06 6:37 ` CK Hu (胡俊光)
2025-08-07 6:19 ` Jay Liu (刘博)
2025-08-07 11:30 ` CK Hu (胡俊光) [this message]
2025-07-27 7:15 ` [PATCH v2 3/7] drm/mediatek: Add TDSHP component support for MT8196 Jay Liu
2025-08-06 6:45 ` CK Hu (胡俊光)
2025-07-27 7:15 ` [PATCH v2 4/7] dt-bindings: display: mediatek: disp-tdshp: Add " Jay Liu
2025-07-27 20:27 ` Rob Herring (Arm)
2025-07-28 12:01 ` Krzysztof Kozlowski
2025-07-29 3:22 ` Jay Liu (刘博)
2025-08-06 6:50 ` CK Hu (胡俊光)
2025-07-27 7:15 ` [PATCH v2 5/7] dt-bindings: display: mediatek: ccorr: " Jay Liu
2025-07-27 20:27 ` Rob Herring (Arm)
2025-07-27 20:35 ` Rob Herring
2025-07-28 6:52 ` Jay Liu (刘博)
2025-07-27 7:15 ` [PATCH v2 6/7] dt-bindings: display: mediatek: dither: " Jay Liu
2025-07-27 20:27 ` Rob Herring (Arm)
2025-08-06 6:53 ` CK Hu (胡俊光)
2025-07-27 7:15 ` [PATCH v2 7/7] dt-bindings: display: mediatek: gamma: " Jay Liu
2025-07-27 20:27 ` Rob Herring (Arm)
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=5d87836c4c78f7f98233d5c304ef2770d43b0e2d.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Jay.Liu@mediatek.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hsinyi@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=yongqiang.niu@mediatek.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;
as well as URLs for NNTP newsgroup(s).