Re: [PATCH v3 1/1] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output

["Luca Ceresoli" <luca.ceresoli@bootlin.com>]

Hello Ernest,

On Fri Sep 4, 2026 at 2:02 PM CEST, Ernest Van Hoecke wrote:

[...]

>> > Also, from our testing, when using:
>> >
>> > dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST |
>> >           MIPI_DSI_MODE_VIDEO_NO_HSA | MIPI_DSI_MODE_NO_EOT_PACKET;
>> >
>> > we are not able to get display output.
>>
>> This is the case for the panel I worked on as well. In the practice we both
>> observe that non-burst mode is what fixes the panel, but there is no clear
>> explanation of the reason in the docs (that's what I hope to discover from
>> TI).
>>
> I am testing a DSI panel on our Verdin iMX8MP module, and noticed that
> this caused a regression.

Ouch :(

> In v4 of this series only the change removing NO_HFP and NO_HBP was
> applied. [1]
>
> For us, the display worked before that change. So with
> MIPI_DSI_MODE_VIDEO_BURST | MIPI_DSI_MODE_VIDEO_NO_HBP |
> MIPI_DSI_MODE_VIDEO_NO_HFP: things are fine.
>
> But with only MIPI_DSI_MODE_VIDEO_NO_HBP | MIPI_DSI_MODE_VIDEO_NO_HFP
> removed, it no longer works.

That's strange, IIRC that removal was just changing an incorrect behaviour
into the correct one. At least, according to the datasheet.

Do you have some more insight on what's going on ith your board? If you
could check your clock tree and panel timings in particular that would be
good: if you have incorrect timings or clocks, pretty much any change
anywhere (correct or not) has some probability of hiding the problem.

> I can verify that if I also remove
> MIPI_DSI_MODE_VIDEO_BURST, things work fine again.
>
> How can we proceed, will we be applying the removal of
> MIPI_DSI_MODE_VIDEO_BURST soon?

No, I'm afraid that's not going to happen. See the discussion starting at
https://lore.kernel.org/r/ahsxWhXMhzbAj_3G@Seans-MacBook-Pro.local

> I think we'll need to either revert this and later apply both together
> when ready, or apply the second patch now as well. Right now, it broke
> the DSI panel behind a TI sn65dsi83 bridge on v7.3-rc1.

Reverting is surely the last resort. If you can answer the above questions
it would be good, maybe we find out reverting is not necessary, and worst
case we'll revert with better understanding on what went wrong, and maybe
come up with a new fix that doesn't regress.

Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com