From: Emanuele Ghidoli <ghidoliemanuele@gmail.com>
To: Marek Vasut <marek.vasut@mailbox.org>,
Tom Rini <trini@konsulko.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Cc: Stefan Roese <stefan.roese@mailbox.org>,
Rasmus Villemoes <rv@rasmusvillemoes.dk>
Subject: Re: Regression on colibri-imx7 due to commit 9c1b13b3fd27 ("cyclic: reduce get_timer_us() calls inside hlist_for_each_entry_safe()")
Date: Thu, 23 Jul 2026 22:41:35 +0200 [thread overview]
Message-ID: <140e540b-08a7-4fca-a6fa-ee398d92dbea@gmail.com> (raw)
In-Reply-To: <23084e8e-ad4c-4f37-872a-9d2a8feb325f@mailbox.org>
On 7/23/26 20:35, Marek Vasut wrote:
> On 7/23/26 4:53 PM, Emanuele Ghidoli wrote:
>
> Hello everyone,
>
>> I found that Colibri iMX7 no longer boots when commit 9c1b13b3fd27
>> ("cyclic: reduce get_timer_us() calls inside hlist_for_each_entry_safe()")
>> is applied. Nothing is printed on the serial.
>>
>> I bisected the issue: booting the parent commit works fine, and
>> reverting this patch on top of current main also restores
>> boot. It's not yet obvious to me what in this change causes the
>> regression.
>>
>> Would it make sense to revert it until the root cause is found?
>
> Give Patrice a bit of time to analyze the problem.
>
Hello,
after the regression, get_timer_us() is called on every cyclic_run() call,
even when the cyclic list is empty. On imx7 this happens earlier than before,
when the timer has not yet been initialized: get_timer_us() calls get_tbclk(),
whose value is zero, and uses it as a divisor in tick_to_time_us(), leading to
a division by zero.
I would fix this by ensuring get_tbclk() returns at least 1 on imx7, but we
could hide bugs in this way. However, this bug could also be present on other
architectures, so I would just guard against entering the cyclic loop by
checking whether the list is empty before doing anything else, so
get_timer_us() is called "at the same point in time" as before.
Something like:
if (hlist_empty(cyclic_get_list())) {
gd->flags &= ~GD_FLG_CYCLIC_RUNNING;
return;
}
Kind regards,
Emanuele
next prev parent reply other threads:[~2026-07-23 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 14:53 Regression on colibri-imx7 due to commit 9c1b13b3fd27 ("cyclic: reduce get_timer_us() calls inside hlist_for_each_entry_safe()") Emanuele Ghidoli
2026-07-23 18:35 ` Marek Vasut via U-Boot
2026-07-23 20:41 ` Emanuele Ghidoli [this message]
2026-07-24 0:00 ` Marek Vasut via U-Boot
2026-07-24 7:05 ` Rasmus Villemoes
2026-07-24 7:36 ` Emanuele Ghidoli
2026-07-26 6:41 ` Marek Vasut via U-Boot
2026-07-28 9:46 ` Emanuele Ghidoli
2026-07-28 11:53 ` Marek Vasut via U-Boot
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=140e540b-08a7-4fca-a6fa-ee398d92dbea@gmail.com \
--to=ghidoliemanuele@gmail.com \
--cc=marek.vasut@mailbox.org \
--cc=patrice.chotard@foss.st.com \
--cc=rv@rasmusvillemoes.dk \
--cc=stefan.roese@mailbox.org \
--cc=trini@konsulko.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