From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@redhat.com, daniel@ffwll.ch, sam@ravnborg.org,
emil.l.velikov@gmail.com, kraxel@redhat.com,
yc_chen@aspeedtech.com
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH v2 0/9] drm/ast: Convert to managed initialization
Date: Thu, 30 Jul 2020 15:51:57 +0200 [thread overview]
Message-ID: <20200730135206.30239-1-tzimmermann@suse.de> (raw)
This is the next patchset for converting ast to managed initialization.
For v2 of the series, I moved the I2C patches into a separate patchset.
This resolves a mid-series problem wrt to releasing I2C. The rest of
the patches are unchanged (except for a rebase).
Patches #1 to #6 address modesetting and device structures. All are
being embedded into struct ast_private. With struct ast_private being
a subclass of struct drm_device, patch #6 switches ast to DRM's managed-
allocation helpers.
Patches #7 and #8 address firmware memory that ast allocates
internally.
Finally, patch #9 removes ast's destroy function in favor of managed
release helpers.
Tested on AST 2100 HW.
v2:
* removed I2C patches from series
Thomas Zimmermann (9):
drm/ast: Embed CRTC and connector in struct ast_private
drm/ast: Separate DRM driver from PCI code
drm/ast: Replace driver load/unload functions with device
create/destroy
drm/ast: Replace struct_drm_device.dev_private with to_ast_private()
drm/ast: Don't use ast->dev if dev is available
drm/ast: Embed struct drm_device in struct ast_private
drm/ast: Managed release of ast firmware
drm/ast: Manage release of firmware backup memory
drm/ast: Managed device release
drivers/gpu/drm/ast/ast_cursor.c | 8 ++--
drivers/gpu/drm/ast/ast_dp501.c | 23 +++++----
drivers/gpu/drm/ast/ast_drv.c | 82 ++++++++++++++------------------
drivers/gpu/drm/ast/ast_drv.h | 43 +++++++++--------
drivers/gpu/drm/ast/ast_main.c | 74 ++++++++++++++--------------
drivers/gpu/drm/ast/ast_mm.c | 2 +-
drivers/gpu/drm/ast/ast_mode.c | 40 ++++------------
drivers/gpu/drm/ast/ast_post.c | 6 +--
8 files changed, 130 insertions(+), 148 deletions(-)
--
2.27.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-07-30 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 13:51 Thomas Zimmermann [this message]
2020-07-30 13:51 ` [PATCH v2 1/9] drm/ast: Embed CRTC and connector in struct ast_private Thomas Zimmermann
2020-07-30 13:51 ` [PATCH v2 2/9] drm/ast: Separate DRM driver from PCI code Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 3/9] drm/ast: Replace driver load/unload functions with device create/destroy Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 4/9] drm/ast: Replace struct_drm_device.dev_private with to_ast_private() Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 5/9] drm/ast: Don't use ast->dev if dev is available Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 6/9] drm/ast: Embed struct drm_device in struct ast_private Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 7/9] drm/ast: Managed release of ast firmware Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 8/9] drm/ast: Manage release of firmware backup memory Thomas Zimmermann
2020-07-30 13:52 ` [PATCH v2 9/9] drm/ast: Managed device release Thomas Zimmermann
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=20200730135206.30239-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=kraxel@redhat.com \
--cc=sam@ravnborg.org \
--cc=yc_chen@aspeedtech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox