From: Andrew Davis <afd@ti.com>
To: Jayesh Choudhary <j-choudhary@ti.com>, <nm@ti.com>,
<vigneshr@ti.com>, <linux-kernel@vger.kernel.org>
Cc: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<kristo@kernel.org>, <u-kumar1@ti.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <devarsht@ti.com>
Subject: Re: [PATCH 0/4] Add global CMA areas for few TI SoCs
Date: Mon, 28 Apr 2025 09:42:59 -0500 [thread overview]
Message-ID: <09979b2a-73b0-4a74-978c-b082764e777e@ti.com> (raw)
In-Reply-To: <20250424084415.66457-1-j-choudhary@ti.com>
On 4/24/25 3:44 AM, Jayesh Choudhary wrote:
> Hello All,
>
> Following AM62* platforms[0], this patches add global CMA reserve area for:
> - J721S2-EVM (1056 MiB)
> - J784S4-EVM (1920 MiB)
> - AM68-SK (1008 MiB)
> - AM69-SK (1904 MiB)
>
> These SoCs does not have MMU and hence they require contiguous memory
> pool to support various multimedia usecase.
>
> The calculation was done considering H264 codec requirements, dual-display
> supported in each platforms and multicamera use-cases.
> Additional buffer was kept for other peripheral s and to account for
> fragmentation.
What if I'm not going to use 8 cameras, 2 displays, and decode 16 H264
streams all at the same time? Why should I always lose 2GB of DRAM
unconditionally, just in-case someone someday runs this imagined
worst-case situation?
If I *do* intend to have my device perform some nightmare use-case like
the above, I can pass the needed CMA size in on the kernel command line.
That is a configuration for my specific use-case after all, and DT is
*not* for configuration, especially not insane configurations like this.
Andrew
> The breakdown is mentioned in each commit message.
>
> [0]: https://lore.kernel.org/all/20240613150902.2173582-1-devarsht@ti.com/
>
> Jayesh Choudhary (4):
> arm64: dts: ti: k3-j721s2-som-p0: Reserve 1056MiB of global CMA
> arm64: dts: ti: k3-j784s4-j742s2-evm-common: Reserve 1920MiB of global
> CMA
> arm64: dts: ti: k3-am68-sk-som: Reserve 1008MiB of global CMA
> arm64: dts: ti: k3-am69-sk: Reserve 1904MiB of global CMA
>
> arch/arm64/boot/dts/ti/k3-am68-sk-som.dtsi | 8 ++++++++
> arch/arm64/boot/dts/ti/k3-am69-sk.dts | 8 ++++++++
> arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi | 8 ++++++++
> arch/arm64/boot/dts/ti/k3-j784s4-j742s2-evm-common.dtsi | 8 ++++++++
> 4 files changed, 32 insertions(+)
>
next prev parent reply other threads:[~2025-04-28 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 8:44 Jayesh Choudhary
2025-04-24 8:44 ` [PATCH 1/4] arm64: dts: ti: k3-j721s2-som-p0: Reserve 1056MiB of global CMA Jayesh Choudhary
2025-04-24 8:44 ` [PATCH 2/4] arm64: dts: ti: k3-j784s4-j742s2-evm-common: Reserve 1920MiB " Jayesh Choudhary
2025-04-24 8:44 ` [PATCH 3/4] arm64: dts: ti: k3-am68-sk-som: Reserve 1008MiB " Jayesh Choudhary
2025-04-24 8:44 ` [PATCH 4/4] arm64: dts: ti: k3-am69-sk: Reserve 1904MiB " Jayesh Choudhary
2025-04-28 14:42 ` Andrew Davis [this message]
2025-05-06 14:20 ` [PATCH 0/4] Add global CMA areas for few TI SoCs Brandon Brnich
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=09979b2a-73b0-4a74-978c-b082764e777e@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--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
all inboxes | Powered by JetHome®