From: sbabic@denx.de
To: Marcel Ziswiler <marcel@ziswiler.com>,u-boot@lists.denx.de
Subject: [PATCH v2 5/5] board: verdin-imx8mp: change prints in spl_dram_init function
Date: Tue, 4 Apr 2023 12:19:57 +0200 (CEST) [thread overview]
Message-ID: <20230404102020.BC46285E3B@phobos.denx.de> (raw)
In-Reply-To: <20230403120157.123621-6-marcel@ziswiler.com>
> From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
> change prints to show which DDR configuration (single/dual rank) is used
> Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Applied to u-boot-imx, next, thanks !
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, 82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2023-04-04 10:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 12:01 [PATCH v2 0/5] board: verdin-imx8mp: ddr updates Marcel Ziswiler
2023-04-03 12:01 ` [PATCH v2 1/5] board: verdin-imx8mp: update ddrc config for different lpddr4 memories Marcel Ziswiler
2023-04-04 10:19 ` sbabic
2023-04-03 12:01 ` [PATCH v2 2/5] board: verdin-imx8mp: fix lpddr4 refresh timing Marcel Ziswiler
2023-04-04 10:19 ` sbabic
2023-04-03 12:01 ` [PATCH v2 3/5] board: verdin-imx8mp: update lpddr4 configuration and training Marcel Ziswiler
2023-04-04 10:19 ` sbabic
2023-04-03 12:01 ` [PATCH v2 4/5] board: verdin-imx8mp: compact slight different lpddr4 configuration Marcel Ziswiler
2023-04-04 10:19 ` sbabic
2023-04-03 12:01 ` [PATCH v2 5/5] board: verdin-imx8mp: change prints in spl_dram_init function Marcel Ziswiler
2023-04-04 10:19 ` sbabic [this message]
2023-04-03 14:03 ` [PATCH v2 0/5] board: verdin-imx8mp: ddr updates Fabio Estevam
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=20230404102020.BC46285E3B@phobos.denx.de \
--to=sbabic@denx.de \
--cc=marcel@ziswiler.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