On Mon, Sep 09, 2024 at 11:15:28AM +0300, Tomi Valkeinen wrote: > Hi, > > On 06/09/2024 14:43, Francesco Dolcini wrote: > > +Max > > > > Hello Aradhya, > > > > On Tue, Jul 16, 2024 at 02:12:44PM +0530, Aradhya Bhatia wrote: > > > The addition of the 2nd OLDI TX (and a 2nd DSS in AM62Px) creates a need > > > for some major changes for a full feature experience. > > > > > > 1. The OF graph needs to be updated to accurately show the data flow. > > > 2. The tidss and OLDI drivers now need to support the dual-link and the > > > cloned single-link OLDI video signals. > > > 3. The drivers also need to support the case where 2 OLDI TXes are > > > connected to 2 different VPs - thereby creating 2 independent streams > > > of single-link OLDI outputs. > > > > Have you considered/tested the use case in which only single link is used? > > You do not mention it here and to me this is a relevant use case. > > > > There is a workaround for this (use option 2, cloned, even if nothing is > > connected to the second link), but this seems not correct. > > > > We (Max in Cc here) noticed that this specific use case is broken on > > your downstream v6.6 TI branch. > > What if you set "fw_devlink=off" kernel boot parameter? Hi Tomi My overlay specifing a single link which did not work by default results in a working panel with "fw_devlink=off" on the cmdline. Max > > Tomi >
