From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/9] drm/i915: Display info cleanup
Date: Thu, 23 Jun 2022 21:27:47 +0300 [thread overview]
Message-ID: <87pmizmdzw.fsf@intel.com> (raw)
In-Reply-To: <20220623130900.26078-1-ville.syrjala@linux.intel.com>
On Thu, 23 Jun 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Collect more stuff under INTEL_INFO->display, and clean up
> some messy stuff in the related register macros.
Makes me wonder if we should have DISPLAY_INFO(i915) macro that returns
a pointer to the display sub-struct.
Anyway, the series is
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Ville Syrjälä (9):
> drm/i915: Move dbuf details to INTEL_INFO->display
> drm/i195: Move pipe_offsets[] & co. to INTEL_INFO->display
> drm/i915: Move display_mmio_offset under INTEL_INFO->display
> drm/i915: Make pipe_offsets[] & co. u32
> drm/i915: s/_CURSOR2/_MMIO_CURSOR2//
> drm/i915: Use _MMIO_TRANS2() where appropriate
> drm/i915: Use _MMIO_PIPE2() where appropriate
> drm/i915: Get rid of XE_LPD_CURSOR_OFFSETS
> drm/i915: Move the color stuff under INTEL_INFO->display
>
> drivers/gpu/drm/i915/display/intel_color.c | 28 ++---
> drivers/gpu/drm/i915/display/intel_display.h | 2 +-
> .../drm/i915/display/intel_display_power.c | 2 +-
> drivers/gpu/drm/i915/i915_pci.c | 112 +++++++++---------
> drivers/gpu/drm/i915/i915_reg.h | 47 ++++----
> drivers/gpu/drm/i915/intel_device_info.h | 39 +++---
> drivers/gpu/drm/i915/intel_pm.c | 8 +-
> 7 files changed, 117 insertions(+), 121 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-06-23 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 13:08 [Intel-gfx] [PATCH 0/9] drm/i915: Display info cleanup Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 1/9] drm/i915: Move dbuf details to INTEL_INFO->display Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 2/9] drm/i195: Move pipe_offsets[] & co. " Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 3/9] drm/i915: Move display_mmio_offset under INTEL_INFO->display Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 4/9] drm/i915: Make pipe_offsets[] & co. u32 Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 5/9] drm/i915: s/_CURSOR2/_MMIO_CURSOR2// Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 6/9] drm/i915: Use _MMIO_TRANS2() where appropriate Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 7/9] drm/i915: Use _MMIO_PIPE2() " Ville Syrjala
2022-06-23 13:08 ` [Intel-gfx] [PATCH 8/9] drm/i915: Get rid of XE_LPD_CURSOR_OFFSETS Ville Syrjala
2022-06-23 13:09 ` [Intel-gfx] [PATCH 9/9] drm/i915: Move the color stuff under INTEL_INFO->display Ville Syrjala
2022-06-23 14:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Display info cleanup Patchwork
2022-06-23 14:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-23 14:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-06-23 18:27 ` Jani Nikula [this message]
2022-06-23 18:29 ` [Intel-gfx] [PATCH 0/9] " Jani Nikula
2022-06-27 14:29 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=87pmizmdzw.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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