From: Bryan Brattlof <bb@ti.com>
To: Tom Rini <trini@konsulko.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Hari Nagalla <hnagalla@ti.com>, Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Cc: UBoot Mailing List <u-boot@lists.denx.de>,
Andrew Davis <afd@ti.com>, Nishanth Menon <nm@ti.com>,
Bryan Brattlof <bb@ti.com>
Subject: [PATCH 04/11] arm: mach-k3: invert logic for split DM firmware config
Date: Thu, 12 Oct 2023 18:06:21 -0500 [thread overview]
Message-ID: <20231012230616.2101992-17-bb@ti.com> (raw)
In-Reply-To: <20231012230616.2101992-13-bb@ti.com>
Currently for the K3 generation of SoCs there are more SoCs that utilize
the split firmware approach than the combined DMSC firmware. Invert the
logic to avoid adding more and more SoCs to this list.
Signed-off-by: Bryan Brattlof <bb@ti.com>
---
arch/arm/mach-k3/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-k3/Kconfig b/arch/arm/mach-k3/Kconfig
index 9168bf842dcaf..9a211871e04ef 100644
--- a/arch/arm/mach-k3/Kconfig
+++ b/arch/arm/mach-k3/Kconfig
@@ -172,7 +172,7 @@ config K3_ATF_LOAD_ADDR
config K3_DM_FW
bool "Separate DM firmware image"
- depends on SPL && CPU_V7R && (SOC_K3_J721E || SOC_K3_J721S2 || SOC_K3_AM625 || SOC_K3_AM62A7) && !CLK_TI_SCI && !TI_SCI_POWER_DOMAIN
+ depends on SPL && CPU_V7R && !(SOC_K3_AM642S || SOC_K3_AM654) && !CLK_TI_SCI && !TI_SCI_POWER_DOMAIN
default y
help
Enabling this will indicate that the system has separate DM
--
2.42.0
next prev parent reply other threads:[~2023-10-12 23:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 23:06 [PATCH 00/11] Introduce basic support for TI's AM62Px SoC family Bryan Brattlof
2023-10-12 23:06 ` [PATCH 01/11] soc: add info to identify the am62p " Bryan Brattlof
2023-10-12 23:06 ` [PATCH 02/11] arm: mach-k3: am62px: introduce clock and device files for wkup spl Bryan Brattlof
2023-10-12 23:06 ` [PATCH 03/11] ram: k3-ddrss: enable the am62ax's DDR controller for am62px Bryan Brattlof
2023-10-12 23:06 ` Bryan Brattlof [this message]
2023-10-13 1:24 ` [PATCH 04/11] arm: mach-k3: invert logic for split DM firmware config Bryan Brattlof
2023-10-12 23:06 ` [PATCH 05/11] arch: mach-k3: introduce basic files to support the am62px SoC family Bryan Brattlof
2023-10-13 1:28 ` Bryan Brattlof
2023-10-12 23:06 ` [PATCH 06/11] board: ti: introduce basic board files for the am62px family Bryan Brattlof
2023-10-13 12:50 ` Tom Rini
2023-10-13 16:49 ` Bryan Brattlof
2023-10-12 23:06 ` [PATCH 07/11] firmware: ti_sci_static_data: add static DMA channel data Bryan Brattlof
2023-10-12 23:06 ` [PATCH 08/11] arm: dts: add am62p5 dtbs from linux Bryan Brattlof
2023-10-12 23:06 ` [PATCH 09/11] arm: dts: introduce am62p5 uboot dts files Bryan Brattlof
2023-10-12 23:06 ` [PATCH 10/11] configs: introduce configs needed for the am62px Bryan Brattlof
2023-10-12 23:06 ` [PATCH 11/11] doc: board: ti: introduce am62px documentation Bryan Brattlof
2023-10-16 15:52 ` [PATCH 00/11] Introduce basic support for TI's AM62Px SoC family Nishanth Menon
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=20231012230616.2101992-17-bb@ti.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=hnagalla@ti.com \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=nm@ti.com \
--cc=seanga2@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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