From: Conor Dooley <conor@kernel.org>
To: Xingyu Wu <xingyu.wu@starfivetech.com>
Cc: Hal Feng <hal.feng@starfivetech.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v6] clk: starfive: jh7110-sys: Fix lower rate of CPUfreq by setting PLL0 rate to 1.5GHz
Date: Fri, 23 Aug 2024 16:34:32 +0100 [thread overview]
Message-ID: <20240823-able-subtype-4e9a2049c114@spud> (raw)
In-Reply-To: <NTZPR01MB0956ABB5D9B0D087E085EF8B9F882@NTZPR01MB0956.CHNPR01.prod.partner.outlook.cn>
[-- Attachment #1: Type: text/plain, Size: 2017 bytes --]
On Fri, Aug 23, 2024 at 08:34:55AM +0000, Xingyu Wu wrote:
> On 23.08.24 11:42, Hal Feng wrote:
> > > > >
> > > > > I'm still not a fan of hardcoding cpu frequencies in the driver.
> > > > > You've added the notifiers exactly so that we can use the standard
> > > > > device
> > > tree settings for this.
> > > > >
> > > > > In other words I much prefer v5 of this patchset.
> > > > >
> > > > > /Emil
> > > > >
> > > >
> > > > Thanks, Emil.
> > > >
> > > > Hi Conor, what do you think about this issue?
> > >
> > > Apologies for the delay replying, I didn't realise there was a
> > > question here directed at me. My only real thought on the patchset is
> > > that what is done should not cause problems when the same devicetree
> > > is used for both U-Boot and for the kernel. As long as that's
> > > satisfied, I don't mind how you choose to implement it.
> >
> > Actually VF2 U-Boot can run at 1.5GHz. It will work if the PMIC sets the CPU
> > power supply voltage to 1.04V. The reason why we run VF2 U-Boot at 1.0GHz is
> > that the default voltage supplied by the PMIC is 0.9V which only supports JH7110
> > cores running at 1.0GHz.
> >
> > So v5 of this patchset won't cause problems if the VF2 U-Boot makes some
> > changes to support running at 1.5GHz. And I will make these changes when I
> > implement OF_UPSTREAM for VF2 U-Boot.
> >
> > BTW, if v5 is applied, the patch 2 of v5 should be rebased on the new mainline
> > since jh7110-common.dtsi has been created.
> >
>
> Good news. Thanks Hal.
>
> Hi Conor,
>
> According to Hal, U-Boot can also run 1.5G so that the dts from kernel
> can be used on the U-Boot and could not cause any problems. So the way of
> Patch v5[1] works which Emil agreed.
> [1]: https://lore.kernel.org/all/20240507065319.274976-1-xingyu.wu@starfivetech.com/
>
> If you agree, I will submit a new patchset soon and modify it for the new jh7110-common.dtsi.
That's great, thanks for working on it guys.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-08-23 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 2:06 [PATCH v6] clk: starfive: jh7110-sys: Fix lower rate of CPUfreq by setting PLL0 rate to 1.5GHz Xingyu Wu
2024-07-02 6:28 ` Xingyu Wu
2024-08-06 9:58 ` Emil Renner Berthing
2024-08-08 3:44 ` Xingyu Wu
2024-08-18 13:44 ` Conor Dooley
2024-08-23 3:41 ` Hal Feng
2024-08-23 8:34 ` Xingyu Wu
2024-08-23 15:34 ` Conor Dooley [this message]
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=20240823-able-subtype-4e9a2049c114@spud \
--to=conor@kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=hal.feng@starfivetech.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=xingyu.wu@starfivetech.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