From: Leo Liang <ycliang@andestech.com>
To: Kongyang Liu <seashell11234455@gmail.com>
Cc: <u-boot@lists.denx.de>, Ben Dooks <ben.dooks@codethink.co.uk>,
Bin Meng <bmeng@tinylab.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
Michal Simek <michal.simek@amd.com>,
Padmarao Begari <padmarao.begari@microchip.com>,
Randolph <randolph@andestech.com>, Rick Chen <rick@andestech.com>,
Samuel Holland <samuel@sholland.org>,
Tom Rini <trini@konsulko.com>,
Yu Chien Peter Lin <peterlin@andestech.com>
Subject: Re: [PATCH v2 1/2] riscv: spacemit: bananapi_f3: initial support added
Date: Tue, 10 Sep 2024 10:57:02 +0800 [thread overview]
Message-ID: <Zt-1forn-r6YzKSb@swlinux02> (raw)
In-Reply-To: <20240718043329.1500-2-seashell11234455@gmail.com>
On Thu, Jul 18, 2024 at 12:33:22PM +0800, Kongyang Liu wrote:
> Add basic support for SpacemiT's Banana Pi F3 board
>
> Signed-off-by: Kongyang Liu <seashell11234455@gmail.com>
> Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
> ---
>
> Changes in v2:
> - Change license to GPL-2.0-or-later
> - Add memory node for dts
> - Add ft_board_setup function for kernel memory init
> - Use default prompt
>
> arch/riscv/Kconfig | 5 +
> arch/riscv/cpu/k1/Kconfig | 18 ++
> arch/riscv/cpu/k1/Makefile | 6 +
> arch/riscv/cpu/k1/cpu.c | 9 +
> arch/riscv/cpu/k1/dram.c | 54 ++++
> arch/riscv/dts/Makefile | 1 +
> arch/riscv/dts/k1-bananapi-f3.dts | 25 ++
> arch/riscv/dts/k1.dtsi | 375 +++++++++++++++++++++++++
> board/spacemit/bananapi_f3/Kconfig | 25 ++
> board/spacemit/bananapi_f3/MAINTAINERS | 6 +
> board/spacemit/bananapi_f3/Makefile | 5 +
> board/spacemit/bananapi_f3/board.c | 9 +
> configs/bananapi_f3_defconfig | 20 ++
> include/configs/bananapi_f3.h | 15 +
> 14 files changed, 573 insertions(+)
> create mode 100644 arch/riscv/cpu/k1/Kconfig
> create mode 100644 arch/riscv/cpu/k1/Makefile
> create mode 100644 arch/riscv/cpu/k1/cpu.c
> create mode 100644 arch/riscv/cpu/k1/dram.c
> create mode 100644 arch/riscv/dts/k1-bananapi-f3.dts
> create mode 100644 arch/riscv/dts/k1.dtsi
> create mode 100644 board/spacemit/bananapi_f3/Kconfig
> create mode 100644 board/spacemit/bananapi_f3/MAINTAINERS
> create mode 100644 board/spacemit/bananapi_f3/Makefile
> create mode 100644 board/spacemit/bananapi_f3/board.c
> create mode 100644 configs/bananapi_f3_defconfig
> create mode 100644 include/configs/bananapi_f3.h
Hi Kongyang,
`$ make bananapi_f3_defconfig && make` produces the following warning.
In file included from drivers/serial/ns16550.c:13:
include/ns16550.h:205:9: warning: "UART_IIR_ID" redefined
205 | #define UART_IIR_ID 0x06 /* Mask for the interrupt ID */
| ^~~~~~~~~~~
In file included from include/configs/bananapi_f3.h:10,
from include/config.h:3,
from drivers/serial/ns16550.c:8:
include/linux/serial_reg.h:33:9: note: this is the location of the previous definition
33 | #define UART_IIR_ID 0x0e /* Mask for the interrupt ID */
| ^~~~~~~~~~~
There seems to be Macro redefinition.
Could you please take a look?
Best regards,
Leo
> diff --git a/configs/bananapi_f3_defconfig b/configs/bananapi_f3_defconfig
> new file mode 100644
> index 0000000000..6363620208
> --- /dev/null
> +++ b/configs/bananapi_f3_defconfig
> @@ -0,0 +1,20 @@
> +CONFIG_RISCV=y
> +CONFIG_SYS_MALLOC_LEN=0x1000000
> +CONFIG_NR_DRAM_BANKS=2
> +CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
> +CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x1000000
> +CONFIG_DEFAULT_DEVICE_TREE="k1-bananapi-f3"
> +CONFIG_SYS_LOAD_ADDR=0x200000
> +CONFIG_TARGET_BANANAPI_F3=y
> +CONFIG_ARCH_RV64I=y
> +CONFIG_RISCV_SMODE=y
> +CONFIG_FIT=y
> +CONFIG_SYS_BOOTM_LEN=0xa000000
> +CONFIG_SUPPORT_RAW_INITRD=y
> +CONFIG_OF_BOARD_SETUP=y
> +CONFIG_SYS_CBSIZE=256
> +CONFIG_SYS_PBSIZE=276
> +CONFIG_HUSH_PARSER=y
> +CONFIG_ENV_OVERWRITE=y
> +CONFIG_SYS_NS16550=y
> +CONFIG_SYS_NS16550_MEM32=y
> diff --git a/include/configs/bananapi_f3.h b/include/configs/bananapi_f3.h
> new file mode 100644
> index 0000000000..723bbaab69
> --- /dev/null
> +++ b/include/configs/bananapi_f3.h
> @@ -0,0 +1,15 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */
> +/*
> + * Copyright (c) 2024, Kongyang Liu <seashell11234455@gmail.com>
> + *
> + */
> +
> +#ifndef __CONFIG_H
> +#define __CONFIG_H
> +
> +#include <linux/serial_reg.h>
> +
> +#define CFG_SYS_SDRAM_BASE 0x0
> +#define CFG_SYS_NS16550_IER UART_IER_UUE
> +
> +#endif /* __CONFIG_H */
next prev parent reply other threads:[~2024-09-10 2:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 4:33 [PATCH v2 0/2] riscv: spacemit: bananapi_f3: add support for Banana Pi F3 board Kongyang Liu
2024-07-18 4:33 ` [PATCH v2 1/2] riscv: spacemit: bananapi_f3: initial support added Kongyang Liu
2024-09-09 6:40 ` Leo Liang
2024-09-10 2:57 ` Leo Liang [this message]
2024-09-12 21:10 ` Marcel Ziswiler
2024-07-18 4:33 ` [PATCH v2 2/2] doc: spacemit: bananapi_f3: document Banana Pi F3 board Kongyang Liu
2024-09-09 6:41 ` Leo Liang
2024-09-12 21:10 ` Marcel Ziswiler
2024-09-12 21:09 ` [PATCH v2 0/2] riscv: spacemit: bananapi_f3: add support for " Marcel Ziswiler
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=Zt-1forn-r6YzKSb@swlinux02 \
--to=ycliang@andestech.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bmeng@tinylab.org \
--cc=dan.carpenter@linaro.org \
--cc=michal.simek@amd.com \
--cc=padmarao.begari@microchip.com \
--cc=peterlin@andestech.com \
--cc=randolph@andestech.com \
--cc=rick@andestech.com \
--cc=samuel@sholland.org \
--cc=seashell11234455@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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