AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Li <sunpeng.li@amd.com>
To: Michele Palazzi <sysdadmin@m1k.cloud>
Cc: amd-gfx@lists.freedesktop.org, harry.wentland@amd.com,
	alexander.deucher@amd.com, christian.koenig@amd.com,
	siqueira@igalia.com, "Michel Dänzer" <michel.daenzer@mailbox.org>,
	"Shengyu Qu" <wiagn233@outlook.com>
Subject: Re: [PATCH 1/1] drm/amd/display: complete cursor vblank events immediately
Date: Mon, 4 May 2026 14:48:38 -0400	[thread overview]
Message-ID: <9c37520f-ad9a-4fac-bd21-e92f2107ca36@amd.com> (raw)
In-Reply-To: <e415c38b-4102-40e4-a195-0256caf34802@m1k.cloud>



On 2026-03-31 08:57, Michele Palazzi wrote:
>> On 3/20/26 01:52, Leo Li wrote:
> 
>>> Did you happen to try disabling some idle optimization features mentioned in a previous reply?
>>> https://lore.kernel.org/amd-gfx/1356e93b-af76-47f3- afc5-29535a9518bb@amd.com/
>>
> 
> 
> Sorry for the delay i have been away due to business travel, anyway since resuming testing i can't seem to reproduce the timeout with idle optimization features disabled.

Hi Michel, Shengyu,

I sent out a potential fix here: https://lore.kernel.org/amd-gfx/20260504183649.165131-1-sunpeng.li@amd.com/T/#u
If you get a chance, can you give it a spin and let me know the results(*)? The issue remains elusive on my end.

(*) Of course, make sure the Restore 5s vbl offdelay change is not applied, and that no other debug patch/kernel cmdline are applied.

Thanks,
Leo


  reply	other threads:[~2026-05-04 18:48 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 19:16 [PATCH 1/1] drm/amd/display: complete cursor vblank events immediately Michele Palazzi
2026-02-23 15:27 ` Leo Li
2026-02-27  8:53   ` Michele Palazzi
2026-02-27  8:58     ` Michele Palazzi
2026-03-02 22:13       ` Leo Li
2026-03-03  8:17         ` Shengyu Qu
2026-03-03 19:07           ` Leo Li
2026-03-04 14:00             ` Michele Palazzi
2026-03-04 14:20               ` Leo Li
2026-03-05 22:30                 ` Leo Li
2026-03-06  8:37                   ` Michele Palazzi
2026-03-09 16:49                     ` Michele Palazzi
2026-03-10 23:50                       ` Leo Li
2026-03-11 10:16                         ` Shengyu Qu
2026-03-11 10:38                         ` Michele Palazzi
2026-03-11 17:56                           ` Leo Li
2026-03-16 14:55                             ` Michele Palazzi
2026-03-16 15:17                               ` Michele Palazzi
2026-03-16 18:39                                 ` Leo Li
2026-03-16 18:48                                   ` Leo Li
2026-03-18 11:36                                     ` Michele Palazzi
2026-03-20  0:52                                       ` Leo Li
2026-03-20  1:33                                         ` Michele Palazzi
2026-03-31 12:57                                           ` Michele Palazzi
2026-05-04 18:48                                             ` Leo Li [this message]
2026-05-05  7:27                                               ` Michele Palazzi
2026-05-07 20:19                                                 ` Leo Li
2026-05-08  7:37                                                   ` Michele Palazzi
2026-05-05  7:31                                               ` Shengyu Qu
2026-04-18 19:37                                         ` Shengyu Qu
2026-04-22 14:31                                           ` Leo Li
2026-04-22 14:57                                             ` Michele Palazzi
2026-02-27 19:43   ` Alex Deucher
2026-03-02  8:53   ` Michel Dänzer
2026-03-02 22:14     ` Leo Li
  -- strict thread matches above, loose matches on Subject: below --
2026-02-18  0:31 Michele Palazzi
2026-02-18  9:41 ` Michel Dänzer
2026-02-18 10:09   ` Michele Palazzi
2026-02-19 11:09     ` Michel Dänzer
2026-02-19 13:08       ` Michele Palazzi
2026-02-19 13:59         ` Michel Dänzer
2026-02-19 15:56           ` Michele Palazzi
2026-02-19 16:02             ` Michel Dänzer
2026-02-20 11:10               ` Michele Palazzi

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=9c37520f-ad9a-4fac-bd21-e92f2107ca36@amd.com \
    --to=sunpeng.li@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=harry.wentland@amd.com \
    --cc=michel.daenzer@mailbox.org \
    --cc=siqueira@igalia.com \
    --cc=sysdadmin@m1k.cloud \
    --cc=wiagn233@outlook.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