From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/6] drm/i915/color: cleanups and refactoring
Date: Thu, 17 Aug 2023 18:53:02 +0300 [thread overview]
Message-ID: <cover.1692287501.git.jani.nikula@intel.com> (raw)
Split out register macros to a separate file, and move more color
register access to intel_color.c.
Jani Nikula (6):
drm/i915/regs: split out intel_color_regs.h
drm/i915/color: move CHV CGM pipe mode read to intel_color
drm/i915: move HSW+ gamma mode read to intel_color
drm/i915: move ILK+ CSC mode read to intel_color
drm/i915/color: move SKL+ gamma and CSC enable read to intel_color
drm/i915/color: move pre-SKL gamma and CSC enable read to intel_color
drivers/gpu/drm/i915/display/hsw_ips.c | 1 +
drivers/gpu/drm/i915/display/intel_color.c | 97 ++++++
.../gpu/drm/i915/display/intel_color_regs.h | 286 ++++++++++++++++++
drivers/gpu/drm/i915/display/intel_display.c | 45 ---
drivers/gpu/drm/i915/display/intel_overlay.c | 1 +
drivers/gpu/drm/i915/i915_reg.h | 274 -----------------
drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 1 +
7 files changed, 386 insertions(+), 319 deletions(-)
create mode 100644 drivers/gpu/drm/i915/display/intel_color_regs.h
--
2.39.2
next reply other threads:[~2023-08-17 15:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 15:53 Jani Nikula [this message]
2023-08-17 15:53 ` [Intel-gfx] [PATCH 1/6] drm/i915/regs: split out intel_color_regs.h Jani Nikula
2023-08-17 15:53 ` [Intel-gfx] [PATCH 2/6] drm/i915/color: move CHV CGM pipe mode read to intel_color Jani Nikula
2023-08-17 15:53 ` [Intel-gfx] [PATCH 3/6] drm/i915: move HSW+ gamma " Jani Nikula
2023-08-17 15:53 ` [Intel-gfx] [PATCH 4/6] drm/i915: move ILK+ CSC " Jani Nikula
2023-08-17 15:53 ` [Intel-gfx] [PATCH 5/6] drm/i915/color: move SKL+ gamma and CSC enable " Jani Nikula
2023-08-17 15:53 ` [Intel-gfx] [PATCH 6/6] drm/i915/color: move pre-SKL " Jani Nikula
2023-08-18 1:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/color: cleanups and refactoring Patchwork
2023-08-18 1:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-18 1:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-19 1:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-24 14:23 ` [Intel-gfx] [PATCH 0/6] " Hogander, Jouni
2023-08-24 20:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/color: cleanups and refactoring (rev2) Patchwork
2023-08-24 20:33 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-24 20:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-25 10:05 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=cover.1692287501.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.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