mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	"barebox@lists.infradead.org" <barebox@lists.infradead.org>,
	uboot-imx@nxp.com, Steffen Trumtrar <str@pengutronix.de>
Subject: i.MX8/9: question about unused DDR PHY trained CSR board array
Date: Fri, 27 Sep 2024 16:08:00 +0200	[thread overview]
Message-ID: <8074530f-720b-4aea-934b-c0643c356617@pengutronix.de> (raw)

Hello Peng,

Looking at the DDR setup code for i.MX8M and i.MX9 that you had contributed,
I am wondering about struct dram_cfg_param::ddrphy_trained_csr and the global
ddrphy_trained_csr array.

struct dram_cfg_param::ddrphy_trained_csr is presumably generated by the
i.MX DDR tool and it seems populated by all the i.MX8M/9 boards in U-Boot.

This struct member is wholly unused though and instead a global
ddrphy_trained_csr is used.

What I wonder about is whether it's possible for the DDR tool to generate
a different ddrphy_trained_csr than the default:

  1) If yes, we should drop the global ddrphy_trained_csr and actually use
     the board-specific array

  2) If not, we should drop the board-specific array and perhaps ask for
    the DDR tool to be changed

I initially assumed 1) and because all boards supported by barebox had a
board-specific ddrphy_trained_csr that's identical to the global
ddrphy_trained_csr, I dropped the unused array[1][2].

I now have the DDR settings for an i.MX9 LPDDR4 board in front of me that
has different contents for struct dram_cfg_param::ddrphy_trained_csr than
the default.

I will inquire how that came about, but in parallel I wanted to ask you if
this is supposed to happen and to alert you to this issue.

The way things are, this is either a bug or a missed space saving opportunity
for U-Boot.

[1]: https://lore.barebox.org/barebox/20231205083604.1497018-1-a.fatoum@pengutronix.de/
[2]: https://lore.barebox.org/barebox/20240313154217.2747582-1-a.fatoum@pengutronix.de/

Thanks,
Ahmad


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




             reply	other threads:[~2024-09-27 14:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 14:08 Ahmad Fatoum [this message]
2024-09-30  6:38 ` Peng Fan

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=8074530f-720b-4aea-934b-c0643c356617@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=peng.fan@oss.nxp.com \
    --cc=str@pengutronix.de \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox