dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Zack Rusin <zack.rusin@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
	maarten.lankhorst@linux.intel.com,  mripard@kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/3] drm/vmwgfx: Use DRM's vblank timer
Date: Tue, 28 Apr 2026 08:08:24 +0200	[thread overview]
Message-ID: <c4364cae-abb2-4c0e-9a12-ee62e04a7ac2@suse.de> (raw)
In-Reply-To: <CABQX2QOqMct4SKiZF1dkUv7fs86qe=SAt8V_3yP52DE43XhevQ@mail.gmail.com>

Hi

Am 28.04.26 um 07:54 schrieb Zack Rusin:
> On Mon, Apr 27, 2026 at 11:02 AM Thomas Zimmermann <tzimmermann@suse.de> wrote:
>> Replace vmwgfx's vblank timer with DRM's shared implementation. The
>> common code is mostly equivalent, but provides additional protection
>> against concurrent changes to the vblank counter.
>>
>> Patches 1 and 2 align vmwgfx with the shared code, so that it can be
>> converted easily.
>>
>> The conversion is in patch 3. It replaces vmwgfx's custom timer with
>> calls to DRM's vblank interfaces. Initialization happens internally.
>>
>> This series should get some more testing.
>>
>> v2:
>> - patch 3: fix vblank cancalling in CRTC cleanup (Zack)
>> - patch 2: mention timer restart in commit message (Zack)
>>
>> Thomas Zimmermann (3):
>>    drm/vmwgfx: Determine lock-waiting timeout from vblank state
>>    drm/vmwgfx: Move vblank handling into separate helper
>>    drm/vmwgfx: Convert to DRM vblank timers
>>
>>   drivers/gpu/drm/vmwgfx/vmwgfx_kms.h  |  2 -
>>   drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c  |  1 +
>>   drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c |  1 +
>>   drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c |  1 +
>>   drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c | 70 ++++++++--------------------
>>   drivers/gpu/drm/vmwgfx/vmwgfx_vkms.h |  2 +-
>>   6 files changed, 24 insertions(+), 53 deletions(-)
>>
>> --
>> 2.54.0
>
> Looks great! Feel free to push through drm-misc-next or I can do it
> for you if you prefer.

I'll merge it in a few days if no further reviews come in.

>
> Reviewed-by: Zack Rusin <zack.rusin@broadcom.com>

Thanks a lot.

Best regards
Thomas

>
> z

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)



  reply	other threads:[~2026-04-28  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 15:00 [PATCH v2 0/3] drm/vmwgfx: Use DRM's vblank timer Thomas Zimmermann
2026-04-27 15:00 ` [PATCH v2 1/3] drm/vmwgfx: Determine lock-waiting timeout from vblank state Thomas Zimmermann
2026-04-27 15:00 ` [PATCH v2 2/3] drm/vmwgfx: Move vblank handling into separate helper Thomas Zimmermann
2026-04-27 15:00 ` [PATCH v2 3/3] drm/vmwgfx: Convert to DRM vblank timers Thomas Zimmermann
2026-04-28  5:54 ` [PATCH v2 0/3] drm/vmwgfx: Use DRM's vblank timer Zack Rusin
2026-04-28  6:08   ` Thomas Zimmermann [this message]
2026-05-04 12:21   ` 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=c4364cae-abb2-4c0e-9a12-ee62e04a7ac2@suse.de \
    --to=tzimmermann@suse.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=zack.rusin@broadcom.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