Re: [PATCH 0/2] Pixel 3 display fixes

[David Heidelberg <david@ixit.cz>]

Would make sense implement SWIRE "support" (which is here NO-OP)?

I guess device-tree should document that SWIRE is used, even when kernel doesn't 
have to do anything?

e.g. something like - into the device DT?

&pmi8998_labibb {
        qcom,swire-control;
};

David

On 09/08/2026 02:04, David Heidelberg via B4 Relay wrote:
> Fix panel not recovering after unprepare and backlight intensity.
> 
> I extensively reproduced the vendor bootloader sequence, but after the
> boot isn't possible to do the full initialization of the display (at
> least on Pixel 3, and panel can't be found anywhere else).
> 
> The downstream, due to having attached touchscreen reusing same
> supplies, never turns the panel off. Let's do the same.
> 
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> David Heidelberg (2):
>        drm/panel: lg-sw43408: do not assert reset across unprepare
>        drm/panel: lg-sw43408: use the full DCS brightness range
> 
>   drivers/gpu/drm/panel/panel-lg-sw43408.c | 14 ++++++++++----
>   1 file changed, 10 insertions(+), 4 deletions(-)
> ---
> base-commit: 95d6a9ccef99117115e41e9adb271243bd5e985b
> change-id: 20260809-fix-blueline-panel-af2b7c967f2d
> 
> Best regards,
> --
> David Heidelberg <david@ixit.cz>
> 
> 

-- 
David Heidelberg