dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@kernel.org>
To: Leo Li <sunpeng.li@amd.com>,
	Derek John Clark <derekjohn.clark@gmail.com>
Cc: Harry.Wentland@amd.com, airlied@gmail.com,
	amd-gfx@lists.freedesktop.org,  dri-devel@lists.freedesktop.org,
	jani.nikula@linux.intel.com, simona@ffwll.ch,
	ville.syrjala@linux.intel.com
Subject: Re: [PATCH v4 1/2] drm: Introduce drm_crtc_vblank_prepare()
Date: Thu, 29 Jan 2026 10:44:12 -0600	[thread overview]
Message-ID: <f56cb9dc-d47b-49bd-a199-bff9e7bb29b0@kernel.org> (raw)
In-Reply-To: <31babc28-0e69-46e5-94cd-8856e9ad6550@amd.com>

On 1/29/26 10:40 AM, Leo Li wrote:
> 
> 
> On 2026-01-29 10:15, Leo Li wrote:
>>
>>
>> On 2026-01-28 23:43, Derek John Clark wrote:
>>>> From: Leo Li <sunpeng.li@amd.com>
>>>>
>>>> Some drivers need to perform sleepable operations prior to enabling
>>>> vblank interrupts. A display hardware spin-up from a low-power state
>>>> that requires synchronization with the rest of the driver, for example.
>>>>
>>>> To support this, introduce a DRM-internal drm_crtc_vblank_prepare()
>>>> helper that calls back into the driver -- if implemented -- for DRM to
>>>> do such preparation work before enabling vblank.
>>>>
>>>> v3:
>>>> * Unexport drm_crtc_vblank_prepare() and make it DRM internal
>>>> * Drop warnings in drm core for vblank_prepare(), drivers can do so in
>>>>   their implementations
>>>> * Drop unnecessary crtc null checks
>>>> * Check for drm_dev_has_vblank()
>>>> * Rebase on latest drm-misc-next
>>>>
>>>> v4:
>>>> * EXPORT function to fix build error on DRM_KMS_HELPER=m
>>>>
>>>> Signed-off-by: Leo Li <sunpeng.li@amd.com>
>>>
>>> Hi Leo.
>>>
>>> I wanted to know what branch this series applies to. I'm trying to
>>> troubleshoot a possible vblank issue on the Legion Go 2 and was
>>> pointed towards this patch series. Unfortunately I can't get it to
>>> apply cleanly to drm/drm-fixes, drm/drm-next or stable/linux-6.18.y
>>
>> Hi Derek,
>>
>> This applies to drm-misc-next, here:
>> https://gitlab.freedesktop.org/drm/misc/kernel/-/tree/drm-misc-next
>>
>> Thanks,
>> Leo
> 
> FYI, in case you run into the same issue, I had to blacklist my wifi driver:
> modprobe.blacklist=mt7925e in my kernel cmdline for drm-misc-next to boot.
> 

And if you need wifi while testing there's some fixes for this in 6.19 
that could potentially be cherry picked.

> -Leo
> 
>>
>>>
>>>
>>>  From commit 15392f76405ecb953216b437bed76ffa49cefb7b (HEAD,
>>> drm/drm-next, drm/HEAD):
>>> $ b4 shazam https://lore.kernel.org/dri-devel/20260127194143.176248-1-sunpeng.li@amd.com/
>>> Grabbing thread from
>>> lore.kernel.org/all/20260127194143.176248-1-sunpeng.li@amd.com/t.mbox.gz
>>> Checking for newer revisions
>>> Grabbing search results from lore.kernel.org
>>> Analyzing 2 messages in the thread
>>> Analyzing 0 code-review messages
>>> Checking attestation on all messages, may take a moment...
>>> ---
>>>    [PATCH v4 1/2] drm: Introduce drm_crtc_vblank_prepare()
>>>    [PATCH v4 2/2] drm/amd/display: Implement prepare_vblank_enable callback
>>>    ---
>>>    NOTE: install dkimpy for DKIM signature verification
>>> ---
>>> Total patches: 2
>>> ---
>>> Applying: drm: Introduce drm_crtc_vblank_prepare()
>>> Applying: drm/amd/display: Implement prepare_vblank_enable callback
>>> Patch failed at 0002 drm/amd/display: Implement prepare_vblank_enable callback
>>> error: patch failed: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.c:277
>>> error: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.c: patch
>>> does not apply
>>>
>>>
>>> Thanks,
>>> Derek
>>
> 


  parent reply	other threads:[~2026-01-29 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29  4:43 [PATCH v4 1/2] drm: Introduce drm_crtc_vblank_prepare() Derek John Clark
2026-01-29 15:15 ` Leo Li
2026-01-29 16:40   ` Leo Li
2026-01-29 16:41     ` Derek John Clark
2026-01-29 16:44     ` Mario Limonciello [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-27 19:41 sunpeng.li

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=f56cb9dc-d47b-49bd-a199-bff9e7bb29b0@kernel.org \
    --to=superm1@kernel.org \
    --cc=Harry.Wentland@amd.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=derekjohn.clark@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=simona@ffwll.ch \
    --cc=sunpeng.li@amd.com \
    --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