From: Devarsh Thakkar <devarsht@ti.com>
To: Hari Nagalla <hnagalla@ti.com>, <nm@ti.com>, <vigneshr@ti.com>
Cc: <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add R5F and C7x DSP nodes for AM62a SoC
Date: Tue, 9 May 2023 22:04:30 +0530 [thread overview]
Message-ID: <5f523657-ae0a-cef2-4de6-762ce365f20a@ti.com> (raw)
In-Reply-To: <20230502141416.9924-1-hnagalla@ti.com>
Hi Hari,
Thanks for the series.
On 02/05/23 19:44, Hari Nagalla wrote:
> This series adds the R5F processor nodes and C7x DSP node for
> AM62a SoC.
>
> The first patch adds the nodes to the SoC device tree and the second
> patch reserves the memory for remote rpoc IPCs on AM62a-SK.
>
> Hari Nagalla (2):
> arm64: dts: ti: k3-am62a: Add remote proc nodes
> arm64: dts: ti: k3-am62a7-sk: Enable remote proc nodes
>
I think good to preserve the authorship if porting from an existing
tree. Also in my opinion good to keep split patches if coming from
different authors and to different files.
Regards
Devarsh
> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 11 ++++
> arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi | 23 +++++++
> arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi | 23 +++++++
> arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 69 +++++++++++++++++++++
> 4 files changed, 126 insertions(+)
>
next prev parent reply other threads:[~2023-05-09 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 14:14 Hari Nagalla
2023-05-02 14:14 ` [PATCH 1/2] arm64: dts: ti: k3-am62a: Add remote proc nodes Hari Nagalla
2023-05-02 14:14 ` [PATCH 2/2] arm64: dts: ti: k3-am62a7-sk: Enable " Hari Nagalla
2023-05-09 16:34 ` Devarsh Thakkar [this message]
2023-06-15 5:22 ` [PATCH 0/2] Add R5F and C7x DSP nodes for AM62a SoC 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=5f523657-ae0a-cef2-4de6-762ce365f20a@ti.com \
--to=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@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=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®