From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH 0/6] drm: avoid poking at dev->vblank[] directly
Date: Fri, 7 Nov 2025 13:04:54 +0200 [thread overview]
Message-ID: <cover.1762513240.git.jani.nikula@intel.com> (raw)
We have accessors for dev->vblank[], and poking at that directly should
be reserved for drm_vblank.c. This series along with [1] switches to use
the accessors.
I've got a whole another series brewing refactoring drm_vblank.c, but
wanted to split this out of the series to keep it manageable. None of
the patches here depend on each other, and the refactoring doesn't
depend on it, so the patches to drivers can be merged every which way,
just let me know.
BR,
Jani.
[1] https://lore.kernel.org/r/20251106200000.1455164-1-jani.nikula@intel.com
Jani Nikula (6):
drm/vblank: use drm_crtc_vblank_crtc() in workers
drm/atomic: use drm_crtc_vblank_waitqueue()
drm/msm: use drm_crtc_vblank_waitqueue()
drm/tidss: use drm_crtc_vblank_crtc()
drm/vmwgfx: use drm_crtc_vblank_crtc()
drm/gma500: use drm_crtc_vblank_crtc()
drivers/gpu/drm/drm_atomic_helper.c | 4 ++-
drivers/gpu/drm/drm_vblank_work.c | 2 +-
drivers/gpu/drm/gma500/psb_irq.c | 36 +++++++++++++++--------
drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c | 3 +-
drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c | 3 +-
drivers/gpu/drm/tidss/tidss_crtc.c | 3 +-
drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c | 6 ++--
7 files changed, 34 insertions(+), 23 deletions(-)
--
2.47.3
next reply other threads:[~2025-11-07 11:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 11:04 Jani Nikula [this message]
2025-11-07 11:04 ` [PATCH 1/6] drm/vblank: use drm_crtc_vblank_crtc() in workers Jani Nikula
2025-11-10 9:44 ` Thomas Zimmermann
2025-11-07 11:04 ` [PATCH 2/6] drm/atomic: use drm_crtc_vblank_waitqueue() Jani Nikula
2025-11-10 9:57 ` Thomas Zimmermann
2025-11-10 12:51 ` Jani Nikula
2025-11-10 13:18 ` Thomas Zimmermann
2025-11-10 13:42 ` Jani Nikula
2025-11-07 11:04 ` [PATCH 3/6] drm/msm: " Jani Nikula
2025-11-08 17:00 ` Dmitry Baryshkov
2025-11-07 11:04 ` [PATCH 4/6] drm/tidss: use drm_crtc_vblank_crtc() Jani Nikula
2025-11-08 15:54 ` Jyri Sarha
2025-11-07 11:04 ` [PATCH 5/6] drm/vmwgfx: " Jani Nikula
2025-11-07 16:21 ` Ian Forbes
2025-11-07 11:05 ` [PATCH 6/6] drm/gma500: " Jani Nikula
2025-11-07 13:11 ` Patrik Jakobsson
2025-11-07 11:48 ` ✗ CI.checkpatch: warning for drm: avoid poking at dev->vblank[] directly Patchwork
2025-11-07 11:50 ` ✓ CI.KUnit: success " Patchwork
2025-11-07 12:34 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-09 1:01 ` ✗ Xe.CI.Full: 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=cover.1762513240.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).