mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>,
	Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: beaglebone: add delay in lowlevel.c
Date: Wed, 08 Jan 2025 16:46:22 +0100	[thread overview]
Message-ID: <9c00ffd1332ba38dffc26b0b8967f8327d72e4a0.camel@lynxeye.de> (raw)
In-Reply-To: <Z36WZYxab1bAEzFG@hephaistos>

Hi Konstantin,

Am Mittwoch, dem 08.01.2025 um 16:14 +0100 schrieb Konstantin
Kletschke:
> Hello Sascha,
> 
> On Wed, Jan 08, 2025 at 03:32:04PM +0100, Sascha Hauer wrote:
> 
> > Calling udelay(1000) and adding a comment saying it delays 1.8ms looks
> > inconsistent. Maybe better count up to 2 in __udelay() above which makes
> 
> I completely agree somehow since the time is not even constant and depends on
> the PLL settings just done before.
> 
> I suggest the following:
> 
> Removing the "* 3" fancy thingy in the function's loop, calling the
> function with 3000 instead of 1000, changing comment to "needed on some
> Beaglebone Black for warm start after reset".
> 
> That would be as simple as possible.

It would be interesting to know if any of the configured PLLs go out of
lock again during the time your delay loop runs. I.e. check if any of
CM_IDLEST_DPLL_CORE, CM_IDLEST_DPLL_DDR, CM_IDLEST_DPLL_PER or
CM_IDLEST_DPLL_MPU contain a value other than 0x1.

Premature signaling of a PLL lock during warm reboot (where the PLL
isn't in bypass before the configuration) might well explain the issue.

Regards,
Lucas



  parent reply	other threads:[~2025-01-08 15:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 15:01 Konstantin Kletschke
2025-01-08 14:32 ` Sascha Hauer
2025-01-08 15:14   ` Konstantin Kletschke
2025-01-08 15:19     ` Ahmad Fatoum
2025-01-08 15:27       ` Konstantin Kletschke
2025-01-08 15:31         ` Ahmad Fatoum
2025-01-08 15:38           ` Konstantin Kletschke
2025-01-08 15:46     ` Lucas Stach [this message]
2025-01-08 15:18 Konstantin Kletschke
2025-01-08 15:36 Konstantin Kletschke

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=9c00ffd1332ba38dffc26b0b8967f8327d72e4a0.camel@lynxeye.de \
    --to=dev@lynxeye.de \
    --cc=barebox@lists.infradead.org \
    --cc=konstantin.kletschke@inside-m2m.de \
    --cc=s.hauer@pengutronix.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