From: Marek Vasut <marex@nabladev.com>
To: Frieder Schrempf <frieder.schrempf@kontron.de>,
Frieder Schrempf <frieder@fris.de>,
Stefano Babic <sbabic@nabladev.com>,
Fabio Estevam <festevam@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Tom Rini <trini@konsulko.com>,
u-boot@lists.u-boot-project.org
Cc: uboot-imx@nxp.com, Simona Toaca <simona.toaca@nxp.com>,
Viorel Suman <viorel.suman@nxp.com>
Subject: Re: [PATCH v2 3/4] ddr: imx: Allow to call ddr init without logging failure
Date: Wed, 19 Aug 2026 14:47:31 +0200 [thread overview]
Message-ID: <cfe8d0e1-c652-408c-bc47-0ae96dd0a65d@nabladev.com> (raw)
In-Reply-To: <a8be2bf7-aafa-4e8e-9685-5fa100941805@kontron.de>
On 8/19/26 12:10 PM, Frieder Schrempf wrote:
> On 19.08.26 12:04, Marek Vasut wrote:
>> On 8/19/26 9:07 AM, Frieder Schrempf wrote:
>>> From: Frieder Schrempf <frieder.schrempf@kontron.de>
>>>
>>> In some cases we need to call ddr_init() multiple times to try
>>> different configurations.
>>
>> What different configurations ? Details please ?
>
> The detection of different DDR types/sizes on our SoMs has always been
> based on trying the init and seeing if it succeeds, falling back to the
> smaller sizes on failure. See here [1].
Could you maybe bring the interface up in some minimal 400 MTps or 100
MTps configuration and then read out the MR ID registers from the DRAM
to discern which DRAM configuration is present on your SoM? This would
be the ideal generic way of doing this, and it would be reliable since
the IDs are stable and surely indicate which DRAM chip and how big it is.
next prev parent reply other threads:[~2026-08-20 3:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 7:07 [PATCH v2 1/4] ddr: imx: Reload the training firmware for every PHY configuration Frieder Schrempf
2026-08-19 7:07 ` [PATCH v2 2/4] ddr: imx: Move error message for failed training to calling side Frieder Schrempf
2026-08-19 7:07 ` [PATCH v2 3/4] ddr: imx: Allow to call ddr init without logging failure Frieder Schrempf
2026-08-19 10:04 ` Marek Vasut
2026-08-19 10:10 ` Frieder Schrempf
2026-08-19 12:47 ` Marek Vasut [this message]
2026-08-20 6:34 ` Frieder Schrempf
2026-08-20 8:05 ` Marek Vasut
2026-08-20 14:25 ` Frieder Schrempf
2026-08-20 15:25 ` Marek Vasut
2026-08-19 7:07 ` [PATCH v2 4/4] imx: kontron-sl-mx8mm: Stop printing error message on first DDR init Frieder Schrempf
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=cfe8d0e1-c652-408c-bc47-0ae96dd0a65d@nabladev.com \
--to=marex@nabladev.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=frieder@fris.de \
--cc=ilias.apalodimas@linaro.org \
--cc=sbabic@nabladev.com \
--cc=simona.toaca@nxp.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=uboot-imx@nxp.com \
--cc=viorel.suman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.