toggle quoted messageShow quoted text
Thanks for the feedback.
From: Pavel Machek <email@example.com>
Sent: 13 April 2021 11:12
To: Biju Das <firstname.lastname@example.org>
Cc: email@example.com; Nobuhiro Iwamatsu
<firstname.lastname@example.org>; Pavel Machek <email@example.com>; Chris
Paterson <Chris.Paterson2@renesas.com>; Prabhakar Mahadev Lad
Subject: Re: [PATCH 4.19.y-cip] drm: rcar-du: Fix crash when using LVDS1
clock for CRTC
From: Laurent Pinchart <firstname.lastname@example.org>The patch looks okay to me. I'll test it and can apply it if it works
[ Upstream commit 53ced169373aab52d3b5da0fee6a342002d1876d ]
On D3 and E3 platforms, the LVDS encoder includes a PLL that can
generate a clock for the corresponding CRTC, used even when the CRTC
output to a non-LVDS port. This mechanism is supported by the driver,
but the implementation is broken in dual-link LVDS mode. In that case,
the LVDS1 drm_encoder is skipped, which causes a crash when trying to
access its bridge later on.
Fix this by storing bridge pointers internally instead of retrieving
them from the encoder. The rcar_du_device encoders field isn't used
anymore and can be dropped.
But I don't believe it is in our 5.10, so I'd like it to be submitted for
Or just tell me it is okay and I'll apply it there, too.
Please apply to 5.10-cip as well, since it is present in 5.10 stable.