From: Swamil Jain <s-jain1@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <devarsht@ti.com>, <praneeth@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] Add DSS support for AM62L SoC
Date: Sun, 13 Sep 2026 20:34:55 +0530 [thread overview]
Message-ID: <589b873d-f7b7-45d3-bee4-a7b090a26b0a@ti.com> (raw)
In-Reply-To: <f49852ba-c484-4703-9f5a-457443bd4942@ti.com>
On 06-09-2026 19:08, Kumar, Udit wrote:
>
>
> On 9/3/2026 2:46 PM, Swamil Jain wrote:
>> Hi Tomi,
>>
>> On 8/21/26 14:32, Tomi Valkeinen wrote:
>>> Hi,
>>>
>>> On 11/08/2026 16:08, Swamil Jain wrote:
>>>> This series:
>>>> - Adds base support to enable Display on TI AM62L[1] SoCs
>>>> - Adds base support for DSI output
>>>> - Enbales HDMI output out-of-box
>>>>
>>>> [1]: https://www.ti.com/product/AM62L
>>
>> Thanks for reviewing the patch.
>>
>>> Do we really need bootph-all? In any case:
>>>
>>
>> We need it to enable splash-screen.
>>
>
> Then you should have in ports too
Thanks Udit, will add the property to ports too and respin the series.
Regards,
Swamil.
>
>> Regards,
>> Swamil
>>
>>
>>> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>>>
>>> Tomi
>>>
>>
>
prev parent reply other threads:[~2026-09-13 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 13:08 [PATCH v4 0/2] Add DSS support for AM62L SoC Swamil Jain
2026-08-11 13:08 ` [PATCH v4 1/2] arm64: dts: ti: k3-am62l-main: Add DSS & DSI related nodes Swamil Jain
2026-08-11 13:08 ` [PATCH v4 2/2] arm64: dts: ti: k3-am62l3-evm: Add HDMI support Swamil Jain
2026-09-06 13:44 ` Kumar, Udit
2026-09-18 9:17 ` Swamil Jain
2026-08-21 9:02 ` [PATCH v4 0/2] Add DSS support for AM62L SoC Tomi Valkeinen
2026-09-03 9:16 ` Swamil Jain
2026-09-06 13:38 ` Kumar, Udit
2026-09-13 15:04 ` Swamil Jain [this message]
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=589b873d-f7b7-45d3-bee4-a7b090a26b0a@ti.com \
--to=s-jain1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--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