From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/7] drm/i915/regs: split display regs by function
Date: Thu, 16 Mar 2023 17:38:48 +0100 [thread overview]
Message-ID: <72de05c2-68ad-72aa-23a2-4ef220f51a12@linux.intel.com> (raw)
In-Reply-To: <cover.1678973282.git.jani.nikula@intel.com>
On 3/16/2023 2:29 PM, Jani Nikula wrote:
> Shave off 1.2k lines from i915_reg.h.
>
> Jani Nikula (7):
> drm/i915/pps: split out PPS regs to a separate file
> drm/i915/tv: split out TV regs to a separate file
> drm/i915/aux: split out DP AUX regs to a separate file
> drm/i915/fdi: split out FDI regs to a separate file
> drm/i915/wm: split out SKL+ watermark regs to a separate file
> drm/i915/psr: split out PSR regs to a separate file
> drm/i915/dsb: split out DSB regs to a separate file
Some of the files are new to me but haven't seen any functional changes
so I am confident say the series is
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
Thanks,
Nirmoy
> drivers/gpu/drm/i915/display/intel_crt.c | 1 +
> .../drm/i915/display/intel_display_debugfs.c | 1 +
> .../drm/i915/display/intel_display_power.c | 2 +
> .../i915/display/intel_display_power_well.c | 1 +
> drivers/gpu/drm/i915/display/intel_dp_aux.c | 1 +
> .../gpu/drm/i915/display/intel_dp_aux_regs.h | 84 ++
> drivers/gpu/drm/i915/display/intel_dsb.c | 1 +
> drivers/gpu/drm/i915/display/intel_dsb_regs.h | 67 +
> drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 1 +
> drivers/gpu/drm/i915/display/intel_fdi.c | 1 +
> drivers/gpu/drm/i915/display/intel_fdi_regs.h | 151 ++
> drivers/gpu/drm/i915/display/intel_lvds.c | 1 +
> .../gpu/drm/i915/display/intel_pch_display.c | 1 +
> drivers/gpu/drm/i915/display/intel_pps.c | 1 +
> drivers/gpu/drm/i915/display/intel_pps_regs.h | 78 ++
> drivers/gpu/drm/i915/display/intel_psr.c | 1 +
> drivers/gpu/drm/i915/display/intel_psr_regs.h | 260 ++++
> drivers/gpu/drm/i915/display/intel_tv.c | 3 +-
> drivers/gpu/drm/i915/display/intel_tv_regs.h | 490 +++++++
> drivers/gpu/drm/i915/display/skl_watermark.c | 1 +
> .../gpu/drm/i915/display/skl_watermark_regs.h | 165 +++
> drivers/gpu/drm/i915/gvt/edid.c | 1 +
> drivers/gpu/drm/i915/gvt/handlers.c | 5 +
> drivers/gpu/drm/i915/i915_irq.c | 2 +
> drivers/gpu/drm/i915/i915_reg.h | 1219 -----------------
> drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 4 +
> 26 files changed, 1323 insertions(+), 1220 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/display/intel_dp_aux_regs.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_dsb_regs.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_fdi_regs.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_pps_regs.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_psr_regs.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_tv_regs.h
> create mode 100644 drivers/gpu/drm/i915/display/skl_watermark_regs.h
>
next prev parent reply other threads:[~2023-03-16 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 13:29 [Intel-gfx] [PATCH 0/7] drm/i915/regs: split display regs by function Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 1/7] drm/i915/pps: split out PPS regs to a separate file Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 2/7] drm/i915/tv: split out TV " Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 3/7] drm/i915/aux: split out DP AUX " Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 4/7] drm/i915/fdi: split out FDI " Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 5/7] drm/i915/wm: split out SKL+ watermark " Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 6/7] drm/i915/psr: split out PSR " Jani Nikula
2023-03-16 13:29 ` [Intel-gfx] [PATCH 7/7] drm/i915/dsb: split out DSB " Jani Nikula
2023-03-16 16:38 ` Das, Nirmoy [this message]
2023-03-30 16:34 ` [Intel-gfx] [PATCH 0/7] drm/i915/regs: split display regs by function Jani Nikula
2023-03-16 23:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-17 2:19 ` [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=72de05c2-68ad-72aa-23a2-4ef220f51a12@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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