From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@redhat.com, airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org
Cc: Thomas Zimmermann <tzimmermann@suse.de>, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/3] drm/{ast, mgag200}: Protect I/O regs against concurrent access
Date: Mon, 2 May 2022 16:25:11 +0200 [thread overview]
Message-ID: <20220502142514.2174-1-tzimmermann@suse.de> (raw)
Protect access to I/O registers in ast and mgag200 via lock. Commit-
tail functions and get-modes operations use the same registers and can
interfere with each other. This can result in failed mode-setting
operations.
As both drivers use fully managed cleanup, the patchset adds a new helper
that initializes a mutex with auto-cleanup.
Thomas Zimmermann (3):
drm: Add DRM-managed mutex_init()
drm/ast: Protect concurrent access to I/O registers with lock
drm/mgag200: Protect concurrent access to I/O registers with lock
drivers/gpu/drm/ast/ast_drv.h | 1 +
drivers/gpu/drm/ast/ast_main.c | 4 +++
drivers/gpu/drm/ast/ast_mode.c | 48 ++++++++++++++++++++++++--
drivers/gpu/drm/drm_managed.c | 27 +++++++++++++++
drivers/gpu/drm/mgag200/mgag200_drv.c | 6 ++++
drivers/gpu/drm/mgag200/mgag200_drv.h | 1 +
drivers/gpu/drm/mgag200/mgag200_mode.c | 14 ++++++++
include/drm/drm_managed.h | 3 ++
8 files changed, 101 insertions(+), 3 deletions(-)
base-commit: 3ae2e00290c290713e21118220a817a24b44d39f
prerequisite-patch-id: c2b2f08f0eccc9f5df0c0da49fa1d36267deb11d
prerequisite-patch-id: c67e5d886a47b7d0266d81100837557fda34cb24
--
2.36.0
next reply other threads:[~2022-05-02 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 14:25 Thomas Zimmermann [this message]
2022-05-02 14:25 ` [PATCH 1/3] drm: Add DRM-managed mutex_init() Thomas Zimmermann
2022-05-04 9:50 ` Daniel Vetter
2022-05-02 14:25 ` [PATCH 2/3] drm/ast: Protect concurrent access to I/O registers with lock Thomas Zimmermann
2022-05-02 14:25 ` [PATCH 3/3] drm/mgag200: " Thomas Zimmermann
2022-05-04 12:31 ` Jocelyn Falempe
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=20220502142514.2174-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.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 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.