Re: [PATCH v2] drm/amd/display: explicitly update clocks when DC is set to D3 in s0i3

2022-01-07 Thread Thorsten Leemhuis
Hi, this is your Linux kernel regression tracker speaking. On 05.01.22 18:06, Mario Limonciello wrote: > The WA from commit 5965280abd30 ("drm/amd/display: Apply w/a for > hard hang on HPD") causes a regression in s0ix where the system will > fail to resume properly. This may be because an HPD wa

RE: [PATCH v2] drm/amd/display: explicitly update clocks when DC is set to D3 in s0i3

2022-01-06 Thread Limonciello, Mario
[PATCH v2] drm/amd/display: explicitly update clocks when DC is > set > to D3 in s0i3 > > Hi, this is your Linux kernel regression tracker speaking. > > On 05.01.22 18:06, Mario Limonciello wrote: > > The WA from commit 5965280abd30 ("drm/amd/display: Apply w/a for >

RE: [PATCH v2] drm/amd/display: explicitly update clocks when DC is set to D3 in s0i3

2022-01-05 Thread Limonciello, Mario
[PATCH v2] drm/amd/display: explicitly update clocks when DC is > set > to D3 in s0i3 > > On 2022-01-05 12:06, Mario Limonciello wrote: > > The WA from commit 5965280abd30 ("drm/amd/display: Apply w/a for > > hard hang on HPD") causes a regression in s0ix where the sys

Re: [PATCH v2] drm/amd/display: explicitly update clocks when DC is set to D3 in s0i3

2022-01-05 Thread Harry Wentland
On 2022-01-05 12:06, Mario Limonciello wrote: > The WA from commit 5965280abd30 ("drm/amd/display: Apply w/a for > hard hang on HPD") causes a regression in s0ix where the system will > fail to resume properly. This may be because an HPD was active the last > time clocks were updated but clocks di

[PATCH v2] drm/amd/display: explicitly update clocks when DC is set to D3 in s0i3

2022-01-05 Thread Mario Limonciello
The WA from commit 5965280abd30 ("drm/amd/display: Apply w/a for hard hang on HPD") causes a regression in s0ix where the system will fail to resume properly. This may be because an HPD was active the last time clocks were updated but clocks didn't get updated again during s0ix. So add an extra c