> Am 09.11.2020 um 11:22 schrieb Tomi Valkeinen <tomi.valkeinen@xxxxxx>: > > On 09/11/2020 11:30, H. Nikolaus Schaller wrote: >> >>> Am 09.11.2020 um 09:04 schrieb Tomi Valkeinen <tomi.valkeinen@xxxxxx>: >>> >>> On 07/11/2020 14:19, H. Nikolaus Schaller wrote: >>> >>>> I have set up based on our complete letux-5.10-rc2 tree and maybe using our private config makes >>>> the difference. Anyways, the driver is now probed and I can see the call to w677l_get_modes(). >>>> >>>> I have still no image and no calls to prepare/unprepare etc. but now I can start to debug on omap5. >>>> And hopefully we are close to push the panel driver for review. And in a second step some device >>>> tree for the Pyra. >>>> >>>> The new tree is here: https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/work-pyra-panel >>> >>> Ok, good. Do you have a link the previous driver that works (omapdrm specific panel driver)? I think >>> it's good to have that as a reference. >> >> Yes, here: >> >> https://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux/panels > > Ok. The old driver uses two separate VC configurations (request_vc calls), yes indeed. I was not sure how to handle this with the new omapdrm drivers. > so it may not work with > this series. I think we need to implement logic to the dsi driver to somehow handle this kind of setup. I see. Anyways there is missing some simple thing which makes the driver not prepared/enabled. Or is this related to VC? BR and thanks, Nikolaus
