Devicetree
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] Add Mailbox nodes for TI K3 AM65x & J721E SoCs
Date: Wed, 9 Oct 2019 15:19:39 -0500	[thread overview]
Message-ID: <e27abe06-2df0-fdae-6fe5-080a40ee3bdd@ti.com> (raw)
In-Reply-To: <20190725001020.23781-1-s-anna@ti.com>

Hi Tero,

On 7/24/19 7:10 PM, Suman Anna wrote:
> Hi Tero, Nishanth,
> 
> The following series is a revised version of the series [1] that adds
> the Mailbox DT nodes and the sub-mailboxes used to communicate between
> the main MPU processor running Linux and the various R5F and DSP remote
> processors present on the TI K3 AM65x and J721E SoC families. Patches
> are based on v5.3-rc1 + the HwSpinlock DT node series [2], and are
> intended for the 5.4 merge window. Functionality is verified using a
> out-of-tree unit-test module and some additional loopback test nodes
> available here [3] for reference.
> 
> Changes in v2:
>  - All clusters are enabled by default in base dtsi files
>  - The sub-mailboxes are moved to the actual board dts files
>  - Unused clusters disabled in the board dts files

Looks like you missed picking this series up for 5.4. Can you please
pick this up for 5.5? Let me know if you want me to repost the series,
the last patch has a conflict when applying on top of 5.4-rc1 due to
some additional nodes in the board dts file.

regards
Suman

> 
> regards
> Suman
> 
> [1] https://patchwork.kernel.org/cover/11053401/
> [2] https://patchwork.kernel.org/cover/11053311/
> [3] https://github.com/sumananna/mailbox/commits/mbox/test/5.3-rc1-k3-v2
> 
> Suman Anna (4):
>   arm64: dts: ti: k3-am65-main: Add mailbox cluster nodes
>   arm64: dts: ti: k3-am65-base-board: Add IPC sub-mailbox nodes for R5Fs
>   arm64: dts: ti: k3-j721e-main: Add mailbox cluster nodes
>   arm64: dts: ti: k3-j721e-common-proc-board: Add IPC sub-mailbox nodes
> 
>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi      | 108 ++++++++++++++++++
>  .../arm64/boot/dts/ti/k3-am654-base-board.dts |  58 ++++++++++
>  .../dts/ti/k3-j721e-common-proc-board.dts     |  93 +++++++++++++++
>  arch/arm64/boot/dts/ti/k3-j721e-main.dtsi     | 108 ++++++++++++++++++
>  4 files changed, 367 insertions(+)
> 

  parent reply	other threads:[~2019-10-09 20:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25  0:10 [PATCH v2 0/4] Add Mailbox nodes for TI K3 AM65x & J721E SoCs Suman Anna
2019-07-25  0:10 ` [PATCH v2 1/4] arm64: dts: ti: k3-am65-main: Add mailbox cluster nodes Suman Anna
2019-07-25  0:10 ` [PATCH v2 2/4] arm64: dts: ti: k3-am65-base-board: Add IPC sub-mailbox nodes for R5Fs Suman Anna
2019-07-25  0:10 ` [PATCH v2 3/4] arm64: dts: ti: k3-j721e-main: Add mailbox cluster nodes Suman Anna
2019-07-25  0:10 ` [PATCH v2 4/4] arm64: dts: ti: k3-j721e-common-proc-board: Add IPC sub-mailbox nodes Suman Anna
2019-10-09 20:19 ` Suman Anna [this message]
2019-10-18 12:21   ` [PATCH v2 0/4] Add Mailbox nodes for TI K3 AM65x & J721E SoCs Tero Kristo

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=e27abe06-2df0-fdae-6fe5-080a40ee3bdd@ti.com \
    --to=s-anna@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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