From: Tom Rini <trini@konsulko.com>
To: Karthikeyan Mitran <kmitran@axiado.com>
Cc: u-boot@lists.denx.de, Siu Ming Tong <smtong@axiado.com>,
Prasad Bolisetty <pbolisetty@axiado.com>,
Andre Przywara <andre.przywara@arm.com>,
Tzu-Hao Wei <twei@axiado.com>, Simon Glass <sjg@chromium.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Sumit Garg <sumit.garg@kernel.org>
Subject: Re: [PATCH 2/2] arm: axiado: Add AX3005 based SCM3005 board support
Date: Wed, 29 Apr 2026 08:31:49 -0600 [thread overview]
Message-ID: <20260429143149.GV41863@bill-the-cat> (raw)
In-Reply-To: <20260428-ax3005_scm3005-v1-2-7fed19ee6fe0@axiado.com>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
On Tue, Apr 28, 2026 at 07:32:37PM -0700, Karthikeyan Mitran wrote:
> From: Siu Ming Tong <smtong@axiado.com>
>
> Add U-Boot board support for the Axiado AX3005 based targets, a quad-core
> ARM Cortex-A53 (ARMv8) platform.
>
> Board Kconfig introduces ARCH_AX3005, which selects ARM64, driver
> model, GIC-v3, and Zynq UART. TARGET_SCM3005 selects ARCH_AX3005,
> allowing future SoC variants to share the platform configuration.
>
> Secondary cores use spin-table boot. ft_board_setup() corrects
> the cpu-release-addr in the FDT, which arch_fixup_fdt() overwrites
> with the post-relocation address. The board linker script pins
> spin_table_v8.o at offset 0x2fa0 from text base to match the
> address declared in the device tree.
>
> Tested-by: Siu Ming Tong <smtong@axiado.com>
> Signed-off-by: Siu Ming Tong <smtong@axiado.com>
> Signed-off-by: Tzu-Hao Wei <twei@axiado.com>
> Signed-off-by: Karthikeyan Mitran <kmitran@axiado.com>
> ---
> MAINTAINERS | 10 +++
> arch/arm/Kconfig | 17 ++++
> board/axiado/scm3005/Kconfig | 15 ++++
> board/axiado/scm3005/Makefile | 5 ++
> board/axiado/scm3005/scm3005.c | 128 +++++++++++++++++++++++++++
> board/axiado/scm3005/u-boot.lds | 183 +++++++++++++++++++++++++++++++++++++++
> configs/ax3005_scm3005_defconfig | 73 ++++++++++++++++
> include/configs/ax3005-scm3005.h | 29 +++++++
> 8 files changed, 460 insertions(+)
We're adding a new ARCH symbol, but without a new mach- directory, which
I suspect some of the board code should be in, instead. Also:
> diff --git a/board/axiado/scm3005/u-boot.lds b/board/axiado/scm3005/u-boot.lds
> new file mode 100644
> index 00000000000..8e56535fdf9
> --- /dev/null
> +++ b/board/axiado/scm3005/u-boot.lds
> @@ -0,0 +1,183 @@
> +/* SPDX-License-Identifier: GPL-2.0+ */
> +/*
> + * Copyright (c) 2021-2026 Axiado Corporation (or its affiliates).
> + *
> + * Based on arch/arm/cpu/armv8/u-boot.lds
> + */
What differs here really? Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-04-29 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 2:32 [PATCH 0/2] Adding Axiado ax3005 based scm3005 board support Karthikeyan Mitran
2026-04-29 2:32 ` [PATCH 1/2] arm64: dts: axiado: Add AX3005 SCM3005 device tree Karthikeyan Mitran
2026-04-29 14:29 ` Tom Rini
2026-04-29 2:32 ` [PATCH 2/2] arm: axiado: Add AX3005 based SCM3005 board support Karthikeyan Mitran
2026-04-29 14:31 ` Tom Rini [this message]
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=20260429143149.GV41863@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=kmitran@axiado.com \
--cc=neil.armstrong@linaro.org \
--cc=pbolisetty@axiado.com \
--cc=sjg@chromium.org \
--cc=smtong@axiado.com \
--cc=sumit.garg@kernel.org \
--cc=twei@axiado.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