From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: uma.shankar@intel.com, chaitanya.kumar.borah@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH] drm/i915/color: Use correct variable to load lut
Date: Wed, 9 Oct 2024 12:07:53 +0530 [thread overview]
Message-ID: <20241009063753.1799234-2-suraj.kandpal@intel.com> (raw)
Use the blob variable instead of post_csc_lut as it may end up
being null.
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
---
drivers/gpu/drm/i915/display/intel_color.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
index caf1af039960..22b7090c4f6f 100644
--- a/drivers/gpu/drm/i915/display/intel_color.c
+++ b/drivers/gpu/drm/i915/display/intel_color.c
@@ -1503,7 +1503,7 @@ static void ivb_load_luts(const struct intel_crtc_state *crtc_state)
ivb_load_lut_10(crtc_state, pre_csc_lut, PAL_PREC_SPLIT_MODE |
PAL_PREC_INDEX_VALUE(0));
ivb_load_lut_ext_max(crtc_state);
- ivb_load_lut_10(crtc_state, post_csc_lut, PAL_PREC_SPLIT_MODE |
+ ivb_load_lut_10(crtc_state, blob, PAL_PREC_SPLIT_MODE |
PAL_PREC_INDEX_VALUE(512));
break;
case GAMMA_MODE_MODE_10BIT:
@@ -1531,7 +1531,7 @@ static void bdw_load_luts(const struct intel_crtc_state *crtc_state)
bdw_load_lut_10(crtc_state, pre_csc_lut, PAL_PREC_SPLIT_MODE |
PAL_PREC_INDEX_VALUE(0));
ivb_load_lut_ext_max(crtc_state);
- bdw_load_lut_10(crtc_state, post_csc_lut, PAL_PREC_SPLIT_MODE |
+ bdw_load_lut_10(crtc_state, blob, PAL_PREC_SPLIT_MODE |
PAL_PREC_INDEX_VALUE(512));
break;
case GAMMA_MODE_MODE_10BIT:
--
2.43.2
next reply other threads:[~2024-10-09 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 6:37 Suraj Kandpal [this message]
2024-10-09 6:55 ` [PATCH] drm/i915/color: Use correct variable to load lut Ville Syrjälä
2024-10-09 8:46 ` Kandpal, Suraj
2024-10-09 8:50 ` Ville Syrjälä
2024-10-10 4:05 ` Kandpal, Suraj
2024-10-09 7:37 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-09 7:37 ` ✓ CI.checkpatch: " Patchwork
2024-10-09 7:38 ` ✓ CI.KUnit: " Patchwork
2024-10-09 7:50 ` ✓ CI.Build: " Patchwork
2024-10-09 7:52 ` ✓ CI.Hooks: " Patchwork
2024-10-09 7:53 ` ✗ CI.checksparse: warning " Patchwork
2024-10-09 8:20 ` ✓ CI.BAT: success " Patchwork
2024-10-09 12:39 ` ✗ CI.FULL: failure " Patchwork
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=20241009063753.1799234-2-suraj.kandpal@intel.com \
--to=suraj.kandpal@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@intel.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