public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Andrew Davis <afd@ti.com>
Subject: [PATCH 04/11] arm64: dts: ti: k3-am654-base-board: Do not split single items
Date: Tue, 23 Jan 2024 16:25:29 -0600	[thread overview]
Message-ID: <20240123222536.875797-4-afd@ti.com> (raw)
In-Reply-To: <20240123222536.875797-1-afd@ti.com>

Each "mboxes" item is composed of two cells. It seems these got split
as they appeared to be two items in an array, but are actually a single
two-cell item. Rejoin these cells.

Signed-off-by: Andrew Davis <afd@ti.com>
---
 arch/arm64/boot/dts/ti/k3-am654-base-board.dts | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
index 822c288d27976..71c8e035c3eb9 100644
--- a/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
+++ b/arch/arm64/boot/dts/ti/k3-am654-base-board.dts
@@ -531,13 +531,13 @@ mbox_mcu_r5fss0_core1: mbox-mcu-r5fss0-core1 {
 &mcu_r5fss0_core0 {
 	memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
 			<&mcu_r5fss0_core0_memory_region>;
-	mboxes = <&mailbox0_cluster0>, <&mbox_mcu_r5fss0_core0>;
+	mboxes = <&mailbox0_cluster0 &mbox_mcu_r5fss0_core0>;
 };
 
 &mcu_r5fss0_core1 {
 	memory-region = <&mcu_r5fss0_core1_dma_memory_region>,
 			<&mcu_r5fss0_core1_memory_region>;
-	mboxes = <&mailbox0_cluster1>, <&mbox_mcu_r5fss0_core1>;
+	mboxes = <&mailbox0_cluster1 &mbox_mcu_r5fss0_core1>;
 };
 
 &ospi0 {
-- 
2.39.2


  parent reply	other threads:[~2024-01-23 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 22:25 [PATCH 01/11] arm64: dts: ti: k3-am642-evm: Do not split single items Andrew Davis
2024-01-23 22:25 ` [PATCH 02/11] arm64: dts: ti: k3-am642-sk: " Andrew Davis
2024-01-23 22:25 ` [PATCH 03/11] arm64: dts: ti: iot2050: " Andrew Davis
2024-01-23 22:25 ` Andrew Davis [this message]
2024-01-23 22:25 ` [PATCH 05/11] arm64: dts: ti: k3-am68-sk-som: " Andrew Davis
2024-01-23 22:25 ` [PATCH 06/11] arm64: dts: ti: k3-am69-sk: " Andrew Davis
2024-01-23 22:25 ` [PATCH 07/11] arm64: dts: ti: k3-j7200-som-p0: " Andrew Davis
2024-01-23 22:25 ` [PATCH 08/11] arm64: dts: ti: k3-j721e-beagleboneai64: " Andrew Davis
2024-01-23 22:25 ` [PATCH 09/11] arm64: dts: ti: k3-j721e-sk: " Andrew Davis
2024-01-23 22:25 ` [PATCH 10/11] arm64: dts: ti: k3-j721e-som-p0: " Andrew Davis
2024-01-23 22:25 ` [PATCH 11/11] arm64: dts: ti: k3-j721s2-som-p0: " Andrew Davis
2024-02-06  4:33 ` [PATCH 01/11] arm64: dts: ti: k3-am642-evm: " 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=20240123222536.875797-4-afd@ti.com \
    --to=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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