linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jayesh Choudhary <j-choudhary@ti.com>
To: "Kumar, Udit" <u-kumar1@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
	<devarsht@ti.com>, <linux-kernel@vger.kernel.org>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<kristo@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/7] Add DSI display support for TI's Jacinto platforms
Date: Mon, 21 Apr 2025 17:48:43 +0530	[thread overview]
Message-ID: <94e79e4b-ff72-49ba-bcd7-ba69e2296d3b@ti.com> (raw)
In-Reply-To: <02f1912f-0a05-4446-923a-7935ed305cb3@ti.com>

Hello Udit,

On 19/04/25 14:23, Kumar, Udit wrote:
> 
> On 4/11/2025 4:21 PM, Jayesh Choudhary wrote:
>> Hello All,
>>
>> This series adds the dts support to enable DSI on 3 platforms for TI 
>> SoCs:
>> - J784S4-EVM
>> - J721S2-EVM
>> - AM68-SK
>>
>> [..]
>>
>> NOTE: For higher resolutions, we need bigger CMA region.
>> But for validation, the default value is enough.
> 
> I am not sure , how DSS uses CMA region
> 

The framebuffers for dss are allocated from cma-pool.
By default the cma-region is of 32MiB that is shared by various peripherals.

1920x1080 requires ~16MiB of CMA but sometimes due to fragmentation,
we cannot get even this much for framebuffer and memory is not allocated 
resulting in display failures.

And large resolutions like 4k@60fps require ~64MiB straight away.
So it is better to reserve appropriate CMA region.

Thanks
Jayesh

> 
>> I am posting another series to add CMA region to Jacinto platforms
>> similar to Sitara family soon:
>> <https://lore.kernel.org/all/20240613150902.2173582-1-devarsht@ti.com/>
>>
>> Jayesh Choudhary (5):
>>    arm64: dts: ti: k3-j784s4-j742s2-main-common: add DSI & DSI PHY
>>    arm64: dts: ti: k3-j784s4-j742s2-evm-common: Enable DisplayPort-1
>>    arm64: dts: ti: k3-j721s2-common-proc-board: Add main_i2c4 instance
>>    arm64: dts: ti: k3-j721s2-common-proc-board: Enable DisplayPort-1
>>    arm64: dts: ti: k3-am68-sk: Enable DSI on DisplayPort-0
>>
>> Rahul T R (2):
>>    arm64: dts: ti: k3-j721s2-main: add DSI & DSI PHY
>>    arm64: dts: ti: k3-j721s2-som-p0: add DSI to eDP
>>
>>   .../boot/dts/ti/k3-am68-sk-base-board.dts     |  96 ++++++++++++++
>>   .../dts/ti/k3-j721s2-common-proc-board.dts    | 116 +++++++++++++++++
>>   arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi    |  37 ++++++
>>   arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi  |  52 ++++++++
>>   .../dts/ti/k3-j784s4-j742s2-evm-common.dtsi   | 117 +++++++++++++++++-
>>   .../dts/ti/k3-j784s4-j742s2-main-common.dtsi  |  37 ++++++
>>   6 files changed, 454 insertions(+), 1 deletion(-)
>>


      reply	other threads:[~2025-04-21 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 10:51 [PATCH 0/7] Add DSI display support for TI's Jacinto platforms Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 1/7] arm64: dts: ti: k3-j784s4-j742s2-main-common: add DSI & DSI PHY Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 2/7] arm64: dts: ti: k3-j784s4-j742s2-evm-common: Enable DisplayPort-1 Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 3/7] arm64: dts: ti: k3-j721s2-main: add DSI & DSI PHY Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 4/7] arm64: dts: ti: k3-j721s2-common-proc-board: Add main_i2c4 instance Jayesh Choudhary
2025-04-19  9:23   ` Kumar, Udit
2025-04-21 10:09     ` Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 5/7] arm64: dts: ti: k3-j721s2-som-p0: add DSI to eDP Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 6/7] arm64: dts: ti: k3-j721s2-common-proc-board: Enable DisplayPort-1 Jayesh Choudhary
2025-04-19  9:29   ` Kumar, Udit
2025-04-21 12:02     ` Jayesh Choudhary
2025-04-11 10:51 ` [PATCH 7/7] arm64: dts: ti: k3-am68-sk: Enable DSI on DisplayPort-0 Jayesh Choudhary
2025-04-19  9:34   ` Kumar, Udit
2025-04-21 11:10     ` Jayesh Choudhary
2025-04-19  8:53 ` [PATCH 0/7] Add DSI display support for TI's Jacinto platforms Kumar, Udit
2025-04-21 12:18   ` Jayesh Choudhary [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=94e79e4b-ff72-49ba-bcd7-ba69e2296d3b@ti.com \
    --to=j-choudhary@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=robh@kernel.org \
    --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).