From: Danilo Krummrich <dakr@redhat.com>
To: daniel@ffwll.ch, airlied@linux.ie, tzimmermann@suse.de,
mripard@kernel.org, liviu.dudau@arm.com, brian.starkey@arm.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Danilo Krummrich <dakr@redhat.com>
Subject: [PATCH drm-misc-next v2 0/9] drm/arm/malidp: use drm managed resources
Date: Sat, 1 Oct 2022 18:39:37 +0200 [thread overview]
Message-ID: <20221001163946.534067-1-dakr@redhat.com> (raw)
Hi,
This patch series converts the driver to use drm managed resources to prevent
potential use-after-free issues on driver unbind/rebind and to get rid of the
usage of deprecated APIs.
Changes in v2:
- While protecting critical sections with drm_dev_{enter,exit} I forgot to
handle alternate return paths within the read-side critical sections, hence
fix them.
- Add a patch to remove explicit calls to drm_mode_config_cleanup() and switch
to drmm_mode_config_init() explicitly.
Danilo Krummrich (9):
drm/arm/malidp: use drmm_* to allocate driver structures
drm/arm/malidp: replace drm->dev_private with drm_to_malidp()
drm/arm/malidp: crtc: use drmm_crtc_init_with_planes()
drm/arm/malidp: plane: use drm managed resources
drm/arm/malidp: use drm_dev_unplug()
drm/arm/malidp: plane: protect device resources after removal
drm/arm/malidp: crtc: protect device resources after removal
drm/arm/malidp: drv: protect device resources after removal
drm/arm/malidp: remove calls to drm_mode_config_cleanup()
drivers/gpu/drm/arm/malidp_crtc.c | 68 +++++++++++++++++++------
drivers/gpu/drm/arm/malidp_drv.c | 78 ++++++++++++-----------------
drivers/gpu/drm/arm/malidp_drv.h | 2 +
drivers/gpu/drm/arm/malidp_hw.c | 10 ++--
drivers/gpu/drm/arm/malidp_mw.c | 6 +--
drivers/gpu/drm/arm/malidp_planes.c | 45 ++++++++---------
6 files changed, 117 insertions(+), 92 deletions(-)
base-commit: 08fb97de03aa2205c6791301bd83a095abc1949c
--
2.37.3
next reply other threads:[~2022-10-01 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 16:39 Danilo Krummrich [this message]
2022-10-01 16:39 ` [PATCH drm-misc-next v2 1/9] drm/arm/malidp: use drmm_* to allocate driver structures Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 2/9] drm/arm/malidp: replace drm->dev_private with drm_to_malidp() Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 3/9] drm/arm/malidp: crtc: use drmm_crtc_init_with_planes() Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 4/9] drm/arm/malidp: plane: use drm managed resources Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 5/9] drm/arm/malidp: use drm_dev_unplug() Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 6/9] drm/arm/malidp: plane: protect device resources after removal Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 7/9] drm/arm/malidp: crtc: " Danilo Krummrich
2022-10-01 19:47 ` kernel test robot
2022-10-01 16:39 ` [PATCH drm-misc-next v2 8/9] drm/arm/malidp: drv: " Danilo Krummrich
2022-10-01 16:39 ` [PATCH drm-misc-next v2 9/9] drm/arm/malidp: remove calls to drm_mode_config_cleanup() Danilo Krummrich
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=20221001163946.534067-1-dakr@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@linux.ie \
--cc=brian.starkey@arm.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®