From: Roger Quadros <rogerq@kernel.org>
To: Joe Hershberger <joe.hershberger@ni.com>,
Ramon Fried <rfried.dev@gmail.com>,
Tom Rini <trini@konsulko.com>, Nishanth Menon <nm@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
Wadim Egorov <w.egorov@phytec.de>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Simon Glass <sjg@chromium.org>
Cc: srk@ti.com, s-vadapalli@ti.com, vigneshr@ti.com,
r-gunasekaran@ti.com, danishanwar@ti.com, u-boot@lists.denx.de,
Roger Quadros <rogerq@kernel.org>
Subject: [PATCH 0/3] arm: dts: am62-beagleplay: Fix Beagleplay Ethernet
Date: Thu, 25 Apr 2024 15:20:51 +0300 [thread overview]
Message-ID: <20240425-for-2024-07-beagleplay-eth-v1-0-6c985de1c316@kernel.org> (raw)
Sync AM62 device tree files with Linux v6.9-rc5 and
add in the missing bits in -u-boot.dtsi to get CPSW
Ethernet working.
The last patch is marked [not-for-merge] as it is not yet
applied to Linux device tree.
CI testing
https://github.com/u-boot/u-boot/pull/527
Signed-off-by: Roger Quadros <rogerq@kernel.org>
---
---
Roger Quadros (3):
arm: dts: k3-am62*: sync with Linux v6.9-rc5
arm: dts: k3-am625-beagleplay: get CPSW Ethernet to work
[not-for-merge] arm: dts: k3-am625-beagleplay: Fix Ethernet PHY reset GPIO
arch/arm/dts/k3-am62-main.dtsi | 126 ++++++++++++++---
arch/arm/dts/k3-am62-mcu.dtsi | 4 +-
arch/arm/dts/k3-am62-phycore-som.dtsi | 5 +-
arch/arm/dts/k3-am62-thermal.dtsi | 5 +-
arch/arm/dts/k3-am62-wakeup.dtsi | 38 +++--
arch/arm/dts/k3-am62.dtsi | 4 +-
arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi | 63 +++++++++
arch/arm/dts/k3-am625-beagleplay.dts | 66 ++++-----
arch/arm/dts/k3-am625-phyboard-lyra-rdk.dts | 104 +++++++++++++-
arch/arm/dts/k3-am625-sk.dts | 4 +-
arch/arm/dts/k3-am625.dtsi | 4 +-
arch/arm/dts/k3-am62a-main.dtsi | 201 +++++++++++++++++++++++++--
arch/arm/dts/k3-am62a-mcu.dtsi | 4 +-
arch/arm/dts/k3-am62a-thermal.dtsi | 5 +-
arch/arm/dts/k3-am62a-wakeup.dtsi | 4 +-
arch/arm/dts/k3-am62a.dtsi | 4 +-
arch/arm/dts/k3-am62a7-sk.dts | 162 ++++++++++++++++++++-
arch/arm/dts/k3-am62a7.dtsi | 4 +-
arch/arm/dts/k3-am62x-sk-common.dtsi | 24 +++-
19 files changed, 722 insertions(+), 109 deletions(-)
---
base-commit: 38ea74d6d5c05224acdb03f799897c1bdd56f8cc
change-id: 20240305-for-2024-07-beagleplay-eth-f82a51197937
Best regards,
--
Roger Quadros <rogerq@kernel.org>
next reply other threads:[~2024-04-25 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:20 Roger Quadros [this message]
2024-04-25 12:20 ` [PATCH 1/3] arm: dts: k3-am62*: sync with Linux v6.9-rc5 Roger Quadros
2024-04-25 12:20 ` [PATCH 2/3] arm: dts: k3-am625-beagleplay: get CPSW Ethernet to work Roger Quadros
2024-04-25 12:20 ` [PATCH not-for-merge 3/3] arm: dts: k3-am625-beagleplay: Fix Ethernet PHY reset GPIO Roger Quadros
2024-05-10 9:55 ` [PATCH 0/3] arm: dts: am62-beagleplay: Fix Beagleplay Ethernet Roger Quadros
2024-05-10 13:08 ` Tom Rini
2024-05-10 19:24 ` Roger Quadros
2024-05-10 19:33 ` Tom Rini
2024-05-10 19:58 ` Nishanth Menon
2024-05-10 20:00 ` Tom Rini
2024-05-10 20:01 ` Tom Rini
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=20240425-for-2024-07-beagleplay-eth-v1-0-6c985de1c316@kernel.org \
--to=rogerq@kernel.org \
--cc=danishanwar@ti.com \
--cc=joe.hershberger@ni.com \
--cc=marcel.ziswiler@toradex.com \
--cc=nm@ti.com \
--cc=r-gunasekaran@ti.com \
--cc=rfried.dev@gmail.com \
--cc=robertcnelson@gmail.com \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=srk@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).