U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Schultz <d.schultz@phytec.de>
To: <w.egorov@phytec.de>, <trini@konsulko.com>,
	<ggiordano@phytec.com>, <u-boot@lists.denx.de>
Cc: <nm@ti.com>, <n-francis@ti.com>, <nmorrisson@phytec.com>,
	<d-gole@ti.com>,  <m.otto@phytec.de>, <bb@ti.com>,
	<upstream@lists.phytec.de>, Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH 2/4] board: Phytec: phycore_am6*: Add k3 Kconfig to A53
Date: Thu, 6 Feb 2025 22:51:20 -0800	[thread overview]
Message-ID: <20250207065122.2495923-3-d.schultz@phytec.de> (raw)
In-Reply-To: <20250207065122.2495923-1-d.schultz@phytec.de>

Add board/phytec/common/k3/Kconfig to the A53 builds to make
the PHYTEC_K3_ configs visible for this defconfig.

This patch also adds .../k3/Kconfig to the AM64x R5 build for the
same reason.

Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
 board/phytec/phycore_am62ax/Kconfig | 1 +
 board/phytec/phycore_am62x/Kconfig  | 1 +
 board/phytec/phycore_am64x/Kconfig  | 2 ++
 3 files changed, 4 insertions(+)

diff --git a/board/phytec/phycore_am62ax/Kconfig b/board/phytec/phycore_am62ax/Kconfig
index 516dc8e2020..81f2311ec97 100644
--- a/board/phytec/phycore_am62ax/Kconfig
+++ b/board/phytec/phycore_am62ax/Kconfig
@@ -15,6 +15,7 @@ config SYS_CONFIG_NAME
        default "phycore_am62ax"
 
 source "board/phytec/common/Kconfig"
+source "board/phytec/common/k3/Kconfig"
 
 endif
 
diff --git a/board/phytec/phycore_am62x/Kconfig b/board/phytec/phycore_am62x/Kconfig
index ecee5873c0c..6c2eb82787e 100644
--- a/board/phytec/phycore_am62x/Kconfig
+++ b/board/phytec/phycore_am62x/Kconfig
@@ -15,6 +15,7 @@ config SYS_CONFIG_NAME
        default "phycore_am62x"
 
 source "board/phytec/common/Kconfig"
+source "board/phytec/common/k3/Kconfig"
 
 endif
 
diff --git a/board/phytec/phycore_am64x/Kconfig b/board/phytec/phycore_am64x/Kconfig
index 829526c3295..ddfb4a39989 100644
--- a/board/phytec/phycore_am64x/Kconfig
+++ b/board/phytec/phycore_am64x/Kconfig
@@ -18,6 +18,7 @@ config SYS_CONFIG_NAME
        default "phycore_am64x"
 
 source "board/phytec/common/Kconfig"
+source "board/phytec/common/k3/Kconfig"
 
 endif
 
@@ -33,5 +34,6 @@ config SYS_CONFIG_NAME
        default "phycore_am64x"
 
 source "board/phytec/common/Kconfig"
+source "board/phytec/common/k3/Kconfig"
 
 endif
-- 
2.25.1


  parent reply	other threads:[~2025-02-07  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07  6:51 [PATCH 0/4] phyCORE-AM62x/AM64x: Sign Images with External Keys Daniel Schultz
2025-02-07  6:51 ` [PATCH 1/4] board: phytec: common: k3: Introduce Configs to Sign Images Daniel Schultz
2025-02-07 17:07   ` Andrew Davis
2025-02-10  7:40     ` Daniel Schultz
2025-02-07  6:51 ` Daniel Schultz [this message]
2025-02-07  6:51 ` [PATCH 3/4] arch: arm: dts: k3-am625-phycore-som-binman: Add custMpk and ti-degenerate keys with CONFIG entries Daniel Schultz
2025-02-07  6:51 ` [PATCH 4/4] arch: arm: dts: k3-am642-phycore-som-binman: " Daniel Schultz

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=20250207065122.2495923-3-d.schultz@phytec.de \
    --to=d.schultz@phytec.de \
    --cc=bb@ti.com \
    --cc=d-gole@ti.com \
    --cc=ggiordano@phytec.com \
    --cc=m.otto@phytec.de \
    --cc=n-francis@ti.com \
    --cc=nm@ti.com \
    --cc=nmorrisson@phytec.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=upstream@lists.phytec.de \
    --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