From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@redhat.com, daniel@ffwll.ch, kraxel@redhat.com,
sam@ravnborg.org, emil.velikov@collabora.com, cogarre@gmail.com
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/5] drm/mgag200: Embed DRM device in struct mga_device
Date: Tue, 5 May 2020 11:56:44 +0200 [thread overview]
Message-ID: <20200505095649.25814-1-tzimmermann@suse.de> (raw)
After receiving reviews on the conversion of mgag200 to atomic mode
setting, I thought it would make sense to embed the DRM device in
struct mga_device first. Several comments in the atomic-conversion
reviews refer to that.
Patches 1 to 3 do some cleanups and preparation work. Patch 4 changes
the the init functions to allocate struct mga_device before struct
drm_device. Patch 5 does the conversion.
I did not switch over struct mga_device to the new managed release
code. I found that this justifies another round of cleanup patches,
which I did not want to put into this patchset.
The patches were tested on mgag200 hardware.
Thomas Zimmermann (5):
drm/mgag200: Convert struct drm_device to struct mga_device with macro
drm/mgag200: Integrate init function into load function
drm/mgag200: Remove several references to struct mga_device.dev
drm/mgag200: Init and finalize devices in mgag200_device_{init,fini}()
drm/mgag200: Embed DRM device instance in struct mga_device
drivers/gpu/drm/mgag200/mgag200_cursor.c | 10 +-
drivers/gpu/drm/mgag200/mgag200_drv.c | 29 +++---
drivers/gpu/drm/mgag200/mgag200_drv.h | 8 +-
drivers/gpu/drm/mgag200/mgag200_i2c.c | 10 +-
drivers/gpu/drm/mgag200/mgag200_main.c | 114 +++++++++++------------
drivers/gpu/drm/mgag200/mgag200_mode.c | 35 +++----
drivers/gpu/drm/mgag200/mgag200_ttm.c | 4 +-
7 files changed, 101 insertions(+), 109 deletions(-)
--
2.26.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-05-05 9:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 9:56 Thomas Zimmermann [this message]
2020-05-05 9:56 ` [PATCH 1/5] drm/mgag200: Convert struct drm_device to struct mga_device with macro Thomas Zimmermann
2020-05-05 13:51 ` Daniel Vetter
2020-05-05 16:36 ` Sam Ravnborg
2020-05-06 11:06 ` Daniel Vetter
2020-05-05 9:56 ` [PATCH 2/5] drm/mgag200: Integrate init function into load function Thomas Zimmermann
2020-05-05 14:05 ` Daniel Vetter
2020-05-05 16:40 ` Sam Ravnborg
2020-05-05 9:56 ` [PATCH 3/5] drm/mgag200: Remove several references to struct mga_device.dev Thomas Zimmermann
2020-05-05 14:09 ` Daniel Vetter
2020-05-06 7:48 ` Thomas Zimmermann
2020-05-06 9:22 ` Daniel Vetter
2020-05-05 16:43 ` Sam Ravnborg
2020-05-05 9:56 ` [PATCH 4/5] drm/mgag200: Init and finalize devices in mgag200_device_{init, fini}() Thomas Zimmermann
2020-05-05 14:14 ` [PATCH 4/5] drm/mgag200: Init and finalize devices in mgag200_device_{init,fini}() Daniel Vetter
2020-05-06 7:57 ` Thomas Zimmermann
2020-05-05 16:49 ` Sam Ravnborg
2020-05-06 7:59 ` Thomas Zimmermann
2020-05-05 9:56 ` [PATCH 5/5] drm/mgag200: Embed DRM device instance in struct mga_device Thomas Zimmermann
2020-05-05 14:18 ` Daniel Vetter
2020-05-05 16:30 ` [PATCH 0/5] drm/mgag200: Embed DRM device " Sam Ravnborg
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=20200505095649.25814-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=cogarre@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.velikov@collabora.com \
--cc=kraxel@redhat.com \
--cc=sam@ravnborg.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