Intel-GFX Archive mirror
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/9] drm/i915: Plane fb refactoring
Date: Mon,  6 May 2024 15:57:09 +0300	[thread overview]
Message-ID: <20240506125718.26001-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

A bit of cleanup/refactoring around plane fb stuff.
This is mainly prep work for a slightly bigger rework
of alignment handling.

Ville Syrjälä (9):
  drm/i915: Split gen2 vs. gen3 .max_stride()
  drm/i915: Clean up skl+ plane stride limits
  drm/i915: Drop 'uses_fence' parameter from intel_pin_fb_obj_dpt()
  drm/i915: Extract intel_plane_needs_physical()
  drm/i915: Polish types in fb calculations
  drm/i915: Constify 'fb' in during pinning
  drm/i915: Change intel_fbdev_fb_alloc() reuturn type
  drm/i915: Cleanup fbdev fb setup
  drm/i915: Rename the fb pinning functions to indicate the address
    space

 drivers/gpu/drm/i915/display/i9xx_plane.c     | 34 ++++---
 .../gpu/drm/i915/display/intel_atomic_plane.c |  8 ++
 .../gpu/drm/i915/display/intel_atomic_plane.h |  1 +
 drivers/gpu/drm/i915/display/intel_dpt.c      |  6 +-
 drivers/gpu/drm/i915/display/intel_dpt.h      |  6 +-
 drivers/gpu/drm/i915/display/intel_fb.c       | 27 +++---
 drivers/gpu/drm/i915/display/intel_fb_pin.c   | 73 +++++++-------
 drivers/gpu/drm/i915/display/intel_fb_pin.h   | 12 +--
 drivers/gpu/drm/i915/display/intel_fbdev.c    | 39 ++++----
 drivers/gpu/drm/i915/display/intel_fbdev_fb.c |  6 +-
 drivers/gpu/drm/i915/display/intel_fbdev_fb.h |  5 +-
 .../drm/i915/display/skl_universal_plane.c    | 94 ++++++++++---------
 drivers/gpu/drm/xe/display/xe_fb_pin.c        | 18 ++--
 drivers/gpu/drm/xe/display/xe_plane_initial.c |  4 +-
 14 files changed, 175 insertions(+), 158 deletions(-)

-- 
2.43.2


             reply	other threads:[~2024-05-06 12:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 12:57 Ville Syrjala [this message]
2024-05-06 12:57 ` [PATCH 1/9] drm/i915: Split gen2 vs. gen3 .max_stride() Ville Syrjala
2024-05-06 13:57   ` Jani Nikula
2024-05-06 12:57 ` [PATCH 2/9] drm/i915: Clean up skl+ plane stride limits Ville Syrjala
2024-05-06 14:03   ` Jani Nikula
2024-05-06 16:38     ` Ville Syrjälä
2024-05-07  9:02       ` Jani Nikula
2024-05-06 12:57 ` [PATCH 3/9] drm/i915: Drop 'uses_fence' parameter from intel_pin_fb_obj_dpt() Ville Syrjala
2024-05-06 14:04   ` Jani Nikula
2024-05-06 12:57 ` [PATCH 4/9] drm/i915: Extract intel_plane_needs_physical() Ville Syrjala
2024-05-06 14:05   ` Jani Nikula
2024-05-06 12:57 ` [PATCH 5/9] drm/i915: Polish types in fb calculations Ville Syrjala
2024-05-06 14:07   ` Jani Nikula
2024-05-06 12:57 ` [PATCH 6/9] drm/i915: Constify 'fb' in during pinning Ville Syrjala
2024-05-06 14:11   ` Jani Nikula
2024-05-06 12:57 ` [PATCH 7/9] drm/i915: Change intel_fbdev_fb_alloc() reuturn type Ville Syrjala
2024-05-06 14:16   ` Jani Nikula
2024-05-06 16:51     ` Ville Syrjälä
2024-05-06 18:19       ` Ville Syrjälä
2024-05-10 10:22   ` [PATCH v2 7/9] drm/i915: Change intel_fbdev_fb_alloc() return type Ville Syrjala
2024-05-10 11:30     ` Jani Nikula
2024-05-06 12:57 ` [PATCH 8/9] drm/i915: Cleanup fbdev fb setup Ville Syrjala
2024-05-10 10:22   ` [PATCH v2 " Ville Syrjala
2024-05-10 11:32     ` Jani Nikula
2024-05-06 12:57 ` [PATCH 9/9] drm/i915: Rename the fb pinning functions to indicate the address space Ville Syrjala
2024-05-10 11:35   ` Jani Nikula
2024-05-06 13:34 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Plane fb refactoring Patchwork
2024-05-06 13:42 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-06 18:13 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-05-10 12:37 ` ✓ Fi.CI.BAT: success for drm/i915: Plane fb refactoring (rev3) Patchwork
2024-05-10 16:55 ` [PATCH 0/9] drm/i915: Plane fb refactoring Ville Syrjälä
2024-05-11 19:00   ` Lucas De Marchi
2024-05-11  4:12 ` ✗ Fi.CI.IGT: failure for drm/i915: Plane fb refactoring (rev3) 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=20240506125718.26001-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).