From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>,
Tom Rini <trini@konsulko.com>
Cc: "Patrice CHOTARD" <patrice.chotard@foss.st.com>,
"U-Boot STM32" <uboot-stm32@st-md-mailman.stormreply.com>,
"Marek Vasut" <marex@denx.de>, "Pali Rohár" <pali@kernel.org>
Subject: [PULL] Pull request for u-boot master / v2023.01 = u-boot-stm32-20230106
Date: Fri, 6 Jan 2023 11:48:54 +0100 [thread overview]
Message-ID: <348bc74e-fb7c-3911-680a-b6dff96a70b4@foss.st.com> (raw)
Hi Tom,
Please pull the STM32 related fixes for u-boot/master, v2023.01:
u-boot-stm32-20230106
- stm32mp: Fix board_get_usable_ram_top(): workaround to avoid issue
after the
commit 777aaaa706b ("common/memsize.c: Fix get_effective_memsize() to
check
for overflow") because the effective DDR effective size is reduce by 4KiB
and sometime the board hang on boot
CI status:
https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/14623
This last patch for v2023.01 avoids a hang on 1GB DDR STM32MP15 board
detected
by Marek and caused by Pali patch.
For my point a view , this patch is an acceptable workaround for master
branch and v2023.01 delivery
but the initial patch should be revisited or reverted (in master or in
next ?).
For details see comments in patch
"arm: stm32mp: Fix board_get_usable_ram_top() again"
http://patchwork.ozlabs.org/project/uboot/patch/20230105012222.238075-1-marex@denx.de/
https://lore.kernel.org/u-boot/20230105012222.238075-1-marex@denx.de/
Thanks,
Patrick
=====
The following changes since commit 8d6cbf5e6bc4e10e38b954763fa025caed517cc2:
Merge tag 'efi-2023-01-rc5-3' of
https://source.denx.de/u-boot/custodians/u-boot-efi (2023-01-04 08:50:24
-0500)
are available in the Git repository at:
https://gitlab.denx.de/u-boot/custodians/u-boot-stm.git
tags/u-boot-stm32-20230106
for you to fetch changes up to a2e0b041d662e4c80502cd5c9a8326d026f9deb1:
arm: stm32mp: Fix board_get_usable_ram_top() again (2023-01-06
11:02:17 +0100)
----------------------------------------------------------------
- stm32mp: Fix board_get_usable_ram_top(): workaround to avoid issue
after the
commit 777aaaa706b ("common/memsize.c: Fix get_effective_memsize() to
check
for overflow") because the effective DDR effective size is reduce by 4KiB
and sometime the board hang on boot
----------------------------------------------------------------
Marek Vasut (1):
arm: stm32mp: Fix board_get_usable_ram_top() again
arch/arm/mach-stm32mp/dram_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2023-01-06 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 10:48 Patrick DELAUNAY [this message]
2023-01-06 16:52 ` [PULL] Pull request for u-boot master / v2023.01 = u-boot-stm32-20230106 Tom Rini
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=348bc74e-fb7c-3911-680a-b6dff96a70b4@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=marex@denx.de \
--cc=pali@kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.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.