public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: u-boot@lists.denx.de, "Marek Behún" <kabel@kernel.org>,
	"Peng Fan" <peng.fan@oss.nxp.com>,
	"Tom Rini" <trini@konsulko.com>
Subject: [PATCH 0/9] Support for 4 GB DDR modules for 32-bit U-Boot builds
Date: Fri,  9 Sep 2022 17:32:37 +0200	[thread overview]
Message-ID: <20220909153246.8455-1-pali@kernel.org> (raw)

This patch series fixes U-Boot code to correctly handle RAM size larger
than 2 GB and then fixes fsl ddr driver to do not crash U-Boot when 4 GB
DDR module is detected when U-Boot operates in 32-bit mode (as opposite
of the 36-bit mode).

With this patch series it is possible to boot 32-bit U-Boot with 4 GB
SODIMM DDR3 module without crashes. U-Boot will still use just
CONFIG_MAX_MEM_MAPPED amount of RAM, but it is better than crashing due
to the truncating of 4GB value to 32-bit number (which is zero).

I tested this patch series on powerpc P2020 based board but only with
U-Boot v2022.04 because U-Boot master branch is still broken on P2020.

Pali Rohár (9):
  common/memsize.c: Fix get_effective_memsize() to always check for
    CONFIG_MAX_MEM_MAPPED
  common/memsize.c: Fix get_effective_memsize() to check for overflow
  board_f: Fix types for board_get_usable_ram_top()
  board_f: Fix printing gd->ram_size and gd->ram_top
  ddr: fsl: Fix checking for maximal mappable memory
  ddr: fsl: Fix fsl_ddr_sdram_size() for 4GB modules with 32-bit
    phys_size_t
  ddr: fsl: Allow to detect 4 GB DDR modules in 32-bit mode
  ddr: fsl: Fix re-align of verbose DRAM information for non-SPL builds
  powerpc/mpc85xx: Explain TLB unmapped memory message

 arch/arm/mach-imx/imx8m/soc.c           |  2 +-
 arch/arm/mach-mvebu/arm64-common.c      |  2 +-
 arch/arm/mach-rockchip/sdram.c          |  2 +-
 arch/arm/mach-stm32mp/dram_init.c       |  2 +-
 arch/arm/mach-sunxi/board.c             |  2 +-
 arch/arm/mach-tegra/board2.c            |  2 +-
 arch/mips/mach-jz47xx/jz4780/jz4780.c   |  2 +-
 arch/mips/mach-octeon/dram.c            |  2 +-
 arch/powerpc/cpu/mpc85xx/tlb.c          |  2 +-
 arch/riscv/cpu/fu540/dram.c             |  2 +-
 arch/riscv/cpu/fu740/dram.c             |  2 +-
 arch/riscv/cpu/generic/dram.c           |  2 +-
 arch/x86/cpu/broadwell/sdram.c          |  2 +-
 arch/x86/cpu/coreboot/sdram.c           |  2 +-
 arch/x86/cpu/efi/payload.c              |  2 +-
 arch/x86/cpu/efi/sdram.c                |  2 +-
 arch/x86/cpu/intel_common/mrc.c         |  4 ++--
 arch/x86/cpu/ivybridge/sdram.c          |  2 +-
 arch/x86/cpu/qemu/dram.c                |  2 +-
 arch/x86/cpu/quark/dram.c               |  2 +-
 arch/x86/cpu/slimbootloader/sdram.c     |  2 +-
 arch/x86/cpu/tangier/sdram.c            |  2 +-
 arch/x86/include/asm/mrc_common.h       |  2 +-
 arch/x86/include/asm/u-boot-x86.h       |  2 +-
 arch/x86/lib/fsp1/fsp_dram.c            |  2 +-
 arch/x86/lib/fsp2/fsp_dram.c            |  2 +-
 board/broadcom/bcmns3/ns3.c             |  2 +-
 board/imgtec/boston/ddr.c               |  2 +-
 board/menlo/m53menlo/m53menlo.c         |  2 +-
 board/raspberrypi/rpi/rpi.c             |  2 +-
 board/ti/am65x/evm.c                    |  2 +-
 board/ti/j721e/evm.c                    |  2 +-
 board/ti/j721s2/evm.c                   |  2 +-
 board/xilinx/zynqmp/zynqmp.c            |  2 +-
 common/board_f.c                        |  6 ++---
 common/memsize.c                        | 20 ++++++++++++----
 drivers/ddr/fsl/lc_common_dimm_params.c |  3 +++
 drivers/ddr/fsl/main.c                  | 31 ++++++++++++++++++++-----
 drivers/video/fsl_dcu_fb.c              |  2 +-
 include/init.h                          |  2 +-
 40 files changed, 84 insertions(+), 50 deletions(-)

-- 
2.20.1


             reply	other threads:[~2022-09-09 15:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 15:32 Pali Rohár [this message]
2022-09-09 15:32 ` [PATCH 1/9] common/memsize.c: Fix get_effective_memsize() to always check for CONFIG_MAX_MEM_MAPPED Pali Rohár
2022-09-23 22:48   ` Tom Rini
2022-09-09 15:32 ` [PATCH 2/9] common/memsize.c: Fix get_effective_memsize() to check for overflow Pali Rohár
2022-09-09 15:32 ` [PATCH 3/9] board_f: Fix types for board_get_usable_ram_top() Pali Rohár
2022-09-09 18:21   ` Simon Glass
2022-09-09 15:32 ` [PATCH 4/9] board_f: Fix printing gd->ram_size and gd->ram_top Pali Rohár
2022-09-09 18:20   ` Simon Glass
2022-09-09 21:46     ` Pali Rohár
2022-09-12 13:33       ` Simon Glass
2022-09-09 15:32 ` [PATCH 5/9] ddr: fsl: Fix checking for maximal mappable memory Pali Rohár
2022-09-09 15:32 ` [PATCH 6/9] ddr: fsl: Fix fsl_ddr_sdram_size() for 4GB modules with 32-bit phys_size_t Pali Rohár
2022-09-09 15:32 ` [PATCH 7/9] ddr: fsl: Allow to detect 4 GB DDR modules in 32-bit mode Pali Rohár
2022-09-09 15:32 ` [PATCH 8/9] ddr: fsl: Fix re-align of verbose DRAM information for non-SPL builds Pali Rohár
2022-09-09 18:21   ` Simon Glass
2022-09-09 19:08     ` Tom Rini
2022-09-09 19:39       ` Simon Glass
2022-09-09 21:05         ` Tom Rini
2022-09-09 15:32 ` [PATCH 9/9] powerpc/mpc85xx: Explain TLB unmapped memory message Pali Rohár
2022-09-11  9:29 ` [PATCH 10/9] powerpc/mpc85xx: Fix re-align of unmapped DDR memory message for non-SPL builds Pali Rohár

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=20220909153246.8455-1-pali@kernel.org \
    --to=pali@kernel.org \
    --cc=kabel@kernel.org \
    --cc=peng.fan@oss.nxp.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