From: Rosen Penev <rosenp@gmail.com>
To: devicetree@vger.kernel.org
Cc: "Florian Fainelli" <florian.fainelli@broadcom.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM5301X ARM ARCHITECTURE),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCHv2 0/4] ARM: dts: BCM5301X: add WAN MAC assignments
Date: Wed, 25 Feb 2026 15:08:23 -0800 [thread overview]
Message-ID: <20260225230827.21715-1-rosenp@gmail.com> (raw)
These are used to specify the proper WAN MAC in dts instead of having to
handle in userspace.
v2: remove commits with switch overrides.
Rosen Penev (4):
ARM: dts: BCM5301X: EA9200: set WAN MAC from nvram
ARM: dts: BCM5301X: panamera: set WAN MAC from nvram
ARM: dts: BCM5301X: AC3100: set WAN MAC from nvram
ARM: dts: BCM5301X: AC5300: set WAN MAC from nvram
arch/arm/boot/dts/broadcom/bcm4709-linksys-ea9200.dts | 7 +++++++
arch/arm/boot/dts/broadcom/bcm47094-asus-rt-ac3100.dtsi | 7 +++++++
arch/arm/boot/dts/broadcom/bcm47094-asus-rt-ac5300.dts | 3 +++
arch/arm/boot/dts/broadcom/bcm47094-linksys-panamera.dts | 7 +++++++
4 files changed, 24 insertions(+)
--
2.53.0
next reply other threads:[~2026-02-25 23:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 23:08 Rosen Penev [this message]
2026-02-25 23:08 ` [PATCHv2 1/4] ARM: dts: BCM5301X: EA9200: set WAN MAC from nvram Rosen Penev
2026-03-16 20:43 ` Florian Fainelli
2026-02-25 23:08 ` [PATCHv2 2/4] ARM: dts: BCM5301X: panamera: " Rosen Penev
2026-03-16 20:44 ` Florian Fainelli
2026-02-25 23:08 ` [PATCHv2 3/4] ARM: dts: BCM5301X: AC3100: " Rosen Penev
2026-03-16 20:44 ` Florian Fainelli
2026-02-25 23:08 ` [PATCHv2 4/4] ARM: dts: BCM5301X: AC5300: " Rosen Penev
2026-02-26 10:29 ` kernel test robot
2026-03-16 20:44 ` Florian Fainelli
2026-03-16 21:09 ` Rosen Penev
2026-03-16 21:11 ` Florian Fainelli
2026-03-16 21:13 ` Rosen Penev
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=20260225230827.21715-1-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=linux-kernel@vger.kernel.org \
--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