Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 0/6] drm/i915: dpll, ddi, crc, psr etc conversions to struct intel_display
Date: Fri, 28 Mar 2025 16:01:28 +0200	[thread overview]
Message-ID: <87jz8945l3.fsf@intel.com> (raw)
In-Reply-To: <Z-aAvijGRTTANm0_@intel.com>

On Fri, 28 Mar 2025, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Mar 25, 2025 at 02:36:32PM +0200, Jani Nikula wrote:
>> We're getting there!
>> 
>> Jani Nikula (6):
>>   drm/i915/dpll: convert intel_dpll.[ch] to struct intel_display
>>   drm/i915/ddi: convert intel_ddi.c to struct intel_display
>>   drm/i915/crc: convert intel_pipe_crc.c to struct intel_display
>>   drm/i915/psr: further conversions to struct intel_display
>>   drm/i915/wa: convert intel_display_wa.[ch] to struct intel_display
>>   drm/i915/display: drop some unnecessary intel_de_* compatibility
>>     wrappers
>
> Series is
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Thanks, pushed to din.

BR,
Jani.

>
>> 
>>  drivers/gpu/drm/i915/display/intel_ddi.c      | 904 +++++++++---------
>>  drivers/gpu/drm/i915/display/intel_de.h       |  16 +-
>>  drivers/gpu/drm/i915/display/intel_display.c  |   4 +-
>>  .../drm/i915/display/intel_display_driver.c   |   7 +-
>>  .../gpu/drm/i915/display/intel_display_wa.c   |  30 +-
>>  .../gpu/drm/i915/display/intel_display_wa.h   |  11 +-
>>  drivers/gpu/drm/i915/display/intel_dpll.c     | 312 +++---
>>  drivers/gpu/drm/i915/display/intel_dpll.h     |  13 +-
>>  drivers/gpu/drm/i915/display/intel_fbc.c      |   2 +-
>>  drivers/gpu/drm/i915/display/intel_pipe_crc.c | 137 ++-
>>  drivers/gpu/drm/i915/display/intel_pps.c      |   5 +-
>>  drivers/gpu/drm/i915/display/intel_psr.c      |  85 +-
>>  drivers/gpu/drm/xe/display/xe_display_wa.c    |   6 +-
>>  13 files changed, 729 insertions(+), 803 deletions(-)
>> 
>> -- 
>> 2.39.5

-- 
Jani Nikula, Intel

      reply	other threads:[~2025-03-28 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 12:36 [PATCH 0/6] drm/i915: dpll, ddi, crc, psr etc conversions to struct intel_display Jani Nikula
2025-03-25 12:36 ` [PATCH 1/6] drm/i915/dpll: convert intel_dpll.[ch] " Jani Nikula
2025-03-25 12:36 ` [PATCH 2/6] drm/i915/ddi: convert intel_ddi.c " Jani Nikula
2025-03-25 12:36 ` [PATCH 3/6] drm/i915/crc: convert intel_pipe_crc.c " Jani Nikula
2025-03-25 12:36 ` [PATCH 4/6] drm/i915/psr: further conversions " Jani Nikula
2025-03-25 12:36 ` [PATCH 5/6] drm/i915/wa: convert intel_display_wa.[ch] " Jani Nikula
2025-03-25 12:36 ` [PATCH 6/6] drm/i915/display: drop some unnecessary intel_de_* compatibility wrappers Jani Nikula
2025-03-25 18:54 ` ✗ Fi.CI.SPARSE: warning for drm/i915: dpll, ddi, crc, psr etc conversions to struct intel_display Patchwork
2025-03-25 19:16 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-25 21:47 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-28 10:58 ` [PATCH 0/6] " Ville Syrjälä
2025-03-28 14:01   ` Jani Nikula [this message]

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=87jz8945l3.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@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