From: Francesco Dolcini <francesco@dolcini.it>
To: Aradhya Bhatia <a-bhatia1@ti.com>, max.krummenacher@toradex.com
Cc: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Jyri Sarha <jyri.sarha@iki.fi>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
DRI Development List <dri-devel@lists.freedesktop.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>, Udit Kumar <u-kumar1@ti.com>,
Francesco Dolcini <francesco@dolcini.it>,
Alexander Sverdlin <alexander.sverdlin@siemens.com>,
Randolph Sapp <rs@ti.com>, Devarsh Thakkar <devarsht@ti.com>,
Jayesh Choudhary <j-choudhary@ti.com>,
Jai Luthra <j-luthra@ti.com>
Subject: Re: [PATCH v3 0/4] drm/tidss: Add OLDI bridge support
Date: Fri, 6 Sep 2024 13:43:11 +0200 [thread overview]
Message-ID: <20240906114311.GA32916@francesco-nb> (raw)
In-Reply-To: <20240716084248.1393666-1-a-bhatia1@ti.com>
+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.
Francesco
next prev parent reply other threads:[~2024-09-06 11:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 8:42 [PATCH v3 0/4] drm/tidss: Add OLDI bridge support Aradhya Bhatia
2024-07-16 8:42 ` [PATCH v3 1/4] dt-bindings: display: ti,am65x-dss: Re-indent the example Aradhya Bhatia
2024-07-16 8:42 ` [PATCH v3 2/4] dt-bindings: display: ti: Add schema for AM625 OLDI Transmitter Aradhya Bhatia
2024-07-21 15:36 ` Krzysztof Kozlowski
2024-08-26 5:47 ` Aradhya Bhatia
2024-08-26 8:12 ` Krzysztof Kozlowski
2024-07-16 8:42 ` [PATCH v3 3/4] dt-bindings: display: ti,am65x-dss: Add OLDI properties for AM625 DSS Aradhya Bhatia
2024-07-21 15:39 ` Krzysztof Kozlowski
2024-08-26 7:32 ` Aradhya Bhatia
2024-08-26 8:15 ` Krzysztof Kozlowski
2024-07-16 8:42 ` [PATCH v3 4/4] drm/tidss: Add OLDI bridge support Aradhya Bhatia
2024-09-06 11:43 ` Francesco Dolcini [this message]
2024-09-09 8:15 ` [PATCH v3 0/4] " Tomi Valkeinen
2024-09-09 9:31 ` Aradhya Bhatia
2024-09-09 9:50 ` Tomi Valkeinen
2024-09-09 10:14 ` Aradhya Bhatia
2024-09-09 9:43 ` Max Krummenacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240906114311.GA32916@francesco-nb \
--to=francesco@dolcini.it \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a-bhatia1@ti.com \
--cc=airlied@gmail.com \
--cc=alexander.sverdlin@siemens.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=j-choudhary@ti.com \
--cc=j-luthra@ti.com \
--cc=jyri.sarha@iki.fi \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=max.krummenacher@toradex.com \
--cc=mripard@kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rs@ti.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).