All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 27 Aug 2026 19:06:06 +0200	[thread overview]
Message-ID: <36740ee5-9cac-4bd4-a67a-3ab5cffe9691@nabladev.com> (raw)
In-Reply-To: <5ef02e5a-c0ac-4afb-b90d-4d6d075b05e6@kontron.de>

On 8/27/26 3:35 PM, Frieder Schrempf wrote:
> On 26.08.26 14:24, Marek Vasut wrote:
>> On 8/26/26 10:12 AM, Frieder Schrempf wrote:
>>
>> [...]
>>
>>>>> I'm not sure, but even if it would work, it would require several
>>>>> separate init attempts only to read the IDs
>>>>
>>>> Why ? Init the bus in slowest mode with widest bus settings, then try
>>>> MRRD on all available DRAM chips, then figure out which ones report
>>>> valid IDs and which ones fail the MRd .
>>>
>>> As far as I can see this doesn't work. If we use the widest bus setting
>>> (CsPresent=0x3) on a single rank module, the training fails and the DDR
>>> remains in a state where the MR read doesn't work yet.
>>
>> Do you need training to read the IDs ? Simply force-use the slowest bus
>> mode (100 MTps iirc), the training is only relevant for the high-speed
>> modes.
> I don't see any existing code path for any i.MX with DDR4 that doesn't
> do the training before accessing MR registers. Do you have any
> references or examples? Do you have any sources for the claim that the
> training is only relevant for the high-speed modes? I couldn't find
> anything that supports this.

What happens if you simply skip the DDR training, return 0 from 
ddr_cfg_phy() ?

> Also I would assume that doing the MRRD on an unused CS would give me
> back some arbitrary random values. While I could interpret an unknown
> value as "rank/cs not present", I don't think its reliable enough. Or do
> you know of any error condition being reported for failed MRRD?

Try it and see what happens ?

  reply	other threads:[~2026-08-28  1:21 UTC|newest]

Thread overview: 17+ 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
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-24 23:28                 ` Fabio Estevam
2026-08-25  6:06                   ` Frieder Schrempf
2026-08-26  8:12                 ` Frieder Schrempf
2026-08-26 12:24                   ` Marek Vasut
2026-08-27 13:35                     ` Frieder Schrempf
2026-08-27 17:06                       ` Marek Vasut [this message]
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=36740ee5-9cac-4bd4-a67a-3ab5cffe9691@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.