From: Paul Barker <paul.barker@sancloud.com>
To: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Cc: Paul Barker <paul.barker@sancloud.com>
Subject: [PATCH 4/4] configs: am335x_evm: Fix BeagleBone Green DTB selection
Date: Thu, 17 Jun 2021 10:02:22 +0100 [thread overview]
Message-ID: <20210617090222.7516-4-paul.barker@sancloud.com> (raw)
In-Reply-To: <20210617090222.7516-1-paul.barker@sancloud.com>
The function board_is_bone_lt() returns true for the BeagleBone Green,
the BeagleBone Enhanced and the BeagleBone Black. Therefore when
selecting which devicetree to use we must ensure that the more specific
functions board_is_bbg1() and board_is_bben() are checked first
otherwise all three devices would end up using the am335x-boneblack
devicetree. This can be achieved by placing the relevant devicetree
names (am335x-sancloud-bbe and am335x-bonegreen) before am335x-boneblack
in CONFIG_OF_LIST.
The new am335x-sancloud-bbe name is already in an appropriate place in
the list so we just need to move am335x-bonegreen.
Signed-off-by: Paul Barker <paul.barker@sancloud.com>
---
configs/am335x_evm_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
index 7a372095a3..82674ac82f 100644
--- a/configs/am335x_evm_defconfig
+++ b/configs/am335x_evm_defconfig
@@ -37,7 +37,7 @@ CONFIG_MTDIDS_DEFAULT="nand0=nand.0"
CONFIG_MTDPARTS_DEFAULT="mtdparts=nand.0:128k(NAND.SPL),128k(NAND.SPL.backup1),128k(NAND.SPL.backup2),128k(NAND.SPL.backup3),256k(NAND.u-boot-spl-os),1m(NAND.u-boot),128k(NAND.u-boot-env),128k(NAND.u-boot-env.backup1),8m(NAND.kernel),-(NAND.file-system)"
# CONFIG_SPL_EFI_PARTITION is not set
CONFIG_OF_CONTROL=y
-CONFIG_OF_LIST="am335x-evm am335x-bone am335x-sancloud-bbe am335x-boneblack am335x-evmsk am335x-bonegreen am335x-icev2 am335x-pocketbeagle"
+CONFIG_OF_LIST="am335x-evm am335x-bone am335x-sancloud-bbe am335x-bonegreen am335x-boneblack am335x-evmsk am335x-icev2 am335x-pocketbeagle"
CONFIG_ENV_OVERWRITE=y
CONFIG_SYS_RELOC_GD_ENV_ADDR=y
CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
--
2.26.2
next prev parent reply other threads:[~2021-06-17 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:02 [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config Paul Barker
2021-06-17 9:02 ` [PATCH 2/4] arm: dts: am335x-sancloud-bbe: New dtb to support ethernet Paul Barker
2021-06-17 9:02 ` [PATCH 3/4] configs: am335x_evm: Support GbE PHYs Paul Barker
2021-06-17 9:02 ` Paul Barker [this message]
2021-06-17 10:05 ` [PATCH 1/4] arm: dts: am335x-boneblack: Extract common config Peter Robinson
2021-06-17 10:31 ` Paul Barker
2021-06-17 10:35 ` Peter Robinson
2021-06-17 10:49 ` Paul Barker
2021-06-17 12:27 ` Tom Rini
2021-07-12 16:23 ` Paul Barker
2021-07-13 5:58 ` 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=20210617090222.7516-4-paul.barker@sancloud.com \
--to=paul.barker@sancloud.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