From: Andrew Gaylard <ag@ffroot.co.za>
To: qinjian@cqplus1.com, linux-arm-kernel@lists.infradead.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux@armlinux.org.uk, devicetree@vger.kernel.org,
Andrew Gaylard <ag@ffroot.co.za>
Subject: [PATCH 0/2] arm: sunplus: add SP7021 LTPP3G2 board support
Date: Wed, 2 Sep 2026 12:45:43 +0200 [thread overview]
Message-ID: <20260902104545.67794-1-ag@ffroot.co.za> (raw)
This series adds device tree support for the Tibbo LTPP3G2 board, which
is based on the Sunplus SP7021 SoC (quad-core ARM Cortex-A7).
Patch 1 adds peripheral device nodes to the SP7021 SoC DTSI for
peripherals whose drivers are already upstream: PWM, watchdog, eMMC,
and the L2SW Ethernet switch.
Patch 2 adds a DTS for the LTPP3G2 board itself, enabling those
peripherals and configuring the board-specific pinmux and Ethernet
topology. It also updates the defconfig to enable the relevant drivers.
Tested on the Tibbo LTPP3G2 board with linux-next 20260901.
Andrew Gaylard (2):
arm: dts: sunplus: add peripheral device nodes to sp7021.dtsi
arm: sunplus: add Tibbo LTPP3G2 board support; update defconfig
arch/arm/boot/dts/sunplus/Makefile | 5 +-
.../dts/sunplus/sunplus-sp7021-ltpp3g2.dts | 301 ++++++++++++++++++
arch/arm/boot/dts/sunplus/sunplus-sp7021.dtsi | 48 +++
arch/arm/configs/sp7021_defconfig | 30 ++
4 files changed, 381 insertions(+), 3 deletions(-)
create mode 100644 arch/arm/boot/dts/sunplus/sunplus-sp7021-ltpp3g2.dts
--
2.53.0
next reply other threads:[~2026-09-02 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 10:45 Andrew Gaylard [this message]
2026-09-02 10:45 ` [PATCH 1/2] arm: dts: sunplus: add peripheral device nodes to sp7021.dtsi Andrew Gaylard
2026-09-02 10:58 ` sashiko-bot
2026-09-02 10:45 ` [PATCH 2/2] arm: sunplus: add Tibbo LTPP3G2 board support; update defconfig Andrew Gaylard
2026-09-02 11:00 ` sashiko-bot
2026-09-02 15:40 ` [PATCH 0/2] arm: sunplus: add SP7021 LTPP3G2 board support -- withdrawn Andrew Gaylard
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=20260902104545.67794-1-ag@ffroot.co.za \
--to=ag@ffroot.co.za \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=qinjian@cqplus1.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.