Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
	joonas.lahtinen@linux.intel.com, tursulin@ursulin.net,
	lucas.demarchi@intel.com, thomas.hellstrom@linux.intel.com,
	simona@ffwll.ch, airlied@gmail.com, mripard@kernel.org,
	maarten.lankhorst@linux.intel.com, jfalempe@redhat.com,
	javierm@redhat.com
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 00/12] drm/{i915,xe}: Convert to DRM client setup
Date: Tue, 11 Feb 2025 08:17:23 +0100	[thread overview]
Message-ID: <de8325a9-49b2-48ec-ba56-4349140564b1@suse.de> (raw)
In-Reply-To: <20241212170913.185939-1-tzimmermann@suse.de>

ping for a review

Am 12.12.24 um 18:08 schrieb Thomas Zimmermann:
> i915 and xe are the last remaining drivers that still implement their
> own fbdev client. All other clients have been mass converted to DRM's
> client setup in in the series at [1]. As Intel drivers require more
> effort than others, their changes have been moved into this separate
> series.
>
> With DRM's client setup, DRM picks the in-kernel client from the
> kernel's config and parameters. Besides fbdev there's also drm_log
> available. For fbdev support, the driver only has to implement struct
> drm_driver.fbdev_probe, a callback that allocates a compatible
> framebuffer.
>
> At first, some details of the Intel implementation have to be rebuild
> for the generic client and fbdev handling. Patches 1 to 6 do that.
> Hotplugging and suspend/resume are then hidden behind callbacks. Some
> Intel-specifics in the restore and suspend code get their own hooks.
>
> Patches 7 to 9 prepare Intel's fbdev implementation ot get things
> out of the way.
>
> Patch 10 converts i915 and xe to DRM's client setup. Patches 11 and
> 12 clean up the remaining code.
>
> Tested with i915 and xe hardware.
>
> [1] https://patchwork.freedesktop.org/series/137391/
>
> Thomas Zimmermann (12):
>    drm/{i915,xe}: Suspend/resume fbdev emulation via client interfaces
>    drm/client: Add client-hotplug helper
>    drm/client: Send pending hotplug events after resume
>    drm/i915/display: Remove fbdev suspend and hotplug tracking
>    drm/i915/display: fbdev: Move custom restore code to new callback
>    drm/i915/display: fbdev: Move custom suspend code to new callback
>    drm/i915/display: Remove preferred_bpp from struct intel_fbdev
>    drm/i915/display: Remove struct drm_fb_helper from struct intel_fbdev
>    drm/i915/display: Move fbdev code around
>    drm/{i915,xe}: Run DRM default client setup
>    drm/i915/display: Remove compile guard around fbdev debugfs output
>    drm/fb-helper: Remove struct drm_fb_helper.fb_probe
>
>   drivers/gpu/drm/drm_client_event.c            |  41 ++-
>   drivers/gpu/drm/drm_fb_helper.c               |  20 +-
>   .../gpu/drm/i915/display/intel_display_core.h |   1 -
>   .../drm/i915/display/intel_display_debugfs.c  |   2 -
>   drivers/gpu/drm/i915/display/intel_fbdev.c    | 338 ++++--------------
>   drivers/gpu/drm/i915/display/intel_fbdev.h    |  17 +-
>   drivers/gpu/drm/i915/i915_driver.c            |  10 +-
>   drivers/gpu/drm/xe/display/xe_display.c       |  12 +-
>   include/drm/drm_client.h                      |   8 +
>   include/drm/drm_fb_helper.h                   |  44 ++-
>   10 files changed, 176 insertions(+), 317 deletions(-)
>
>
> base-commit: 7bbcd7df9387f0d9004f997df33f7a9472d9c080

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  parent reply	other threads:[~2025-02-11 14:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 17:08 [PATCH 00/12] drm/{i915,xe}: Convert to DRM client setup Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 01/12] drm/{i915, xe}: Suspend/resume fbdev emulation via client interfaces Thomas Zimmermann
2025-02-11 20:55   ` Rodrigo Vivi
2025-02-12  7:43     ` Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 02/12] drm/client: Add client-hotplug helper Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 03/12] drm/client: Send pending hotplug events after resume Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 04/12] drm/i915/display: Remove fbdev suspend and hotplug tracking Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 05/12] drm/i915/display: fbdev: Move custom restore code to new callback Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 06/12] drm/i915/display: fbdev: Move custom suspend " Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 07/12] drm/i915/display: Remove preferred_bpp from struct intel_fbdev Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 08/12] drm/i915/display: Remove struct drm_fb_helper " Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 09/12] drm/i915/display: Move fbdev code around Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 10/12] drm/{i915,xe}: Run DRM default client setup Thomas Zimmermann
2025-01-07 12:10   ` Jocelyn Falempe
2025-01-07 14:42     ` Thomas Zimmermann
2025-01-07 15:18       ` Jocelyn Falempe
2024-12-12 17:08 ` [PATCH 11/12] drm/i915/display: Remove compile guard around fbdev debugfs output Thomas Zimmermann
2024-12-12 17:08 ` [PATCH 12/12] drm/fb-helper: Remove struct drm_fb_helper.fb_probe Thomas Zimmermann
2024-12-12 17:53 ` ✓ CI.Patch_applied: success for drm/{i915,xe}: Convert to DRM client setup Patchwork
2024-12-12 17:53 ` ✓ CI.checkpatch: " Patchwork
2024-12-12 17:55 ` ✓ CI.KUnit: " Patchwork
2024-12-12 18:13 ` ✓ CI.Build: " Patchwork
2024-12-12 18:15 ` ✓ CI.Hooks: " Patchwork
2024-12-12 18:17 ` ✗ CI.checksparse: warning " Patchwork
2024-12-12 18:47 ` ✓ Xe.CI.BAT: success " Patchwork
2024-12-12 23:18 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-07  9:07 ` [PATCH 00/12] " Thomas Zimmermann
2025-02-11  7:17 ` Thomas Zimmermann [this message]
2025-02-12  7:28   ` Maarten Lankhorst
2025-02-12  7:42     ` Thomas Zimmermann
2025-02-28  8:49     ` Thomas Zimmermann
2025-03-04 19:40       ` Maarten Lankhorst
2025-03-04 21:38         ` Jocelyn Falempe

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=de8325a9-49b2-48ec-ba56-4349140564b1@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=javierm@redhat.com \
    --cc=jfalempe@redhat.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    /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