Hi, On Wed, May 24, 2023 at 1:06 AM Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> wrote: > > On 24/05/2023 09:59, Johan Hovold wrote: > > On Tue, May 23, 2023 at 12:23:04PM -0700, Abhinav Kumar wrote: > >> On 5/23/2023 8:24 AM, Johan Hovold wrote: > >>> On Fri, May 12, 2023 at 09:13:04PM +0300, Dmitry Baryshkov wrote: > >>>> On 28/04/2023 02:28, Abhinav Kumar wrote: > >>>>> On sc7280 where eDP is the primary display, PSR is causing > >>>>> IGT breakage even for basic test cases like kms_atomic and > >>>>> kms_atomic_transition. Most often the issue starts with below > >>>>> stack so providing that as reference > >>>>> > >>>>> Call trace: > > > >>>>> ---[ end trace 0000000000000000 ]--- > >>>>> [drm-dp] dp_ctrl_push_idle: PUSH_IDLE pattern timedout > >>>>> > >>>>> Other basic use-cases still seem to work fine hence add a > >>>>> a module parameter to allow toggling psr enable/disable till > >>>>> PSR related issues are hashed out with IGT. > >>>> > >>>> For the reference: Bjorn reported that he has issues with VT on a > >>>> PSR-enabled laptops. This patch fixes the issue for him > >>> > >>> Module parameters are almost never warranted, and it is definitely not > >>> the right way to handle a broken implementation. > >>> > >>> I've just sent a revert that unconditionally disables PSR support until > >>> the implementation has been fixed: > >>> > >>> https://lore.kernel.org/lkml/20230523151646.28366-1-johan+linaro@xxxxxxxxxx/ > >> > >> I dont completely agree with this. Even the virtual terminal case was > >> reported to be fixed by one user but not the other. So it was probably > >> something missed out either in validation or reproduction steps of the > >> user who reported it to be fixed OR the user who reported it not fixed. > >> That needs to be investigated now. > > > > Yes, there may still be some time left to fix it, but it's pretty damn > > annoying to find that an issue reported two months ago still is not > > fixed at 6.4-rc3. (I even waited to make the switch to 6.4 so that I > > would not have to spend time on this.) > > > > I didn't see any mail from Bjorn saying that the series that claimed to > > fix the VT issue actually did fix the VT issue. There's only the comment > > above from Dmitry suggesting that disabling this feature is the only way > > to get a working terminal back. > > Originally this issue was reported by Doug, and at [1] he reported that > an issue is fixed for him. So, for me it looks like we have hardware > where VT works and hardware where it doesn't. As I understand it, the problem was originally reported by Bjorn over IRC. When he reported the problem on VT2, Stephen Boyd confirmed that he could see the same problem on our hardware when using VT2. I confirmed I could reproduce and also tested the fix. I don't remember if Bjorn ever tested the fix. I think many of us assumed that it was the same issue so a fix for one person would also fix the other. > Doug, can you please confirm whether you can reproduce the PSR+VT issue > on 6.4-rc (without extra patches) or if the issue is fixed for you? > > [1] > https://lore.kernel.org/dri-devel/CAD=FV=VSHmQPtsQfWjviEZeErms-VEOTmfozejASUC9zsMjAbA@xxxxxxxxxxxxxx/ Ugh. Unfortunately, it's not easy for me to test this particular feature directly on upstream Linux. :( I typically run with a ChromeOS root filesystem, which works pretty well with mainline. One place where it doesn't work with mainline is VT2. The VT2 feature for Chromebooks is implemented with "frecon" and takes advantage of a downstream patch that we've carried in the ChromeOS kernel trees for years allowing handoff of who the DRM "master" is. For testing the fix previously, I confirmed that I could reproduce the problem on our downstream kernel (which had the PSR patches picked) and that the fixes worked for me in that context. Ah, but it shouldn't be too hard to pick that one patch. Let's see if that works. I'll pick ("CHROMIUM: drm: Add drm_master_relax debugfs file (non-root set/drop master ioctls)"). Indeed, it works! OK, so with the top of Linus's tree (v6.4-rc3-17-g9d646009f65d) plus the CHROMIUM patch to enable my VT2, I can confirm that I don't see the issue. I can switch to VT2 and typing works fine. I will say that on herobrine the backlight is all messed up, but I assume that's an unrelated issue. -Doug > > Regressions happen and sometimes there are corner cases that are harder > > to find, but this is a breakage of a fundamental feature that was > > reported before the code was even merged into mainline. > > > >> We should have ideally gone with the modparam with the feature patches > >> itself knowing that it gets enabled for all sinks if PSR is supported. > > > > Modparams are things of the past should not be used to enable broken > > features so that some vendor can tick of their internal lists of > > features that have been "mainlined". > > We have had a history of using modparam with i915 and IIRC amdgpu / > radeon drivers to allow users to easily check whether new feature works > for their hardware. My current understanding is that PSR+VT works for on > some laptops and doesn't on some other laptops, which makes it a valid case. > > > > > You can carry that single patch out-of-tree to enable this if you need > > it for some particular use case where you don't care about VTs. > > > > But hopefully you can just get this sorted quickly. If not, the revert I > > posted is the way to go rather than adding random module parameters. > > > > Johan > > -- > With best wishes > Dmitry >
