All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini via U-Boot <u-boot@lists.u-boot-project.org>
To: Bryan Brattlof <bb@ti.com>
Cc: u-boot@lists.denx.de, "Peng Fan" <peng.fan@nxp.com>,
	"Alice Guo" <alice.guo@nxp.com>, "Anshul Dalal" <anshuld@ti.com>,
	"Dan Carpenter" <dan.carpenter@linaro.org>,
	"Simon Glass" <sjg@chromium.org>,
	"Alper Nebi Yasak" <alpernebiyasak@gmail.com>,
	"Andrew Davis" <afd@ti.com>, "Udit Kumar" <u-kumar1@ti.com>,
	"Quentin Schulz" <quentin.schulz@cherry.de>,
	"Kory Maincent (TI.com)" <kory.maincent@bootlin.com>,
	"Mattijs Korpershoek" <mkorpershoek@kernel.org>,
	"Daniel Golle" <daniel@makrotopia.org>,
	"Rasmus Villemoes" <rv@rasmusvillemoes.dk>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Manorit Chawdhry" <m-chawdhry@ti.com>,
	"Dhruva Gole" <d-gole@ti.com>,
	"João Paulo Gonçalves" <joao.goncalves@toradex.com>,
	"Paresh Bhagat" <p-bhagat@ti.com>,
	"Sam Protsenko" <semen.protsenko@linaro.org>,
	"George McCollister" <george.mccollister@konsulko.com>,
	"Siddharth Vadapalli" <s-vadapalli@ti.com>,
	"Frieder Schrempf" <frieder.schrempf@kontron.de>,
	"Swamil Jain" <s-jain1@ti.com>,
	"Neha Malcom Francis" <n-francis@ti.com>,
	"Shiva Tripathi" <s-tripathi1@ti.com>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Aristo Chen" <aristo.chen@canonical.com>,
	"Johan Jonker" <jbx6244@gmail.com>,
	"Apurva Nandan" <a-nandan@ti.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>,
	"Hrushikesh Salunke" <h-salunke@ti.com>
Subject: Re: [PATCH 05/11] arm: mach-k3: Add initial am62lx SoC support
Date: Mon, 20 Jul 2026 12:59:20 -0600	[thread overview]
Message-ID: <20260720185920.GD749385@bill-the-cat> (raw)
In-Reply-To: <20260717-am62lx-v1-5-b9830633afb8@ti.com>

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

On Fri, Jul 17, 2026 at 06:23:35PM -0500, Bryan Brattlof wrote:
> Add initial mach-k3 files needed to support boards based on the AM62L
> family of SoCs
> 
> Signed-off-by: Bryan Brattlof <bb@ti.com>
[snip]
> @@ -84,6 +93,7 @@ config SYS_K3_BOOT_PARAM_TABLE_INDEX
>  	default 0x43c3f290 if SOC_K3_AM625
>  	default 0x43c3f290 if SOC_K3_AM62A7 && CPU_V7R
>  	default 0x7000f290 if SOC_K3_AM62A7 && ARM64
> +	default 0x43c4f290 if SOC_K3_AM62L3
>  	default 0x43c4f290 if SOC_K3_AM62P5

These are the same values, are there other places where we should also
change SOC_K3_AM62P5 to SOC_K3_AM62P5 || SOC_K3_AM62L3 ? And now the
SOC_K3_AM625 / SOC_K3_AM62A7 example is also staring me in the face. Can
this, and some other entries here be consolidated? Or, would the
consolidation lead to harder to read entries?

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-07-20 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 23:23 [PATCH 00/11] arm: mach-k3: introduce basic support for the AM62L Bryan Brattlof
2026-07-17 23:23 ` [PATCH 01/11] firmware: scmi: switch to dev_ofnode during bind Bryan Brattlof
2026-07-17 23:23 ` [PATCH 02/11] tools: binman: extend ti_secure_rom to handle op-tee Bryan Brattlof
2026-07-22 13:20   ` Quentin Schulz
2026-07-17 23:23 ` [PATCH 03/11] soc: add data to identify the am62lx Bryan Brattlof
2026-07-17 23:23 ` [PATCH 04/11] boot/Kconfig: disable fit post processing for AM62L Bryan Brattlof
2026-07-17 23:23 ` [PATCH 05/11] arm: mach-k3: Add initial am62lx SoC support Bryan Brattlof
2026-07-20 18:59   ` Tom Rini via U-Boot [this message]
2026-07-17 23:23 ` [PATCH 06/11] board: ti: am62lx: add initial board files Bryan Brattlof
2026-07-17 23:23 ` [PATCH 07/11] arm: dts: k3-am62lx: Add binman support Bryan Brattlof
2026-07-17 23:23 ` [PATCH 08/11] configs: am62lx_evm: add initial defconfig Bryan Brattlof
2026-07-17 23:23 ` [PATCH 09/11] doc: ti: k3: fix pygments warning parsing device-tree Bryan Brattlof
2026-07-17 23:23 ` [PATCH 10/11] doc: board: ti: correct path to tcl scripts Bryan Brattlof
2026-07-17 23:23 ` [PATCH 11/11] doc: board: ti: am62lx_evm: add initial docs for the AM62L-EVM 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=20260720185920.GD749385@bill-the-cat \
    --to=u-boot@lists.u-boot-project.org \
    --cc=a-nandan@ti.com \
    --cc=afd@ti.com \
    --cc=alice.guo@nxp.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=anshuld@ti.com \
    --cc=aristo.chen@canonical.com \
    --cc=bb@ti.com \
    --cc=d-gole@ti.com \
    --cc=dan.carpenter@linaro.org \
    --cc=daniel@makrotopia.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=george.mccollister@konsulko.com \
    --cc=h-salunke@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jbx6244@gmail.com \
    --cc=joao.goncalves@toradex.com \
    --cc=kory.maincent@bootlin.com \
    --cc=m-chawdhry@ti.com \
    --cc=mkorpershoek@kernel.org \
    --cc=n-francis@ti.com \
    --cc=p-bhagat@ti.com \
    --cc=peng.fan@nxp.com \
    --cc=quentin.schulz@cherry.de \
    --cc=rv@rasmusvillemoes.dk \
    --cc=s-jain1@ti.com \
    --cc=s-tripathi1@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=semen.protsenko@linaro.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.