From: Cody Eksal <masterr3c0rd@epochal.quest>
To: Andre Przywara <andre.przywara@arm.com>
Cc: u-boot@lists.denx.de, Jagan Teki <jagan@amarulasolutions.com>,
Philippe Simons <simons.philippe@gmail.com>,
Sumit Garg <sumit.garg@kernel.org>,
linux-sunxi@lists.linux.dev, Tom Rini <trini@konsulko.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>
Subject: Re: [PATCH v2 1/6] sunxi: A133: add DRAM init code
Date: Mon, 12 May 2025 12:12:36 -0300 [thread overview]
Message-ID: <20165cde26bb95b5f79d01d37f1f4af2@epochal.quest> (raw)
In-Reply-To: <20250511011003.15654-2-andre.przywara@arm.com>
On 2025/05/10 10:09 pm, Andre Przywara wrote:
> From: Cody Eksal <masterr3c0rd@epochal.quest>
>
> This adds preliminary support for the DRAM controller in the Allwinner
> A100/A133 SoCs.
> This is work in progress, and has rough edges, but works on at least
> three different boards. It contains support for DDR4 and LPDDR4.
>
> [Andre: formatting fixes, adapt to mainline, drop unused parameters,
> remove struct struct sunxi_mctl_com_reg, hardcode MR registers,
> switch to mctl_check_pattern(), remove simple DRAM check]
Thank you Andre for cleaning up my patches. Life has a nasty way of
getting in the way when it's least convenient.
Signed-off-by: Cody Eksal <masterr3c0rd@epochal.quest>
- Cody
> ---
> .../include/asm/arch-sunxi/cpu_sun50i_h6.h | 4 +
> arch/arm/include/asm/arch-sunxi/dram.h | 2 +
> .../include/asm/arch-sunxi/dram_sun50i_a133.h | 230 ++++
> arch/arm/mach-sunxi/Kconfig | 104 +-
> arch/arm/mach-sunxi/Makefile | 2 +
> arch/arm/mach-sunxi/dram_sun50i_a133.c | 1204 +++++++++++++++++
> arch/arm/mach-sunxi/dram_timings/Makefile | 2 +
> arch/arm/mach-sunxi/dram_timings/a133_ddr4.c | 80 ++
> .../arm/mach-sunxi/dram_timings/a133_lpddr4.c | 102 ++
> 9 files changed, 1722 insertions(+), 8 deletions(-)
> create mode 100644 arch/arm/include/asm/arch-sunxi/dram_sun50i_a133.h
> create mode 100644 arch/arm/mach-sunxi/dram_sun50i_a133.c
> create mode 100644 arch/arm/mach-sunxi/dram_timings/a133_ddr4.c
> create mode 100644 arch/arm/mach-sunxi/dram_timings/a133_lpddr4.c
>
next prev parent reply other threads:[~2025-05-12 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 1:09 [PATCH v2 0/6] sunxi: Allwinner A133 SoC support Andre Przywara
2025-05-11 1:09 ` [PATCH v2 1/6] sunxi: A133: add DRAM init code Andre Przywara
2025-05-11 9:23 ` Andre Przywara
2025-05-12 9:21 ` Quentin Schulz
2025-05-12 10:49 ` Andre Przywara
2025-05-12 15:12 ` Cody Eksal [this message]
2025-05-26 13:45 ` Parthiban
2025-05-11 1:09 ` [PATCH v2 2/6] sunxi: add support for the Allwinner A100/A133 SoC Andre Przywara
2025-05-11 1:10 ` [PATCH v2 3/6] arm64: dts: allwinner: a100: Add CPU Operating Performance Points table Andre Przywara
2025-05-12 9:24 ` Quentin Schulz
2025-05-12 10:46 ` Andre Przywara
2025-05-12 15:58 ` Quentin Schulz
2025-05-11 1:10 ` [PATCH v2 4/6] arm64: dts: allwinner: a100: set maximum MMC frequency Andre Przywara
2025-05-11 1:10 ` [PATCH v2 5/6] arm64: dts: allwinner: a100: add Liontron H-A133L board support Andre Przywara
2025-05-11 1:10 ` [PATCH v2 6/6] sunxi: add support for Liontron H-A133L board Andre Przywara
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=20165cde26bb95b5f79d01d37f1f4af2@epochal.quest \
--to=masterr3c0rd@epochal.quest \
--cc=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=simons.philippe@gmail.com \
--cc=sumit.garg@kernel.org \
--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