From: Andre Przywara <andre.przywara@arm.com>
To: Jesse Taube <mr.bossman075@gmail.com>
Cc: u-boot@lists.denx.de, jagan@amarulasolutions.com,
hdegoede@redhat.com, sjg@chromium.org, icenowy@aosc.io,
marek.behun@nic.cz, festevam@denx.de, narmstrong@baylibre.com,
tharvey@gateworks.com, christianshewitt@gmail.com,
pbrobinson@gmail.com, lokeshvutla@ti.com,
jernej.skrabec@gmail.com, hs@denx.de, samuel@sholland.org,
arnaud.ferraris@gmail.com, giulio.benetti@benettiengineering.com,
thirtythreeforty@gmail.com
Subject: Re: [PATCH 11/11] configs: sunxi: Add support for Lichee Pi Nano
Date: Wed, 26 Jan 2022 14:13:32 +0000 [thread overview]
Message-ID: <20220126141332.1c51f13e@donnerap.cambridge.arm.com> (raw)
In-Reply-To: <20220105003508.1143140-12-Mr.Bossman075@gmail.com>
On Tue, 4 Jan 2022 19:35:08 -0500
Jesse Taube <mr.bossman075@gmail.com> wrote:
Hi,
> From: Icenowy Zheng <icenowy@aosc.io>
>
> The Lichee Pi Nano is a board based on the F1C100s.
> Add defconfigs for it.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
> ---
> configs/licheepi_nano_defconfig | 13 ++++++++++++
> configs/licheepi_nano_spiflash_defconfig | 25 ++++++++++++++++++++++++
> 2 files changed, 38 insertions(+)
> create mode 100644 configs/licheepi_nano_defconfig
> create mode 100644 configs/licheepi_nano_spiflash_defconfig
>
> diff --git a/configs/licheepi_nano_defconfig b/configs/licheepi_nano_defconfig
> new file mode 100644
> index 0000000000..3a24870aaf
> --- /dev/null
> +++ b/configs/licheepi_nano_defconfig
> @@ -0,0 +1,13 @@
> +CONFIG_ARM=y
> +CONFIG_ARCH_SUNXI=y
> +CONFIG_MACH_SUNIV=y
> +CONFIG_SYS_TEXT_BASE=0x81700000
This belongs into boot/Kconfig, where we set the values for the other SoCs.
Please reorder them on the way, Kconfig goes with the first match, so we
should have a "default 0x4a000000 if ARCH_SUNXI" line at the end, and the
special snowflakes first. No need for && ARCH_SUNXI, MACH_SUNxxx is always
a subset of that.
> +CONFIG_SYS_LOAD_ADDR=0x81000000
This should be set in /Kconfig, as for the other SoCs.
> +CONFIG_SYS_MALLOC_LEN=0x120000
Same here, in /Kconfig, and reordering to simplify the expressions.
> +CONFIG_DRAM_CLK=156
> +CONFIG_SYS_DCACHE_OFF=y
Mmh, why is this?
> +CONFIG_DRAM_ZQ=0
> +# CONFIG_VIDEO_SUNXI is not set
> +CONFIG_DEFAULT_DEVICE_TREE="suniv-f1c100s-licheepi-nano"
> +CONFIG_SPL=y
> +# CONFIG_SPL_DM_SERIAL is not set
That should not be needed?
> diff --git a/configs/licheepi_nano_spiflash_defconfig b/configs/licheepi_nano_spiflash_defconfig
> new file mode 100644
> index 0000000000..07b6a27dbe
> --- /dev/null
> +++ b/configs/licheepi_nano_spiflash_defconfig
I dislike the idea of providing separate defconfigs for those board
variants. We have other examples where a SPI flash chip is not always
populated, but that should go well with one defconfig. If there is no SPI
flash, the code will see that and bail out gracefully, no problems with
that.
So there should be one defconfig, including SPI flash support. I'd suggest
to drop that for now, as the current series does not cover this, AFAICT.
We can add this later, which should be simpler with my SPI fix series.
Cheers,
Andre
> @@ -0,0 +1,25 @@
> +CONFIG_ARM=y
> +CONFIG_ARCH_SUNXI=y
> +CONFIG_ENV_SIZE=0x8000
> +CONFIG_ENV_OFFSET=0xf8000
> +CONFIG_MACH_SUNIV=y
> +CONFIG_DRAM_CLK=156
> +CONFIG_DRAM_ZQ=0
> +# CONFIG_VIDEO_SUNXI is not set
> +CONFIG_DEFAULT_DEVICE_TREE="suniv-f1c100s-licheepi-nano"
> +CONFIG_SPL=y
> +# CONFIG_CMD_FLASH is not set
> +# CONFIG_CMD_FPGA is not set
> +CONFIG_CMD_SF=y
> +CONFIG_CMD_SPI=y
> +CONFIG_ENV_IS_IN_SPI_FLASH=y
> +CONFIG_DM_SPI_FLASH=y
> +CONFIG_SPI_FLASH=y
> +CONFIG_SPI_FLASH_BAR=y
> +CONFIG_SPI_FLASH_GIGADEVICE=y
> +CONFIG_SPI_FLASH_MACRONIX=y
> +CONFIG_SPI_FLASH_WINBOND=y
> +CONFIG_SPL_SPI_SUNXI=y
> +# CONFIG_SPL_DM_SERIAL is not set
> +CONFIG_DM_SPI=y
> +CONFIG_SUN6I_SPI=y
next prev parent reply other threads:[~2022-01-26 14:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 0:34 [PATCH 00/11] Add support for SUNIV and F1C100s Jesse Taube
2022-01-05 0:34 ` [PATCH 01/11] arm: arm926ej-s: start.S: port save_boot_params support from armv7 code Jesse Taube
2022-01-21 1:57 ` Andre Przywara
2022-01-05 0:34 ` [PATCH 02/11] arm: arm926ej-s: add sunxi code Jesse Taube
2022-01-21 2:25 ` Andre Przywara
2022-01-21 3:16 ` Jesse Taube
2022-01-24 1:45 ` Andre Przywara
2022-01-05 0:35 ` [PATCH 03/11] dt-bindings: clock: Add initial suniv headers Jesse Taube
2022-01-21 1:57 ` Andre Przywara
2022-01-05 0:35 ` [PATCH 04/11] dt-bindings: reset: " Jesse Taube
2022-01-21 1:58 ` Andre Przywara
2022-01-05 0:35 ` [PATCH 05/11] ARM: sunxi: Add support for F1C100s Jesse Taube
2022-01-26 2:05 ` Andre Przywara
2022-01-26 4:53 ` Jesse Taube
2022-01-26 10:08 ` Andre Przywara
2022-01-05 0:35 ` [PATCH 06/11] sunxi: Add F1C100s DRAM initial support Jesse Taube
2022-01-05 0:35 ` [PATCH 07/11] sunxi: board: Add support for SUNIV Jesse Taube
2022-01-21 1:58 ` Andre Przywara
2022-01-05 0:35 ` [PATCH 08/11] configs: sunxi: Add common SUNIV header Jesse Taube
2022-01-26 2:07 ` Andre Przywara
2022-01-05 0:35 ` [PATCH 09/11] sunxi: Add support for SUNIV architecture Jesse Taube
2022-01-26 14:13 ` Andre Przywara
2022-01-26 14:38 ` Jesse Taube
2022-01-29 3:21 ` Jesse Taube
2022-01-29 11:51 ` Andre Przywara
2022-01-29 19:24 ` Jesse Taube
2022-01-29 20:44 ` Giulio Benetti
2022-01-29 20:59 ` Samuel Holland
2022-01-29 21:05 ` Jesse Taube
2022-01-29 21:18 ` Giulio Benetti
2022-01-29 21:19 ` Jesse Taube
2022-01-29 21:21 ` Giulio Benetti
2022-01-29 21:23 ` Jesse Taube
2022-01-05 0:35 ` [PATCH 10/11] ARM: dts: suniv: Add device tree files for F1C100s Jesse Taube
2022-01-21 1:59 ` Andre Przywara
2022-01-21 2:12 ` Jesse Taube
2022-01-05 0:35 ` [PATCH 11/11] configs: sunxi: Add support for Lichee Pi Nano Jesse Taube
2022-01-26 14:13 ` Andre Przywara [this message]
2022-01-26 14:48 ` Jesse Taube
2022-01-05 11:36 ` [PATCH 00/11] Add support for SUNIV and F1C100s Icenowy Zheng
2022-01-05 12:14 ` Andre Przywara
2022-01-05 12:54 ` Jesse Taube
2022-01-05 16:00 ` Giulio Benetti
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=20220126141332.1c51f13e@donnerap.cambridge.arm.com \
--to=andre.przywara@arm.com \
--cc=arnaud.ferraris@gmail.com \
--cc=christianshewitt@gmail.com \
--cc=festevam@denx.de \
--cc=giulio.benetti@benettiengineering.com \
--cc=hdegoede@redhat.com \
--cc=hs@denx.de \
--cc=icenowy@aosc.io \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=lokeshvutla@ti.com \
--cc=marek.behun@nic.cz \
--cc=mr.bossman075@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=pbrobinson@gmail.com \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.com \
--cc=thirtythreeforty@gmail.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