From: Nishanth Menon <nm@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Devarsh Thakkar <devarsht@ti.com>, <afd@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<a-bhatia1@ti.com>, <j-luthra@ti.com>, <praneeth@ti.com>,
<j-choudhary@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62x-sk-common: Reserve 128MiB of global CMA
Date: Mon, 7 Aug 2023 07:07:20 -0500 [thread overview]
Message-ID: <20230807120720.ibqxqoqifndafls6@judge> (raw)
In-Reply-To: <ZNCNi9k2bKwbXh81@francesco-nb.int.toradex.com>
On 08:46-20230807, Francesco Dolcini wrote:
> On Sat, Aug 05, 2023 at 02:33:55PM -0500, Nishanth Menon wrote:
> > I am esp concerned since there are platforms based on am62x and just
> > 256MB DDR.
>
> On that regard, currently you have reserved memory areas just before
> 512MB DDR limit. Any plan to move those?
Nope. Common min configuration we have seen is 512MB (why TI evms use
that definition). There are exceptional cases of 256MB boards, but in
such cases, the board dts should describe it.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2023-08-07 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 11:14 [PATCH] arm64: dts: ti: k3-am62x-sk-common: Reserve 128MiB of global CMA Devarsh Thakkar
2023-08-05 19:33 ` Nishanth Menon
2023-08-07 6:03 ` Devarsh Thakkar
2023-08-07 18:00 ` Andrew Davis
2023-08-08 8:14 ` Devarsh Thakkar
2024-05-14 14:29 ` Devarsh Thakkar
2023-08-07 6:46 ` Francesco Dolcini
2023-08-07 12:07 ` Nishanth Menon [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=20230807120720.ibqxqoqifndafls6@judge \
--to=nm@ti.com \
--cc=a-bhatia1@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=j-choudhary@ti.com \
--cc=j-luthra@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--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).