From: Artem Novak <artem122novak@gmail.com>
To: florian.fainelli@broadcom.com
Cc: bcm-kernel-feedback-list@broadcom.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org, robh@kernel.org,
Artem Novak <artem122novak@gmail.com>
Subject: [PATCH 0/2] ARM: dts: bcm2835: replace deprecated LED fragment
Date: Sun, 22 Nov 2026 03:52:23 -0600 [thread overview]
Message-ID: <20261122095225.200916-1-artem122novak@gmail.com> (raw)
The Raspberry Pi Zero and Model B device trees include the deprecated
bcm283x-rpi-led-deprecated.dtsi fragment to define their ACT LEDs.
Replace the fragment with board-local gpio-leds nodes, preserving the
existing GPIO assignments, polarity, default state, and heartbeat
trigger.
The changes are split into separate patches for each board.
Artem Novak (2):
ARM: dts: bcm2835: replace deprecated LED fragment on Raspberry Pi
Zero
ARM: dts: bcm2835: replace deprecated LED fragment on Raspberry Pi
Model B
arch/arm/boot/dts/broadcom/bcm2835-rpi-b.dts | 14 +++++++++++---
arch/arm/boot/dts/broadcom/bcm2835-rpi-zero.dts | 14 +++++++++++---
2 files changed, 22 insertions(+), 6 deletions(-)
--
2.56.1
next reply other threads:[~2026-11-22 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 9:52 Artem Novak [this message]
2026-11-22 9:52 ` [PATCH 1/2] ARM: dts: bcm2835: replace deprecated LED fragment on Raspberry Pi Zero Artem Novak
2026-11-22 9:52 ` [PATCH 2/2] ARM: dts: bcm2835: replace deprecated LED fragment on Raspberry Pi Model B Artem Novak
2026-11-22 10:17 ` [PATCH v2 0/2] ARM: dts: bcm2835: replace deprecated LED fragment Artem Novak
2026-11-22 10:17 ` [PATCH v2 1/2] ARM: dts: bcm2835: replace deprecated LED fragment on Raspberry Pi Zero Artem Novak
2026-11-22 10:17 ` [PATCH v2 2/2] ARM: dts: bcm2835: replace deprecated LED fragment on Raspberry Pi Model B Artem Novak
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=20261122095225.200916-1-artem122novak@gmail.com \
--to=artem122novak@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=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=robh@kernel.org \
/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