U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Tom Rini <trini@konsulko.com>,
	Quentin Schulz <foss+uboot@0leil.net>,
	u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Kever Yang <kever.yang@rock-chips.com>,
	Heiko Stuebner <heiko.stuebner@cherry.de>,
	Jagan Teki <jagan@amarulasolutions.com>,
	Suniel Mahesh <sunil@amarulasolutions.com>,
	Klaus Goger <klaus.goger@theobroma-systems.com>,
	jonas@kwiboo.se, u-boot@lists.denx.de,
	Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH 00/10] rockchip: px30: migrate to common bss and stack addresses + UART fixes for evb-px30
Date: Wed, 22 May 2024 14:14:47 +0200	[thread overview]
Message-ID: <2148002.OBFZWjSADL@diego> (raw)
In-Reply-To: <c9a78f7a-5b63-4d37-93d4-2c6bd8db0076@cherry.de>

Am Mittwoch, 22. Mai 2024, 10:39:25 CEST schrieb Quentin Schulz:
> Hi Tom,
> 
> On 5/21/24 8:04 PM, Tom Rini wrote:
> > On Tue, May 21, 2024 at 07:39:53PM +0200, Quentin Schulz wrote:
> >> PX30 Ringneck ran out of memory in the allocation pool of U-Boot proper
> >> pre-reloc. Something needed to be done. Jonas did migrate a few SoCs
> >> already to this common bss+stack addresses so it made sense to follow
> >> the same route for one additional SoC: PX30.
> >>
> >> While at it, also fix a few issues related to UART on the PX30 Mini EVB
> >> I could test.
> >>
> >> Boot (to U-Boot CLI) tested on PX30 Ringneck and PX30 Mini-EVB.
> >>
> >> Thanks to Jonas for hinting where to look at.
> >>
> >> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> >> ---
> >> Quentin Schulz (10):
> >>        rockchip: px30: default TPL_SYS_MALLOC_F_LEN to 0x600 on PX30 Kconfig level
> >>        rockchip: Use common bss and stack addresses on PX30
> >>        rockchip: ringneck_px30: Use common bss and stack addresses
> >>        rockchip: evb-px30: Use common bss and stack addresses
> >>        rockchip: firefly-px30: Use common bss and stack addresses
> >>        rockchip: odroid-go2: Use common bss and stack addresses
> >>        rockchip: px30-core-*: Use common bss and stack addresses
> >>        rockchip: px30: make UART pinmux accessible to TPL/SPL DTB
> >>        rockchip: evb-px30: do not remove pinctrl nodes from SPL DTB
> >>        rockchip: evb-px30: make UART5 the debug UART
> >>
> >>   arch/arm/dts/px30-u-boot.dtsi                 | 16 ++++++++++++++++
> >>   arch/arm/mach-rockchip/px30/Kconfig           |  8 +++++++-
> >>   configs/evb-px30_defconfig                    | 23 +++++------------------
> >>   configs/firefly-px30_defconfig                | 19 +++----------------
> >>   configs/odroid-go2_defconfig                  | 19 +++----------------
> >>   configs/px30-core-ctouch2-of10-px30_defconfig | 19 +++----------------
> >>   configs/px30-core-ctouch2-px30_defconfig      | 19 +++----------------
> >>   configs/px30-core-edimm2.2-px30_defconfig     | 19 +++----------------
> >>   configs/ringneck-px30_defconfig               | 19 +++----------------
> >>   9 files changed, 46 insertions(+), 115 deletions(-)
> >> ---
> >> base-commit: a7f0154c412859323396111dd0c09dbafbc153cb
> >> change-id: 20240521-px30-2024-07-rc-7136f6241d29
> > 
> > As I assume we want to fix the platforms for v2024.07, is this the level
> > of config changes everyone is comfortable with on the platforms? Or
> > should we just go with the minimum for release and the rest to -next?
> > 
> 
> I can tell you that Ringneck doesn't work anymore on v2024.07-rc, but 
> the PX30 Mini EVB was still reaching U-Boot CLI without the changes. I 
> don't know about the other boards.
> 
> So I could split this into two series, one for master, one for next.
> 
> I could suggest: patch 1 to 3 in master, the rest in next. Patch 1 is 
> just moving things around. Patch 2 is doing nothing if nobody uses 
> ROCKCHIP_COMMON_STACK_ADDR and SPL_SHARES_INIT_SP_ADDR (which is the 
> case for px30 boards). Patch 3 is for fixing Ringneck, which I know is 
> broken.
> 
> Heiko having access to the Odroid Go2, maybe he could test without my 
> patches and see if it reaches the CLI to know if we should pull it in 
> for master as well.

I did that yesterday evening. The Odroid Go2 also reached u-boot CLI
and also booted without these changes. So I guess it's small enough
or whatever.

So at least the Go2 is fine on 2024.07-rc3 either way with or without
this series.

Heiko



  reply	other threads:[~2024-05-22 12:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 17:39 [PATCH 00/10] rockchip: px30: migrate to common bss and stack addresses + UART fixes for evb-px30 Quentin Schulz
2024-05-21 17:39 ` [PATCH 01/10] rockchip: px30: default TPL_SYS_MALLOC_F_LEN to 0x600 on PX30 Kconfig level Quentin Schulz
2024-05-21 20:22   ` Heiko Stübner
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:39 ` [PATCH 02/10] rockchip: Use common bss and stack addresses on PX30 Quentin Schulz
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:39 ` [PATCH 03/10] rockchip: ringneck_px30: Use common bss and stack addresses Quentin Schulz
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:39 ` [PATCH 04/10] rockchip: evb-px30: " Quentin Schulz
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:39 ` [PATCH 05/10] rockchip: firefly-px30: " Quentin Schulz
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:39 ` [PATCH 06/10] rockchip: odroid-go2: " Quentin Schulz
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:40 ` [PATCH 07/10] rockchip: px30-core-*: " Quentin Schulz
2024-05-23  3:48   ` Kever Yang
2024-05-21 17:40 ` [PATCH 08/10] rockchip: px30: make UART pinmux accessible to TPL/SPL DTB Quentin Schulz
2024-05-23  3:49   ` Kever Yang
2024-05-21 17:40 ` [PATCH 09/10] rockchip: evb-px30: do not remove pinctrl nodes from SPL DTB Quentin Schulz
2024-05-23  3:49   ` Kever Yang
2024-05-21 17:40 ` [PATCH 10/10] rockchip: evb-px30: make UART5 the debug UART Quentin Schulz
2024-05-23  3:49   ` Kever Yang
2024-05-21 18:04 ` [PATCH 00/10] rockchip: px30: migrate to common bss and stack addresses + UART fixes for evb-px30 Tom Rini
2024-05-22  8:39   ` Quentin Schulz
2024-05-22 12:14     ` Heiko Stübner [this message]
2024-05-22 14:15       ` Tom Rini
2024-05-21 19:16 ` Heiko Stübner

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=2148002.OBFZWjSADL@diego \
    --to=heiko@sntech.de \
    --cc=foss+uboot@0leil.net \
    --cc=heiko.stuebner@cherry.de \
    --cc=jagan@amarulasolutions.com \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=klaus.goger@theobroma-systems.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=quentin.schulz@cherry.de \
    --cc=sjg@chromium.org \
    --cc=sunil@amarulasolutions.com \
    --cc=trini@konsulko.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