From: Devarsh Thakkar <devarsht@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <praneeth@ti.com>, <a-bhatia1@ti.com>, <j-luthra@ti.com>,
<b-brnich@ti.com>, <detheridge@ti.com>, <p-mantena@ti.com>,
<vijayp@ti.com>, <devarsht@ti.com>
Subject: [PATCH 0/3] Add global CMA reserve area
Date: Thu, 13 Jun 2024 20:38:59 +0530 [thread overview]
Message-ID: <20240613150902.2173582-1-devarsht@ti.com> (raw)
Add global CMA reserve area for AM62x, AM62A and AM62P SoCs.
These SoCs do not have MMU and hence require contiguous memory pool to
support various multimedia use-cases.
Brandon Brnich (1):
arm64: dts: ti: k3-am62p5-sk: Reserve 576 MiB of global CMA
Devarsh Thakkar (2):
arm64: dts: ti: k3-am62x-sk-common: Reserve 128MiB of global CMA
arm64: dts: ti: k3-am62a7-sk: Reserve 576MiB of global CMA
arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 9 +++++++++
arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 7 +++++++
arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 8 ++++++++
3 files changed, 24 insertions(+)
--
2.39.1
next reply other threads:[~2024-06-13 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 15:08 Devarsh Thakkar [this message]
2024-06-13 15:09 ` [PATCH 1/3] arm64: dts: ti: k3-am62x-sk-common: Reserve 128MiB of global CMA Devarsh Thakkar
2024-06-13 15:09 ` [PATCH 2/3] arm64: dts: ti: k3-am62a7-sk: Reserve 576MiB " Devarsh Thakkar
2024-06-14 17:27 ` Brandon Brnich
2024-06-13 15:09 ` [PATCH 3/3] arm64: dts: ti: k3-am62p5-sk: Reserve 576 MiB " Devarsh Thakkar
2024-06-14 17:04 ` Brandon Brnich
2024-06-21 16:14 ` Devarsh Thakkar
2024-06-14 17:58 ` [PATCH 0/3] Add global CMA reserve area Randolph Sapp
2024-06-24 16:33 ` Andrew Davis
2024-06-28 15:57 ` Devarsh Thakkar
2024-06-28 16:35 ` Randolph Sapp
2024-06-30 7:09 ` Vignesh Raghavendra
2024-07-01 14:33 ` Andrew Davis
2024-07-01 18:26 ` Randolph Sapp
2024-07-05 13:18 ` (subset)[PATCH " Vignesh Raghavendra
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=20240613150902.2173582-1-devarsht@ti.com \
--to=devarsht@ti.com \
--cc=a-bhatia1@ti.com \
--cc=b-brnich@ti.com \
--cc=conor+dt@kernel.org \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-luthra@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=p-mantena@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=vijayp@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.