From: Aradhya Bhatia <aradhya.bhatia@linux.dev>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"jyri.sarha@iki.fi" <jyri.sarha@iki.fi>,
"tomi.valkeinen@ideasonboard.com"
<tomi.valkeinen@ideasonboard.com>,
"robh@kernel.org" <robh@kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"mripard@kernel.org" <mripard@kernel.org>
Cc: "j-choudhary@ti.com" <j-choudhary@ti.com>,
"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"u-kumar1@ti.com" <u-kumar1@ti.com>,
"max.oss.09@gmail.com" <max.oss.09@gmail.com>,
"francesco@dolcini.it" <francesco@dolcini.it>,
"devarsht@ti.com" <devarsht@ti.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, "nm@ti.com" <nm@ti.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"praneeth@ti.com" <praneeth@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] drm/tidss: Add OLDI bridge support
Date: Thu, 20 Mar 2025 18:57:53 +0530 [thread overview]
Message-ID: <b4f19dc0-6eee-4085-998f-b2739e15ba01@linux.dev> (raw)
In-Reply-To: <4155a886b3b3027d4ca8bb7a13801852ef8754e7.camel@siemens.com>
Hi,
On 18/03/25 19:05, Sverdlin, Alexander wrote:
> Hi Aradhya!
>
> On Sun, 2024-11-24 at 20:06 +0530, Aradhya Bhatia wrote:
>> From: Aradhya Bhatia <a-bhatia1@ti.com>
>>
>> The AM62x and AM62Px SoCs feature 2 OLDI TXes each, which makes it
>> possible to connect them in dual-link or cloned single-link OLDI display
>> modes. The current OLDI support in tidss_dispc.c can only support for
>> a single OLDI TX, connected to a VP and doesn't really support
>> configuration of OLDIs in the other modes. The current OLDI support in
>> tidss_dispc.c also works on the principle that the OLDI output can only
>> be served by one, and only one, DSS video-port. This isn't the case in
>> the AM62Px SoC, where there are 2 DSS controllers present that share the
>> OLDI TXes.
>>
>> Having their own devicetree and their own bridge entity will help
>> support the various display modes and sharing possiblilities of the OLDI
>> hardware.
>>
>> For all these reasons, add support for the OLDI TXes as DRM bridges.
>
> ...
>
>> +int tidss_oldi_init(struct tidss_device *tidss)
>> +{
>> + struct tidss_oldi *oldi;
>> + struct device_node *child;
>> + struct drm_bridge *bridge;
>> + u32 parent_vp, oldi_instance, companion_instance;
>> + enum tidss_oldi_link_type link_type = OLDI_MODE_UNSUPPORTED;
>> + struct device_node *oldi_parent;
>> + int ret = 0;
>> +
>> + tidss->num_oldis = 0;
>> +
>> + oldi_parent = of_get_child_by_name(tidss->dev->of_node, "oldi-transmitters");
>> + if (!oldi_parent)
>> + /* Return gracefully */
>> + return 0;
>> +
>> + for_each_child_of_node(oldi_parent, child) {
>
> Would for_each_available_child_of_node() make sense here so that
> k3-am62-main.dtsi would have both ports with status = "disabled" and
> the users will enable one or another?
>
Thank you for the suggestion!
for_each_available_child_of_node() does seem to be the better option.
I will send another revision.
--
Regards
Aradhya
next prev parent reply other threads:[~2025-03-20 13:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 14:36 [PATCH v4 0/3] drm/tidss: Add OLDI bridge support Aradhya Bhatia
2024-11-24 14:36 ` [PATCH v4 1/3] dt-bindings: display: ti,am65x-dss: Re-indent the example Aradhya Bhatia
2024-11-24 14:36 ` [PATCH v4 1/3] dt-bindings: display: ti, am65x-dss: " Aradhya Bhatia
2024-11-24 14:36 ` [PATCH v4 2/3] dt-bindings: display: ti: Add schema for AM625 OLDI Transmitter Aradhya Bhatia
2024-12-04 14:09 ` Rob Herring
2024-11-24 14:36 ` [PATCH v4 3/3] drm/tidss: Add OLDI bridge support Aradhya Bhatia
2025-03-18 13:35 ` Sverdlin, Alexander
2025-03-20 13:27 ` Aradhya Bhatia [this message]
2024-12-03 12:12 ` [PATCH v4 0/3] " Tomi Valkeinen
2024-12-03 18:14 ` Aradhya Bhatia
2024-12-03 18:36 ` Tomi Valkeinen
2024-12-09 4:17 ` Aradhya Bhatia
2025-03-19 18:00 ` Sverdlin, Alexander
2025-03-20 13:24 ` Aradhya Bhatia
2025-03-20 13:30 ` Sverdlin, Alexander
2025-03-25 18:57 ` Sverdlin, Alexander
2025-03-29 13:45 ` Aradhya Bhatia
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=b4f19dc0-6eee-4085-998f-b2739e15ba01@linux.dev \
--to=aradhya.bhatia@linux.dev \
--cc=airlied@gmail.com \
--cc=alexander.sverdlin@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=francesco@dolcini.it \
--cc=j-choudhary@ti.com \
--cc=jyri.sarha@iki.fi \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=max.oss.09@gmail.com \
--cc=mripard@kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.