mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrei Lalaev <andrey.lalaev@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: iMX ddrphy_utils difference with U-boot
Date: Mon, 8 Jun 2026 20:15:41 +0200	[thread overview]
Message-ID: <82d65dc1-f88b-4527-b627-57378da46f95@gmail.com> (raw)
In-Reply-To: <7d47871b-989a-4ad0-bfb1-4d449fd13ceb@pengutronix.de>

Hi Ahmad,

Thank you for your quick reply.

On 08.06.26 19:26, Ahmad Fatoum wrote:
> Hello Andrei,
> 
> On 6/8/26 16:24, Andrei Lalaev wrote:
>> Hi,
>>
>> I am moving an iMX8MP module from vendor U-Boot 2024.04 to Barebox 2025.02
> 
> Sidenote: You'll probably want to use one of the still supported
> v2026.04 or v2026.06 releases.
> 

That's our plan for the near future :)


>> and found a strange difference in the DDR training code:
>>
>>   vim drivers/ddr/imx/ddrphy_utils.c +94
>>
>> And the corresponding line in U-Boot:
>>
>>   vim drivers/ddr/imx/phy/ddrphy_utils.c +101
>>
>> Is there any chance that somebody knows/remembers why "return -1" was replaced with "hang()"?
> 
> I can't speak for Sascha, but having looked at the code, I see no reason
> why not to propagate the error.
> 
>> I couldn't find any explanation in the commits/mailing lists.
> 
> My guess is that it wasn't anticipated that boards would handle
> the error gracefully to fall back to a different DDR init.
> 

In our case this is the only option, because we may have 2 and 4 GB modules.
So, if the 4 GB timings don't apply, we fall back to the 2 GB timings.


> Cheers,
> Ahmad


-- 
Best regards,
Andrei Lalaev



  reply	other threads:[~2026-06-08 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 14:24 Andrei Lalaev
2026-06-08 17:26 ` Ahmad Fatoum
2026-06-08 18:15   ` Andrei Lalaev [this message]
2026-06-08 19:12     ` Ahmad Fatoum
2026-06-15  8:49   ` Sascha Hauer
2026-06-11 20:35 ` Ahmad Fatoum
2026-06-11 20:36   ` Ahmad Fatoum

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=82d65dc1-f88b-4527-b627-57378da46f95@gmail.com \
    --to=andrey.lalaev@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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