From: "Kumar, Udit" <u-kumar1@ti.com>
To: Vaishnav Achath <vaishnav.a@ti.com>, <nm@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>
Cc: <linux-kernel@vger.kernel.org>, <j-choudhary@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 3/3] arm64: dts: ti: Add support for TI J722S Evaluation Module
Date: Mon, 15 Jan 2024 15:52:35 +0530 [thread overview]
Message-ID: <45b833bf-e568-4b8f-93f2-07340e794b6c@ti.com> (raw)
In-Reply-To: <20231213124930.3012-4-vaishnav.a@ti.com>
Hi Vaishnav
On 12/13/2023 6:19 PM, Vaishnav Achath wrote:
> Add basic support for the J722S EVM with UART console and
> MMC SD as rootfs.
>
> Schematics are available at:
> https://www.ti.com/lit/zip/sprr495
>
> Co-developed-by: Jayesh Choudhary <j-choudhary@ti.com>
> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
> ---
> [..]
> +
> + wkup_r5fss0_core0_memory_region: r5f-memory@a0100000 {
> + compatible = "shared-dma-pool";
> + reg = <0x00 0xa0100000 0x00 0xf00000>;
> + no-map;
> + };
Do you think, we should have some reserve memory for dma area as well
Something like wkup_r5fss0_core0_dma_memory_region
> +
> + };
> + [..]
prev parent reply other threads:[~2024-01-15 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:49 [PATCH 0/3] arm64: dts: ti: Introduce J722S SoC and EVM Vaishnav Achath
2023-12-13 12:49 ` [PATCH 1/3] dt-bindings: arm: ti: Add bindings for J722S SoCs Vaishnav Achath
2023-12-13 16:03 ` Conor Dooley
2023-12-14 7:42 ` Krzysztof Kozlowski
2023-12-13 12:49 ` [PATCH 2/3] arm64: dts: ti: Introduce J722S family of SoCs Vaishnav Achath
2023-12-13 20:27 ` Nishanth Menon
2023-12-14 8:37 ` Vaishnav Achath
2023-12-14 12:27 ` Nishanth Menon
2023-12-14 15:43 ` Andrew Davis
2023-12-14 18:33 ` Nishanth Menon
2023-12-13 12:49 ` [PATCH 3/3] arm64: dts: ti: Add support for TI J722S Evaluation Module Vaishnav Achath
2023-12-13 20:28 ` Nishanth Menon
2024-01-15 10:22 ` Kumar, Udit [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=45b833bf-e568-4b8f-93f2-07340e794b6c@ti.com \
--to=u-kumar1@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@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=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vaishnav.a@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