From: Francesco Dolcini <francesco@dolcini.it>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Vitor Soares <ivitro@gmail.com>,
marcel.ziswiler@toradex.com, trini@konsulko.com,
u-boot@lists.denx.de, Vitor Soares <vitor.soares@toradex.com>
Subject: Re: [PATCH] arm: dts: k3-am625-verdin-r5: Change CPU frequency to 1000MHz
Date: Tue, 20 Feb 2024 09:28:23 +0100 [thread overview]
Message-ID: <20240220082823.GA4685@francesco-nb> (raw)
In-Reply-To: <00d656a1-52f2-4f69-a2dc-6e98347780b2@ti.com>
On Tue, Feb 20, 2024 at 10:47:03AM +0530, Vignesh Raghavendra wrote:
>
>
> On 19/02/24 18:04, Vitor Soares wrote:
> > From: Vitor Soares <vitor.soares@toradex.com>
> >
> > The same U-Boot binary is compatible with multiple Verdin AM62 board
> > variants. However, some of the SoC models can only operate at a maximum
> > speed of 1 GHz.
> >
> > Previously, the boards with lower-speed grades were running at
> > overclocked speeds, leading to kernel complaints about unsupported
> > configurations.
> >
> > To resolve this issue, the operating speed has been decreased to the
> > maximum allowable value across all Verdin AM62 board variants. As a
> > result, there is a regression in overall boot time, increasing by around
> > 200 milliseconds for the faster SoC variant.
> >
>
> Patch as such is fine. But one way to avoid boot regression is to fixup
> the clock freq using based on speed grade identified by
> k3_get_speed_grade() and freq mapping table for each letter as show in
> datasheet [0]
Ack. I would still merge this as it is, I think that is conceptually
better to have a safe and valid value in the DT source file.
We can still do the optimization you suggested afterward, we just wanted
to get rid of any potential malfunction because of this overclocking as
soon as possible.
Francesco
next prev parent reply other threads:[~2024-02-20 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 12:34 [PATCH] arm: dts: k3-am625-verdin-r5: Change CPU frequency to 1000MHz Vitor Soares
2024-02-19 17:26 ` Francesco Dolcini
2024-02-20 5:17 ` Vignesh Raghavendra
2024-02-20 8:28 ` Francesco Dolcini [this message]
2024-03-01 18:54 ` Tom Rini
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=20240220082823.GA4685@francesco-nb \
--to=francesco@dolcini.it \
--cc=ivitro@gmail.com \
--cc=marcel.ziswiler@toradex.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=vitor.soares@toradex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox