From: Andrew Davis <afd@ti.com>
To: Bryan Brattlof <bb@ti.com>, Tom Rini <trini@konsulko.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Hari Nagalla <hnagalla@ti.com>
Cc: Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Simon Glass <sjg@chromium.org>,
Sumit Garg <sumit.garg@linaro.org>, Nishanth Menon <nm@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
UBoot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH v2 05/13] arm: mach-k3: invert logic for split DM firmware config
Date: Fri, 2 Feb 2024 10:44:48 -0600 [thread overview]
Message-ID: <b7e61559-4f23-4da4-8ba5-e95994475672@ti.com> (raw)
In-Reply-To: <20240201030634.1120963-22-bb@ti.com>
On 1/31/24 9:06 PM, Bryan Brattlof wrote:
> 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 03898424c9546..0574e81075e6d 100644
> --- a/arch/arm/mach-k3/Kconfig
> +++ b/arch/arm/mach-k3/Kconfig
> @@ -130,7 +130,7 @@ config K3_ATF_LOAD_ADDR
>
> config K3_DM_FW
> bool "Separate DM firmware image"
> - depends on CPU_V7R && (SOC_K3_J721E || SOC_K3_J721S2 || SOC_K3_AM625 || SOC_K3_AM62A7) && !CLK_TI_SCI && !TI_SCI_POWER_DOMAIN
> + depends on CPU_V7R && ARCH_K3 && !SOC_K3_AM642 && !SOC_K3_AM654 && !CLK_TI_SCI && !TI_SCI_POWER_DOMAIN
Always amusing to see how many SoCs get added to these lists before someone
realizes there is only one or two SoCs that are not on the list :)
BTW, this whole file is inside an "if ARCH_K3" block, so all symbols
depend on ARCH_K3 automatically. You can drop that check.
Otherwise,
Acked-by: Andrew Davis <afd@ti.com>
> default y
> help
> Enabling this will indicate that the system has separate DM
next prev parent reply other threads:[~2024-02-02 16:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:06 [PATCH] arm: dts: k3-am62p5: enable the wkup i2c bus Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 00/13] Introduce basic support for TI's AM62Px SoC family Bryan Brattlof
2024-02-02 8:03 ` Sumit Garg
2024-02-02 16:36 ` Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 01/13] soc: add info to identify the am62p " Bryan Brattlof
2024-02-01 14:41 ` Igor Opaniuk
2024-02-01 3:06 ` [PATCH v2 02/13] power: domain: ti: use IS_ENABLED macro Bryan Brattlof
2024-02-01 14:46 ` Igor Opaniuk
2024-02-01 3:06 ` [PATCH v2 03/13] arm: mach-k3: am62px: introduce clock and device files for wkup spl Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 04/13] ram: k3-ddrss: enable the am62ax's DDR controller for am62px Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 05/13] arm: mach-k3: invert logic for split DM firmware config Bryan Brattlof
2024-02-02 16:44 ` Andrew Davis [this message]
2024-02-02 17:12 ` Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 06/13] arch: mach-k3: introduce basic files to support the am62px SoC family Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 07/13] board: ti: introduce basic board files for the am62px family Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 08/13] firmware: ti_sci_static_data: add static DMA channel data Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 09/13] dma: ti: k3-udma: Add DMA PSIL mappings for AM62P and J722S Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 10/13] arm: dts: introduce am62p5 uboot dts files Bryan Brattlof
2024-02-02 15:53 ` Andrew Davis
2024-02-02 16:28 ` Bryan Brattlof
2024-02-02 16:36 ` Andrew Davis
2024-02-02 17:06 ` Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 11/13] Makefile: remove hardcoded device tree source directory Bryan Brattlof
2024-02-02 7:57 ` Sumit Garg
2024-02-01 3:06 ` [PATCH v2 12/13] configs: introduce configs needed for the am62px Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 13/13] doc: board: ti: introduce am62px documentation Bryan Brattlof
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=b7e61559-4f23-4da4-8ba5-e95994475672@ti.com \
--to=afd@ti.com \
--cc=bb@ti.com \
--cc=hnagalla@ti.com \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@linaro.org \
--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