This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
Hello,
In our design we use OLDI which goes to an LVDS to DPI converter (THC63LVDR84C) and the DPI output of this gets fed into an ADV7513, which looks like the below
Now my question is how I would model this into a device tree to get this working.
I'm using a build based on meta-ti-bsp and arago distro, and using linux-ti 6.6, I've tried looking over a couple of the LCD panels that use OLDI but I still don't feel any wiser on how I would model this onto a setup like mine.
We also use the DPI and that was a bit more straight forward to model the setup of VP2 DPI -> ADV7513 -> connector
Any help would be greatly appreciated to get this working.
Best regards,
Jesse
Hi Jesse,
Currently we do not have support for the drivers used by you on our EVMs, due to which we cannot validate their working. But I would like you to ask you the following questions:
1. Is there any upstream driver for THC63LVDR84C? I was not able to find one.
2. Has your schematic been reviewed by TI?
3. Have you done any hardware validation for the compatibility amongst the bridges and between SoC & bridge?
Regards
Divyansh
Hello Divyansh,
1. No but I use a generic lvds-codec node, that should link properly
2. No
3. Yes that should work
In the meantime I think I've found what the issue might be, it's that single lange LVDS is currently not working going by this patchset from TI: https://patchwork.kernel.org/project/dri-devel/cover/20240716084248.1393666-1-a-bhatia1@ti.com/
Which is confirmed by my own testing when I try put it into single lane mode on linux-ti it ends up in some sort of infinite loop and the DSS does not work.
Hi Jesse,
I am currently out of office. Please expect a response in the next week.
Hi Jesse,
May I know which SDK you are using, 9.x (Linux 6.1) or 10.x (Linux 6.6)? There is a known issue with single-link driver on SDK 10.0, which may get fixed by the next SDK release. Does your application demand the use of Linux 6.6?
Regards
Divyansh
Hello Divyansh, I'm currently on your yocto scarthgap which I guess correlates to PSDK 10, but no it's not a hard requirement as we're still bringing up this board and evaluating, so I'll wait for the support to arrive, thanks!