From: Chris Morgan <macroalpha82@gmail.com>
To: u-boot@lists.denx.de
Cc: xypron.glpk@gmx.de, cym@rock-chips.com,
kever.yang@rock-chips.com, philipp.tomsich@vrull.eu,
sjg@chromium.org, trini@konsulko.com,
eugen.hristev@collabora.com, jonas@kwiboo.se,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/2] Use ATAGs for RK3588 For RAM Info
Date: Tue, 26 Mar 2024 15:49:42 -0500 [thread overview]
Message-ID: <20240326204944.1572667-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
Use the ATAG info provided by the Rockchip binary TPL to identify
RAM banks.
This is needed because there are specific addresses that should not
be written to for all RK3588 based devices with >=16GB of RAM, writing
to these addresses immediately results in a crash.
Chris Morgan (2):
rockchip: rk3588: Add support for ATAG parsing
rockchip: rk3588: Add Support for RAM Defines from ATAGs
arch/arm/include/asm/arch-rockchip/atags.h | 222 +++++++++++++++++++++
arch/arm/mach-rockchip/Makefile | 1 +
arch/arm/mach-rockchip/atags.c | 99 +++++++++
arch/arm/mach-rockchip/sdram.c | 58 ++++++
4 files changed, 380 insertions(+)
create mode 100644 arch/arm/include/asm/arch-rockchip/atags.h
create mode 100644 arch/arm/mach-rockchip/atags.c
--
2.34.1
next reply other threads:[~2024-03-26 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 20:49 Chris Morgan [this message]
2024-03-26 20:49 ` [PATCH 1/2] rockchip: rk3588: Add support for ATAG parsing Chris Morgan
2024-03-27 9:45 ` Quentin Schulz
2024-03-27 10:32 ` Kever Yang
2024-03-27 12:12 ` Tom Rini
2024-03-27 13:32 ` Chris Morgan
2024-03-27 14:21 ` Eugen Hristev
2024-03-27 15:03 ` Chris Morgan
2024-03-28 20:02 ` Tom Rini
2024-03-28 21:58 ` Chris Morgan
2024-03-28 22:13 ` Tom Rini
2024-03-26 20:49 ` [PATCH 2/2] rockchip: rk3588: Add Support for RAM Defines from ATAGs Chris Morgan
2024-03-27 10:51 ` Quentin Schulz
2024-03-27 13:10 ` Jonas Karlman
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=20240326204944.1572667-1-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=cym@rock-chips.com \
--cc=eugen.hristev@collabora.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=macromorgan@hotmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--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