devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, Nishanth Menon <nm@ti.com>,
	Tero Kristo <t-kristo@ti.com>
Cc: <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/8] Add R5F nodes on TI K3 AM65x and J721E SoCs
Date: Fri, 6 Nov 2020 08:26:17 -0600	[thread overview]
Message-ID: <f0caafff-9825-ae7b-cffd-69efdcb8982b@ti.com> (raw)
In-Reply-To: <547ca06c-9895-b164-60ab-5909e6c78983@ti.com>

On 11/6/20 5:43 AM, Lokesh Vutla wrote:
> 
> 
> On 29/10/20 9:07 am, Suman Anna wrote:
>> Hi Nishanth,
>>
>> The TI K3 R5F remoteproc driver and bindings were merged into 5.10-rc1,
>> and this series adds the follow-on base dt nodes for the R5F remote
>> processors on TI K3 AM65x and J721E SoCs. Additional memory nodes were
>> also added to boot these processors successfully on applicable TI K3
>> AM65x and J721E EVM boards. The series uses previously accepted mailbox
>> nodes.
>>
>> The patches follow slightly different convention between AM65x and
>> J721E. The reserved-memory nodes are added directly in the relevant
>> board dts file for AM65x boards, while they are added in the common
>> k3-j721e-som-p0.dtsi file for J721E SoCs following the similar addition
>> of K3 C66x and C71x DSP nodes in 5.10-rc1.
>>
>> Patches apply on top of your 5.10-rc1 based staging branch.
>>
>> I have validated the IPC functionality using System Firmware v2020.04a
>> and corresponding IPC example firmwares. 
> 
> 
> Series looks good to me.
> 
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>

Thanks Lokesh.


> On a side note: any reason not to add R5f nodes for J7200?

J7200 nodes would have to wait until the corresponding dt-bindings and driver
updates make it into mainline. They do use different compatibles, and I will
post them in the next couple of weeks.

regards
Suman

  reply	other threads:[~2020-11-06 14:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  3:37 [PATCH 0/8] Add R5F nodes on TI K3 AM65x and J721E SoCs Suman Anna
2020-10-29  3:37 ` [PATCH 1/8] arm64: dts: ti: k3-am65-mcu: Add MCU domain R5F cluster node Suman Anna
2020-10-29  3:37 ` [PATCH 2/8] arm64: dts: ti: k3-am654-base-board: Add mailboxes to R5Fs Suman Anna
2020-10-29  3:37 ` [PATCH 3/8] arm64: dts: ti: k3-am654-base-board: Add DDR carveout memory nodes for R5Fs Suman Anna
2020-10-29  3:37 ` [PATCH 4/8] arm64: dts: ti: k3-am654-base-board: Reserve memory for IPC between R5F cores Suman Anna
2020-10-29  3:37 ` [PATCH 5/8] arm64: dts: ti: k3-j721e-mcu: Add MCU domain R5F cluster node Suman Anna
2020-10-29  3:38 ` [PATCH 6/8] arm64: dts: ti: k3-j721e-main: Add MAIN domain R5F cluster nodes Suman Anna
2020-10-29  3:38 ` [PATCH 7/8] arm64: dts: ti: k3-j721e-som-p0: Add mailboxes to R5Fs Suman Anna
2020-10-29  3:38 ` [PATCH 8/8] arm64: dts: ti: k3-j721e-som-p0: Add DDR carveout memory nodes for R5Fs Suman Anna
2020-11-06 11:43 ` [PATCH 0/8] Add R5F nodes on TI K3 AM65x and J721E SoCs Lokesh Vutla
2020-11-06 14:26   ` Suman Anna [this message]
2020-11-12 17:48 ` Nishanth Menon
2020-11-12 18:56   ` Suman Anna

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=f0caafff-9825-ae7b-cffd-69efdcb8982b@ti.com \
    --to=s-anna@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=t-kristo@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).