From: Paul Barker <paul.barker@sancloud.com>
To: Tom Rini <trini@konsulko.com>,
Peter Robinson <pbrobinson@gmail.com>,
Lokesh Vutla <lokeshvutla@ti.com>
Cc: Paul Barker <paul.barker@sancloud.com>, u-boot@lists.denx.de
Subject: [PATCH v2 0/5] Resync BeagleBone dtbs, add SanCloud BBE support & minor fixups
Date: Mon, 12 Jul 2021 21:14:07 +0100 [thread overview]
Message-ID: <20210712201412.13306-1-paul.barker@sancloud.com> (raw)
This updated patch series takes the approach of copying the device trees
for the BeagleBone Black, BeagleBone Green & BeagleBone enhanced from
the latest stable Linux kernel (v5.13.1). To support this we also need
to port over a couple of changes to the relevant dt-bindings headers.
I considered also copying the newer versions of am33xx*.dtsi but this
resulted in significant churn and incompatibility with some of the other
devicetrees in the u-boot tree.
With the new device trees in place we enable GbE phy support and fix the
DTB ordering in the am335x evm defconfig. These two patches are
unchanged from the v1 series previously sent to the list.
With these changes applied, Ethernet works on the SanCloud BBE in
u-boot.
These changes have been tested on both a SanCloud BBE and on a
BeagleBone Black. In both cases it was confirmed that Ethernet worked in
u-boot and that we could successfully boot a Linux kernel & rootfs built
with Yocto Project.
Paul Barker (5):
dt-bindings: Resync omap & am33xx pinctrl bindings
arm: dts: Resync BeagleBone device trees
arm: dts: Import am335x-sancloud-bbe devicetree
configs: am335x_evm: Support GbE PHYs
configs: am335x_evm: Fix BeagleBone Green DTB selection
arch/arm/dts/Makefile | 1 +
arch/arm/dts/am335x-bone-common.dtsi | 185 +++++++++---------
arch/arm/dts/am335x-bone.dts | 7 +-
arch/arm/dts/am335x-boneblack-common.dtsi | 169 +++++++++++++++++
arch/arm/dts/am335x-boneblack.dts | 217 +++++++++++++++-------
arch/arm/dts/am335x-bonegreen-common.dtsi | 41 ++++
arch/arm/dts/am335x-bonegreen.dts | 49 +----
arch/arm/dts/am335x-sancloud-bbe.dts | 137 ++++++++++++++
board/ti/am335x/board.c | 2 +
configs/am335x_evm_defconfig | 3 +-
include/dt-bindings/pinctrl/am33xx.h | 131 ++++++++++++-
include/dt-bindings/pinctrl/omap.h | 11 +-
12 files changed, 730 insertions(+), 223 deletions(-)
create mode 100644 arch/arm/dts/am335x-boneblack-common.dtsi
create mode 100644 arch/arm/dts/am335x-bonegreen-common.dtsi
create mode 100644 arch/arm/dts/am335x-sancloud-bbe.dts
base-commit: 490101a5e5df65238b900b21b81361bc4b13da2e
--
2.26.2
next reply other threads:[~2021-07-12 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 20:14 Paul Barker [this message]
2021-07-12 20:14 ` [PATCH v2 1/5] dt-bindings: Resync omap & am33xx pinctrl bindings Paul Barker
2021-07-12 20:14 ` [PATCH v2 2/5] arm: dts: Resync BeagleBone device trees Paul Barker
2021-07-12 20:14 ` [PATCH v2 3/5] arm: dts: Import am335x-sancloud-bbe devicetree Paul Barker
2021-07-12 20:14 ` [PATCH v2 4/5] configs: am335x_evm: Support GbE PHYs Paul Barker
2021-07-12 20:14 ` [PATCH v2 5/5] configs: am335x_evm: Fix BeagleBone Green DTB selection Paul Barker
2021-07-13 6:29 ` Lokesh Vutla
2021-07-20 8:19 ` Paul Barker
2021-07-21 5:59 ` Lokesh Vutla
2021-07-21 6:40 ` Paul Barker
2021-07-26 7:11 ` Lokesh Vutla
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=20210712201412.13306-1-paul.barker@sancloud.com \
--to=paul.barker@sancloud.com \
--cc=lokeshvutla@ti.com \
--cc=pbrobinson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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