mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>
Cc: "open list:ARM/Amlogic Meson..."
	<linux-amlogic@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Christian Hewitt <christianshewitt@gmail.com>
Subject: Re: Missing mali regulator in Amlogic dts
Date: Tue, 8 Mar 2022 20:34:21 +0000	[thread overview]
Message-ID: <7eec71da-e4b4-eac3-a29c-4244c28f2875@arm.com> (raw)
In-Reply-To: <CAFBinCB700+g_fDmC5dXbNONLyESghp+RmZ+1myvhPbseXpY4A@mail.gmail.com>

On 2022-03-08 19:29, Martin Blumenstingl wrote:
> Hi Heiner,
> 
> On Tue, Mar 8, 2022 at 7:24 PM Heiner Kallweit <hkallweit1@gmail.com> wrote:
>>
>> I get following error on a  S905W-based system.
>> lima d00c0000.gpu: dev_pm_opp_set_regulators: no regulator (mali) found: -19
> This warning is harmless (see below)
> 
>> I see mali-supply in the DTS of few other vendors, but in no Amlogic DTS.
>> Is it missing, or are Amlogic SoCs different here?
> As far as I understand, on GXBB and GXL SoCs the VDDEE regulator is
> managed by the firmware (which is unfortunately closed-source).
> IIRC on the hardware side VDDEE is just another PWM regulator, just
> like with the 32-bit SoCs or with G12A (and later) SoCs.
> 
>> In the latter case supposedly drivers/gpu/drm/lima/lima_devfreq.c would
>> have to be changed to check for the optional regulator and not call
>> devm_pm_opp_set_regulators() if it's missing.
> I think I just copied the logic from panfrost
> (drivers/gpu/drm/panfrost/panfrost_devfreq.c) to lima.
> So GXM boards (using panfrost) will probably report a similar warning.
> That said, I don't know enough to judge whether your approach makes sense.

As a quality-of-life thing, it might make the most sense to refactor the 
API a bit so that it can offer a dedicated helper for setting optional 
regulators - possibly specifically a single optional regulator, since 
it's not necessarily clear how optionality should scale to a set of 
multiple items.

FWIW I do indeed see the same thing with panfrost, on an Arm Juno board 
where OPPs are completely abstracted behind the arm_scmi DVFS "clock".

Robin.

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2022-03-08 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 18:24 Heiner Kallweit
2022-03-08 19:29 ` Martin Blumenstingl
2022-03-08 20:34   ` Robin Murphy [this message]
2022-03-09  5:51     ` Christian Hewitt

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=7eec71da-e4b4-eac3-a29c-4244c28f2875@arm.com \
    --to=robin.murphy@arm.com \
    --cc=christianshewitt@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.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

all inboxes | Powered by JetHome®