public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
	linux-sunxi@lists.linux.dev, jernej.skrabec@gmail.com,
	samuel@sholland.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: allwinner: a64: Move CPU OPPs to the SoC dtsi file
Date: Thu, 05 Sep 2024 14:54:03 +0200	[thread overview]
Message-ID: <8a80465aaa4b7dc4c8c15d7a73944cfd@manjaro.org> (raw)
In-Reply-To: <20240905134254.6e15a1e5@donnerap.manchester.arm.com>

On 2024-09-05 14:42, Andre Przywara wrote:
> On Thu, 05 Sep 2024 14:38:53 +0200
> Dragan Simic <dsimic@manjaro.org> wrote:
> 
>> Hello Andre,
>> 
>> On 2024-09-05 14:34, Andre Przywara wrote:
>> > On Thu, 5 Sep 2024 20:26:15 +0800
>> > Chen-Yu Tsai <wens@csie.org> wrote:
>> >
>> >> Hi,
>> >>
>> >> On Thu, Sep 5, 2024 at 8:17 PM Dragan Simic <dsimic@manjaro.org>
>> >> wrote:
>> >> >
>> >> > Hello,
>> >> >
>> >> > Just checking, any further thoughts about this patch?
>> >>
>> >> Sorry, but I feel like it's not really worth the churn. There's not
>> >> really a problem to be solved here. What you are arguing for is more
>> >> about aesthetics, and we could argue that having them separate makes
>> >> it easier to read and turn on/off.
>> >
>> > Yeah, I agree. If a board wants to support OPPs, they just have to
>> > include
>> > a single file and define the CPU regulator, and that's a nice opt-in,
>> > IMHO.
>> > But having this patch would make it quite hard to opt out, I believe.
>> > For
>> > Linux there are probably ways to disable DVFS nevertheless, but I am
>> > not
>> > sure this is true in an OS agnostic pure-DT-only way.
>> 
>> Thanks for your response.  The only thing that still makes me wonder
>> is why would a board want to opt out of DVFS?  Frankly, I'd consider
>> the design of the boards that must keep DVFS disabled broken.
> 
> Yes! Among the boards using Allwinner SoCs there are some, say 
> less-optimal
> designs ;-)

I see, but such boards could simply disable the "cpu0_opp_table" node in
their dts(i) files, for the encapsulated CPU OPPs scenario, and 
everything
would still work and be defined in a clean(er) way.

I mean, if there are some suboptimal designs, perhaps the defaults 
should
be tailored towards the good designs, and the suboptimal designs should 
be
some kind of exceptions.

>> > This could probably be solved, but same as Chen-Yu I don't see any good
>> > enough reason for this patch in the first place.
>> >
>> >> And even though the GPU OPPs are in the dtsi, it's just one OPP acting
>> >> as a default clock rate.

  reply	other threads:[~2024-09-05 12:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14  5:51 [PATCH] arm64: dts: allwinner: a64: Move CPU OPPs to the SoC dtsi file Dragan Simic
2024-08-14 16:11 ` Chen-Yu Tsai
2024-08-15 16:34   ` Dragan Simic
2024-08-15 17:15     ` Andre Przywara
2024-08-17  4:25       ` Dragan Simic
2024-09-05 12:17         ` Dragan Simic
2024-09-05 12:26           ` Chen-Yu Tsai
2024-09-05 12:29             ` Dragan Simic
2024-09-05 12:34             ` Andre Przywara
2024-09-05 12:38               ` Dragan Simic
2024-09-05 12:42                 ` Andre Przywara
2024-09-05 12:54                   ` Dragan Simic [this message]
2024-09-05 13:20                     ` Andre Przywara
2024-09-10  5:17                       ` Dragan Simic

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=8a80465aaa4b7dc4c8c15d7a73944cfd@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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