Re: [PATCH v2] drm/panel: nt35510: Make new commands optional

2024-09-22 Thread Linus Walleij
On Sun, Sep 22, 2024 at 4:47 PM Dmitry Baryshkov wrote: > > if (ret) > > return ret; > > + > > ret = nt35510_send_long(nt, dsi, NT35510_P1_SETVCL, > > NT35510_P1_VCL_LEN, > > nt->conf->vcl); > > if (ret) >

Re: [PATCH v2] drm/panel: nt35510: Make new commands optional

2024-09-22 Thread Dmitry Baryshkov
On Sun, Sep 08, 2024 at 11:50:30PM GMT, Linus Walleij wrote: > The commit introducing the Frida display started to write the > SETVCMOFF registers unconditionally, and some (not all!) Hydis > display seem to be affected by ghosting after the commit. > > Make SETVCMOFF optional and only send these

Re: [PATCH v2] drm/panel: nt35510: Make new commands optional

2024-09-09 Thread Stefan Hansson
Hi again! On 2024-09-08 23:50, Linus Walleij wrote: The commit introducing the Frida display started to write the SETVCMOFF registers unconditionally, and some (not all!) Hydis display seem to be affected by ghosting after the commit. Make SETVCMOFF optional and only send these commands on the

[PATCH v2] drm/panel: nt35510: Make new commands optional

2024-09-08 Thread Linus Walleij
The commit introducing the Frida display started to write the SETVCMOFF registers unconditionally, and some (not all!) Hydis display seem to be affected by ghosting after the commit. Make SETVCMOFF optional and only send these commands on the Frida display for now. Reported-by: Stefan Hansson Fi