From: Thomas Zimmermann <tzimmermann@suse.de>
To: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tvrtko.ursulin@linux.intel.com,
ville.syrjala@linux.intel.com, imre.deak@intel.com,
tejas.upadhyay@intel.com, javierm@redhat.com, airlied@gmail.com,
daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v5 0/7] drm/i915: Convert fbdev to DRM client
Date: Wed, 27 Sep 2023 12:26:45 +0200 [thread overview]
Message-ID: <20230927102808.18650-1-tzimmermann@suse.de> (raw)
Convert i915's fbdev code to struct drm_client. Replaces the current
ad-hoc integration. The conversion includes a number of cleanups. The
patchset also enables unloading of driver modules with in-kernel DRM
clients; a feature required by i915.
As with the other drivers' fbdev emulation, fbdev in i915 is now
an in-kernel DRM client that runs after the DRM device has been
registered. This allows to remove the asynchronous initialization.
i915 is the last driver with an fbdev emulation that is not build
upon struct drm_client. Once reviewed, the patches would ideally go
into drm-misc-next, so that the old fbdev helper code can be removed.
We can also attempt to add additional in-kernel clients. A DRM-based
dmesg log or a bootsplash are commonly mentioned. DRM can then switch
easily among the existing clients if/when required.
v5:
* style fixes (checkpatch)
v4:
<no changes>
v3:
* support module unloading (Jani, CI bot)
* as before, silently ignore devices without displays (CI bot)
v2:
* fix error handling (Jani)
* fix non-fbdev builds
* various minor fixes and cleanups
Thomas Zimmermann (7):
drm/i915: Unregister in-kernel clients
drm/client: Do not acquire module reference
drm/client: Export drm_client_dev_unregister()
drm/i915: Move fbdev functions
drm/i915: Initialize fbdev DRM client with callback functions
drm/i915: Implement fbdev client callbacks
drm/i915: Implement fbdev emulation as in-kernel client
drivers/gpu/drm/drm_client.c | 25 +-
drivers/gpu/drm/i915/display/intel_display.c | 1 -
.../drm/i915/display/intel_display_driver.c | 19 --
drivers/gpu/drm/i915/display/intel_fbdev.c | 250 ++++++++++--------
drivers/gpu/drm/i915/display/intel_fbdev.h | 29 +-
drivers/gpu/drm/i915/i915_driver.c | 27 +-
6 files changed, 156 insertions(+), 195 deletions(-)
--
2.42.0
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Zimmermann <tzimmermann@suse.de>
To: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, tvrtko.ursulin@linux.intel.com,
ville.syrjala@linux.intel.com, imre.deak@intel.com,
tejas.upadhyay@intel.com, javierm@redhat.com, airlied@gmail.com,
daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: [PATCH v5 0/7] drm/i915: Convert fbdev to DRM client
Date: Wed, 27 Sep 2023 12:26:45 +0200 [thread overview]
Message-ID: <20230927102808.18650-1-tzimmermann@suse.de> (raw)
Convert i915's fbdev code to struct drm_client. Replaces the current
ad-hoc integration. The conversion includes a number of cleanups. The
patchset also enables unloading of driver modules with in-kernel DRM
clients; a feature required by i915.
As with the other drivers' fbdev emulation, fbdev in i915 is now
an in-kernel DRM client that runs after the DRM device has been
registered. This allows to remove the asynchronous initialization.
i915 is the last driver with an fbdev emulation that is not build
upon struct drm_client. Once reviewed, the patches would ideally go
into drm-misc-next, so that the old fbdev helper code can be removed.
We can also attempt to add additional in-kernel clients. A DRM-based
dmesg log or a bootsplash are commonly mentioned. DRM can then switch
easily among the existing clients if/when required.
v5:
* style fixes (checkpatch)
v4:
<no changes>
v3:
* support module unloading (Jani, CI bot)
* as before, silently ignore devices without displays (CI bot)
v2:
* fix error handling (Jani)
* fix non-fbdev builds
* various minor fixes and cleanups
Thomas Zimmermann (7):
drm/i915: Unregister in-kernel clients
drm/client: Do not acquire module reference
drm/client: Export drm_client_dev_unregister()
drm/i915: Move fbdev functions
drm/i915: Initialize fbdev DRM client with callback functions
drm/i915: Implement fbdev client callbacks
drm/i915: Implement fbdev emulation as in-kernel client
drivers/gpu/drm/drm_client.c | 25 +-
drivers/gpu/drm/i915/display/intel_display.c | 1 -
.../drm/i915/display/intel_display_driver.c | 19 --
drivers/gpu/drm/i915/display/intel_fbdev.c | 250 ++++++++++--------
drivers/gpu/drm/i915/display/intel_fbdev.h | 29 +-
drivers/gpu/drm/i915/i915_driver.c | 27 +-
6 files changed, 156 insertions(+), 195 deletions(-)
--
2.42.0
next reply other threads:[~2023-09-27 10:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 10:26 Thomas Zimmermann [this message]
2023-09-27 10:26 ` [PATCH v5 0/7] drm/i915: Convert fbdev to DRM client Thomas Zimmermann
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 1/7] drm/i915: Unregister in-kernel clients Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-10-25 7:28 ` [Intel-gfx] " Hogander, Jouni
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 2/7] drm/client: Do not acquire module reference Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-11-01 12:01 ` [Intel-gfx] " Javier Martinez Canillas
2023-11-01 12:01 ` Javier Martinez Canillas
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 3/7] drm/client: Export drm_client_dev_unregister() Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 4/7] drm/i915: Move fbdev functions Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-10-25 7:49 ` [Intel-gfx] " Hogander, Jouni
2023-10-25 7:49 ` Hogander, Jouni
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 5/7] drm/i915: Initialize fbdev DRM client with callback functions Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-10-25 8:36 ` [Intel-gfx] " Hogander, Jouni
2023-11-01 8:11 ` Thomas Zimmermann
2023-11-01 9:10 ` Hogander, Jouni
2023-11-01 9:32 ` Thomas Zimmermann
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 6/7] drm/i915: Implement fbdev client callbacks Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-10-25 9:36 ` [Intel-gfx] " Hogander, Jouni
2023-11-01 8:26 ` Thomas Zimmermann
2023-09-27 10:26 ` [Intel-gfx] [PATCH v5 7/7] drm/i915: Implement fbdev emulation as in-kernel client Thomas Zimmermann
2023-09-27 10:26 ` Thomas Zimmermann
2023-10-25 11:36 ` [Intel-gfx] " Hogander, Jouni
2023-10-25 11:36 ` Hogander, Jouni
2023-11-01 8:33 ` [Intel-gfx] " Thomas Zimmermann
2023-11-01 8:33 ` Thomas Zimmermann
2023-11-01 9:25 ` [Intel-gfx] " Ville Syrjälä
2023-11-01 9:25 ` Ville Syrjälä
2023-11-01 9:35 ` [Intel-gfx] " Thomas Zimmermann
2023-11-01 9:35 ` Thomas Zimmermann
2023-09-27 18:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Convert fbdev to DRM client (rev5) Patchwork
2023-09-27 19:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-28 7:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20230927102808.18650-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=javierm@redhat.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tejas.upadhyay@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.