From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Federico Amedeo Izzo <federico@izzo.pro>
Subject: Re: [PATCH] drm/msm/dpu: disable gamma correction unit on SC7180
Date: Mon, 17 Nov 2025 12:25:36 +0100 [thread overview]
Message-ID: <6457c60a-2ede-4df8-ad82-d974690eba89@oss.qualcomm.com> (raw)
In-Reply-To: <20251115-dpu-fix-gc-v1-1-0a4fd718208d@oss.qualcomm.com>
On 11/15/25 4:08 AM, Dmitry Baryshkov wrote:
> IGT reported test failures with Gamma correction block on SC7180.
> Disable GC subblock on SC7180 until we trage the issue.
>
> Cc: Federico Amedeo Izzo <federico@izzo.pro>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> Most likely I will squash this into the GC patch
> ---
Peeking at downstream, 7180 and 845 should have the exact same GC
(v1.8).. it seems like there's an attempt to program it through
REGDMA instead of regular reg access. Not sure if it's actually
necessary or just an optimization
What tests are exactly failing? I couldn't track it down on FDO GL
Konrad
next prev parent reply other threads:[~2025-11-17 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-15 3:08 Dmitry Baryshkov
2025-11-17 11:25 ` Konrad Dybcio [this message]
2025-11-17 11:51 ` Dmitry Baryshkov
2025-11-17 12:09 ` Konrad Dybcio
2025-11-17 13:16 ` Dmitry Baryshkov
2025-11-17 13:39 ` Konrad Dybcio
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=6457c60a-2ede-4df8-ad82-d974690eba89@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=federico@izzo.pro \
--cc=freedreno@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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®