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,
airlied@gmail.com, daniel@ffwll.ch,
ville.syrjala@linux.intel.com, imre.deak@intel.com,
tejas.upadhyay@intel.com, javierm@redhat.com
Cc: intel-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: [PATCH 0/4] drm/i915: Convert fbdev to DRM client
Date: Tue, 28 Mar 2023 13:14:18 +0200 [thread overview]
Message-ID: <20230328111422.23986-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.
As with most other driver's fbdev emulation, fbdev in i915 is now
just another DRM client that runs after the DRM device has been
registered. This allows to remove the asynchronous initialization,
hopefully.
Once all drivers' fbdev emulation has been converted to struct drm_client,
we can 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.
Tested on Intel HD 530 hardware.
Thomas Zimmermann (4):
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/i915/display/intel_display.c | 31 ---
drivers/gpu/drm/i915/display/intel_fbdev.c | 254 ++++++++++---------
drivers/gpu/drm/i915/display/intel_fbdev.h | 29 +--
drivers/gpu/drm/i915/i915_driver.c | 24 +-
4 files changed, 143 insertions(+), 195 deletions(-)
base-commit: 6e5f96153989e454041848f66a5227be9bd0bbc3
--
2.40.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,
airlied@gmail.com, daniel@ffwll.ch,
ville.syrjala@linux.intel.com, imre.deak@intel.com,
tejas.upadhyay@intel.com, javierm@redhat.com
Cc: intel-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 0/4] drm/i915: Convert fbdev to DRM client
Date: Tue, 28 Mar 2023 13:14:18 +0200 [thread overview]
Message-ID: <20230328111422.23986-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.
As with most other driver's fbdev emulation, fbdev in i915 is now
just another DRM client that runs after the DRM device has been
registered. This allows to remove the asynchronous initialization,
hopefully.
Once all drivers' fbdev emulation has been converted to struct drm_client,
we can 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.
Tested on Intel HD 530 hardware.
Thomas Zimmermann (4):
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/i915/display/intel_display.c | 31 ---
drivers/gpu/drm/i915/display/intel_fbdev.c | 254 ++++++++++---------
drivers/gpu/drm/i915/display/intel_fbdev.h | 29 +--
drivers/gpu/drm/i915/i915_driver.c | 24 +-
4 files changed, 143 insertions(+), 195 deletions(-)
base-commit: 6e5f96153989e454041848f66a5227be9bd0bbc3
--
2.40.0
next reply other threads:[~2023-03-28 11:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 11:14 Thomas Zimmermann [this message]
2023-03-28 11:14 ` [Intel-gfx] [PATCH 0/4] drm/i915: Convert fbdev to DRM client Thomas Zimmermann
2023-03-28 11:14 ` [PATCH 1/4] drm/i915: Move fbdev functions Thomas Zimmermann
2023-03-28 11:14 ` [Intel-gfx] " Thomas Zimmermann
2023-03-28 11:14 ` [PATCH 2/4] drm/i915: Initialize fbdev DRM client with callback functions Thomas Zimmermann
2023-03-28 11:14 ` [Intel-gfx] " Thomas Zimmermann
2023-03-28 15:20 ` Jani Nikula
2023-03-28 15:20 ` [Intel-gfx] " Jani Nikula
2023-03-29 15:03 ` Sam Ravnborg
2023-03-29 15:03 ` [Intel-gfx] " Sam Ravnborg
2023-03-28 11:14 ` [PATCH 3/4] drm/i915: Implement fbdev client callbacks Thomas Zimmermann
2023-03-28 11:14 ` [Intel-gfx] " Thomas Zimmermann
2023-03-28 11:14 ` [PATCH 4/4] drm/i915: Implement fbdev emulation as in-kernel client Thomas Zimmermann
2023-03-28 11:14 ` [Intel-gfx] " Thomas Zimmermann
2023-03-28 15:31 ` Jani Nikula
2023-03-28 15:31 ` [Intel-gfx] " Jani Nikula
2023-04-03 12:50 ` Thomas Zimmermann
2023-04-03 12:50 ` [Intel-gfx] " Thomas Zimmermann
2023-07-11 13:09 ` Thomas Zimmermann
2023-07-11 13:09 ` [Intel-gfx] " Thomas Zimmermann
2023-03-28 20:40 ` kernel test robot
2023-03-28 20:40 ` kernel test robot
2023-03-28 21:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Convert fbdev to DRM client Patchwork
2023-03-28 22:07 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=20230328111422.23986-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.