mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: beaglebone: add delay in lowlevel.c
Date: Wed, 8 Jan 2025 16:31:40 +0100	[thread overview]
Message-ID: <bc7ab523-2a65-42f9-bba1-ad7d17878cd3@pengutronix.de> (raw)
In-Reply-To: <Z36ZVQNtHi6krRl0@hephaistos>

On 08.01.25 16:27, Konstantin Kletschke wrote:
> More like this?
> 
> On Wed, Jan 08, 2025 at 04:19:49PM +0100, Ahmad Fatoum wrote:
>>
>> It would be nice to have the comment more verbose. e.g. that this issue
>> was observed on new Seeed-produced BBBs is an intersting info IMO.
> 
>  arch/arm/boards/beaglebone/lowlevel.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/arch/arm/boards/beaglebone/lowlevel.c b/arch/arm/boards/beaglebone/lowlevel.c
> index 5dc49dfaaf..7dc338d03a 100644
> --- a/arch/arm/boards/beaglebone/lowlevel.c
> +++ b/arch/arm/boards/beaglebone/lowlevel.c
> @@ -97,6 +97,12 @@ extern char __dtb_z_am335x_boneblack_start[];
>  extern char __dtb_z_am335x_bone_common_start[];
>  extern char __dtb_z_am335x_bone_start[];
> 
> +static void __udelay(int us)
> +{
> +        volatile int i;
> +       for (i = 0; i < us; i++);
> +}
> +
>  /**
>   * @brief The basic entry point for board initialization.
>   *
> @@ -135,6 +141,12 @@ static noinline int beaglebone_sram_init(void)
>         am33xx_enable_uart0_pin_mux();
>         omap_debug_ll_init();
>         putc_ll('>');
> +       /*
> +        * Some (~5%) Beaglebone Black received from SEEED in batches
> +        * after autumn 2024 require a delay to be able to warm start
> +        * after reset

Sounds good. Please add

Link: https://lore.barebox.org/barebox/Z0gywL2hLcIDoLQ8@hephaistos/

to your commit message before the S-o-b and then it's good to go, I think.

Thanks,
Ahmad

> +        */
> +       __udelay(3000);
> 
>         barebox_arm_entry(0x80000000, sdram_size, fdt);
>  }
> 
> 
> 
> 
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-01-08 15:32 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 [this message]
2025-01-08 15:38           ` Konstantin Kletschke
2025-01-08 15:46     ` Lucas Stach
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=bc7ab523-2a65-42f9-bba1-ad7d17878cd3@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=konstantin.kletschke@inside-m2m.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