devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Edwards <cfsworks@gmail.com>
To: "Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"William Zhang" <william.zhang@broadcom.com>,
	"Anand Gore" <anand.gore@broadcom.com>,
	"Kursad Oney" <kursad.oney@broadcom.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Sam Edwards <CFSworks@gmail.com>
Subject: [PATCH 3/3] arm64: dts: broadcom: bcmbca: bcm4908: Fix Netgear R8000P partitioning
Date: Wed,  9 Oct 2024 14:50:46 -0700	[thread overview]
Message-ID: <20241009215046.1449389-4-CFSworks@gmail.com> (raw)
In-Reply-To: <20241009215046.1449389-1-CFSworks@gmail.com>

As we have just modified the DT schema for BCM4908 partitioning in order
to accommodate `nvmem-cells` partitions, the workaround of using
`fixed-partitions` is no longer necessary to pass the DT check. Promote
this partition table to full-blown BCM4908 active-partition detection
and remove an inappropriate `ranges` property, thus fully complying with
the schema.

Signed-off-by: Sam Edwards <CFSworks@gmail.com>
---
 .../arm64/boot/dts/broadcom/bcmbca/bcm4906-netgear-r8000p.dts | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-netgear-r8000p.dts b/arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-netgear-r8000p.dts
index 999d93730240..23adcfd52843 100644
--- a/arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-netgear-r8000p.dts
+++ b/arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-netgear-r8000p.dts
@@ -139,7 +139,7 @@ &nandcs {
 	#size-cells = <0>;
 
 	partitions {
-		compatible = "fixed-partitions";
+		compatible = "brcm,bcm4908-partitions";
 		#address-cells = <1>;
 		#size-cells = <1>;
 
@@ -150,7 +150,6 @@ partition@0 {
 
 			#address-cells = <1>;
 			#size-cells = <1>;
-			ranges = <0 0x0 0x100000>;
 
 			base_mac_addr: mac@106a0 {
 				reg = <0x106a0 0x6>;
@@ -159,7 +158,6 @@ base_mac_addr: mac@106a0 {
 
 		partition@100000 {
 			compatible = "brcm,bcm4908-firmware";
-			label = "firmware";
 			reg = <0x100000 0x4400000>;
 		};
 	};
-- 
2.44.2


      parent reply	other threads:[~2024-10-09 21:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 21:50 [PATCH 0/3] Resolve BCMBCA DT validation errors Sam Edwards
2024-10-09 21:50 ` [PATCH 1/3] dt-bindings: mtd: Relax BCM4908 partition schema Sam Edwards
2024-10-10  2:06   ` Rob Herring (Arm)
2024-10-10  2:38   ` Rob Herring
2024-10-10  3:37     ` Sam Edwards
2024-10-09 21:50 ` [PATCH 2/3] arm64: dts: broadcom: bcmbca: bcm4908: Fix Asus GT-AC5300's cferom partition Sam Edwards
2024-10-09 21:50 ` Sam Edwards [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=20241009215046.1449389-4-CFSworks@gmail.com \
    --to=cfsworks@gmail.com \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=krzk+dt@kernel.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=robh@kernel.org \
    --cc=william.zhang@broadcom.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).