Devicetree
 help / color / mirror / Atom feed
From: Rosen Penev <rosenp@gmail.com>
To: "Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Hauke Mehrtens" <hauke@hauke-m.de>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>
Cc: "Broadcom internal kernel review list"
	<bcm-kernel-feedback-list@broadcom.com>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v2 05/22] ARM: dts: BCM5301X: EA6300: set gmac2 MAC address from nvram
Date: Thu, 19 Nov 2026 00:54:35 -0800	[thread overview]
Message-ID: <20261119085452.75708-6-rosenp@gmail.com> (raw)
In-Reply-To: <20261119085452.75708-1-rosenp@gmail.com>

Describe the et0macaddr nvram cell and assign it to gmac2, so the MAC
address doesn't have to be set from userspace.

gmac2 connects to switch port 8, the switch's IMP port, which the next
patch makes the only CPU port.

Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
 arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6300-v1.dts | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6300-v1.dts b/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6300-v1.dts
index 03d5546a147c..f8dd08cc7cca 100644
--- a/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6300-v1.dts
+++ b/arch/arm/boot/dts/broadcom/bcm4708-linksys-ea6300-v1.dts
@@ -24,6 +24,10 @@ memory@0 {
 	nvram@1c080000 {
 		compatible = "brcm,nvram";
 		reg = <0x1c080000 0x180000>;
+
+		et0macaddr: et0macaddr {
+			#nvmem-cell-cells = <1>;
+		};
 	};
 
 	gpio-keys {
@@ -50,3 +54,8 @@ &usb3_phy {
 &usb3 {
 	vcc-gpio = <&chipcommon 10 GPIO_ACTIVE_HIGH>;
 };
+
+&gmac2 {
+	nvmem-cells = <&et0macaddr 0>;
+	nvmem-cell-names = "mac-address";
+};
-- 
2.56.1


  parent reply	other threads:[~2026-11-19  8:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  8:54 [PATCH v2 00/22] ARM: dts: BCM5301X: describe switches and use gmac2 as the CPU port Rosen Penev
2026-11-19  8:54 ` [PATCH v2 01/22] ARM: dts: BCM5301X: AC56U: specify switch Rosen Penev
2026-11-19  8:54 ` [PATCH v2 02/22] ARM: dts: BCM5301X: AC68U: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 03/22] ARM: dts: BCM5301X: N18U: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 04/22] ARM: dts: BCM5301X: R7000: " Rosen Penev
2026-11-19  8:54 ` Rosen Penev [this message]
2026-11-19  8:54 ` [PATCH v2 06/22] ARM: dts: BCM5301X: EA6300: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 07/22] ARM: dts: BCM5301X: phicomm-k3: add nvram node Rosen Penev
2026-11-19  8:54 ` [PATCH v2 08/22] ARM: dts: BCM5301X: phicomm-k3: specify switch Rosen Penev
2026-11-19  8:54 ` [PATCH v2 09/22] ARM: dts: BCM5301X: R6300 v2: add nvram node Rosen Penev
2026-11-19  8:54 ` [PATCH v2 10/22] ARM: dts: BCM5301X: R6300 v2: specify switch Rosen Penev
2026-11-19  8:54 ` [PATCH v2 11/22] ARM: dts: BCM5301X: EA6500 v2: add nvram node Rosen Penev
2026-11-19  8:54 ` [PATCH v2 12/22] ARM: dts: BCM5301X: EA6500 v2: specify switch Rosen Penev
2026-11-19  8:54 ` [PATCH v2 13/22] ARM: dts: BCM5301X: R8500: add nvram node Rosen Penev
2026-11-19  8:54 ` [PATCH v2 14/22] ARM: dts: BCM5301X: R8500: specify switch Rosen Penev
2026-11-19  8:54 ` [PATCH v2 15/22] ARM: dts: BCM5301X: WZR-900DHP: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 16/22] ARM: dts: BCM5301X: WZR-1750DHP: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 17/22] ARM: dts: BCM5301X: WXR-1900DHP: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 18/22] ARM: dts: BCM5301X: Archer C5 v2: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 19/22] ARM: dts: BCM5301X: Archer C9 v1: " Rosen Penev
2026-11-19  8:54 ` [PATCH v2 20/22] ARM: dts: BCM5301X: DIR-885L: use gmac2 Rosen Penev
2026-11-19  8:54 ` [PATCH v2 21/22] ARM: dts: BCM5301X: use gmac2 as the CPU port Rosen Penev
2026-11-19  8:54 ` [PATCH v2 22/22] ARM: dts: BCM5301X: enable GMACs in boards that use them Rosen Penev
2026-11-19  9:13   ` sashiko-bot

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=20261119085452.75708-6-rosenp@gmail.com \
    --to=rosenp@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=hauke@hauke-m.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rafal@milecki.pl \
    --cc=robh@kernel.org \
    --cc=zajec5@gmail.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