linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Dragan Simic <dsimic@manjaro.org>,
	linux-rockchip@lists.infradead.org,
	Quentin Schulz <quentin.schulz@cherry.de>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	alchark@gmail.com
Subject: Re: [PATCH v2] arm64: dts: rockchip: Add OPP voltage ranges to RK3399 OP1 SoC dtsi
Date: Wed, 06 Nov 2024 10:41:36 +0100	[thread overview]
Message-ID: <3252308.5fSG56mABF@diego> (raw)
In-Reply-To: <f6bb3387-4396-45d4-9cb4-594d58095510@cherry.de>

Am Mittwoch, 6. November 2024, 10:32:06 CET schrieb Quentin Schulz:
> Hi Dragan,
> 
> On 11/6/24 9:33 AM, Dragan Simic wrote:
> > Add support for voltage ranges to the CPU, GPU and DMC OPPs defined in the
> > SoC dtsi for Rockchip OP1, as a variant of the Rockchip RK3399.  This may be
> > useful if there are any OP1-based boards whose associated voltage regulators
> > are unable to deliver the exact voltages; otherwise, it causes no functional
> > changes to the resulting OPP voltages at runtime.
> > 
> > These changes cannot cause stability issues or any kind of damage, because
> > it's perfectly safe to use the highest voltage from an OPP group for each OPP
> > in the same group.  The only possible negative effect of using higher voltages
> > is wasted energy in form of some additionally generated heat.
> > 
> > Reported-by: Quentin Schulz <quentin.schulz@cherry.de>
> 
> Well, I merely highlighted that the voltage was different on OP1 
> compared to RK3399 for the 600MHz OPP :)
> 
> So... If there's ONE SoC I'm pretty sure is working as expected it's the 
> OP1 fitted on the Gru Chromebooks with the ChromiumOS kernel fork 
> (though yes, I believe all Gru CB are EoL since August 2023). In the 6.1 
> kernel fork, there's also no range: 
> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/chromeos-6.1/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi

yeah, this somehow goes quite a bit into the "stuff that doesn't need to
change" area. On the one hand it does make "some" sense to unify things
if we're using ranges everywhere else.

On the other hand, as Quentin noted below, all existing OP1 devices seem
to run just fine, and there won't be any more entering the kernel.

So what do we realisitically gain here, except hiding existing git-history
under another layer?

> So not sure we need to handle theoretical cases here. Will let 
> maintainers decide on that one. FWIW, there are two other OP1 devices, 
> the RockPi4A+ and RockPi4B+ which do not change the OPP either.


Heiko




  reply	other threads:[~2024-11-06 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  8:33 [PATCH v2] arm64: dts: rockchip: Add OPP voltage ranges to RK3399 OP1 SoC dtsi Dragan Simic
2024-11-06  9:32 ` Quentin Schulz
2024-11-06  9:41   ` Heiko Stübner [this message]
2024-11-06 10:45     ` Dragan Simic
2024-11-06 11:24       ` Heiko Stübner
2024-11-06 11:37         ` Dragan Simic
2024-11-06 10:38   ` Dragan Simic
2024-11-09 18:27 ` Heiko Stuebner

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=3252308.5fSG56mABF@diego \
    --to=heiko@sntech.de \
    --cc=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=quentin.schulz@cherry.de \
    --cc=robh@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).