Skip to contentSkip to conversation

module_mipi_dsi_driver panel with omapdrm?

DISCUSSION H. Nikolaus Schaller 1 participant 1 message Aug 5, 2020 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi David,
good to know! Would mean that the combination of HDMI and DSI may make trouble.

Maybe we should simply wait ca. 14 days until I have access to my own test setup and can run such tests easily and within minutes myself. Since it is already broken since v5.7-rc1 it should be possible to wait that time :)

Best regards,
Nikolaus

Quoted 42 lines

Am 05.08.2020 um 13:53 schrieb David Shah <[email protected]>:

If it helps, I can confirm that HDMI was working fine on the uEVM the last time I test 5.7 (I think it was the final rc before release).

David

-------- Original message --------
From: "H. Nikolaus Schaller" <[email protected]>
Date: 05/08/2020 12:49 (GMT+00:00)
To: Sebastian Reichel <[email protected]>
Cc: Laurent Pinchart <[email protected]>, Tony Lindgren <[email protected]>, Tomi Valkeinen <[email protected]>, Linux-OMAP <[email protected]>, Jyri Sarha <[email protected]>, [email protected], Discussions about the Letux Kernel <[email protected]>, David Shah <[email protected]>
Subject: Re: module_mipi_dsi_driver panel with omapdrm?

Hi,

Quoted 4 lines

Am 05.08.2020 um 13:28 schrieb Sebastian Reichel <[email protected]>:

Hi,

Quoted 8 lines
Quoted 2 lines · H. Nikolaus Schaller

What I do not yet understand is how Laurent's patch should be able to break it.

omapdrm will not probe successfully if any DT enabled component does not probe correctly. Since the patch you identified touched HDMI and VENC and you are probably using HDMI, I suggest looking there first.

Yes, that is a very good explanation.

Maybe there is a subtle change in how the HDMI connector has to be defined which is missing in our (private) DTB. Maybe the OMAP5-uEVM DTS gives a hint.

A quick check shows last hdmi specific change for omap5-board-common or uevm was in 2017 but I may have missed something.

There are 715a5a978733f0 and 671ab615bd507f which arrived in v5.7-rc1 as well and are related to hdmi clocks. So this may be (or not) and influencing factor.

BR and thanks,
Nikolaus