linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] dt-bindings: gpu: mali-utgard: add optional supply regulator
Date: Fri, 15 Sep 2017 11:01:45 +0200	[thread overview]
Message-ID: <11237143.FSQKKME6IQ@phil> (raw)
In-Reply-To: <20170913143415.fcds556hdqwnhsvm@rob-hp-laptop>

Am Mittwoch, 13. September 2017, 09:34:15 CEST schrieb Rob Herring:
> On Wed, Sep 13, 2017 at 12:12:24AM +0200, Heiko St?bner wrote:
> > Hi Rob,
> > 
> > Am Dienstag, 12. September 2017, 17:09:20 CEST schrieb Rob Herring:
> > > On Tue, Sep 05, 2017 at 12:57:34PM +0200, Heiko Stuebner wrote:
> > > > Mali GPUs have a separate supplying regulator in a lot of socs,
> > > > so describe a mali-supply property. The already described
> > > > operating points will likely also need access to this regulator.
> > > > 
> > > > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > > > ---
> > > > 
> > > >  Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt | 3 +++
> > > >  1 file changed, 3 insertions(+)
> > > > 
> > > > diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt
> > > > b/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt index
> > > > 3b7f6f72f032..bcaa640c883f 100644
> > > > --- a/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt
> > > > +++ b/Documentation/devicetree/bindings/gpu/arm,mali-utgard.txt
> > > > 
> > > > @@ -39,6 +39,9 @@ Optional properties:
> > > >      Memory region to allocate from, as defined in
> > > >      Documentation/devicetree/bindi/reserved-memory/reserved-memory.txt
> > > > 
> > > > +  - mali-supply : Phandle to regulator for the Mali device. Refer to
> > > > +    Documentation/devicetree/bindings/regulator/regulator.txt for
> > > > details.
> > > 
> > > Wouldn't a power domain be more appropriate?
> > 
> > At least on Rockchip socs there is a power-domain, but also the separate 
> > additional regulator. See the similar mali-midgard binding.
> 
> And that regulator's state is independent of the power domain's state? 
>
> But I guess OPPs need a regulator. Really we should allow OPPs to be 
> tied to the power domain. Maybe we do, I can't keep up with the ever 
> evolving PM stuff.

Yep, the external gpu regulator state is completely independent of the
power-domain inside the soc and is most of the time one of the regulators
coming from the external pmic or sometimes even a completely separate
i2c-connected ic.

It's the same for the cpu cores on Rockchip socs, they have power-domains
for controlling the actual on/off state and need separate supplying
i2c-connected regulators that still have to be enabled on their own.


> So, given we already have it for midgard,
> 
> Acked-by: Rob Herring <robh@kernel.org>

Thanks, added for v2.

  reply	other threads:[~2017-09-15  9:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 10:57 [PATCH 0/7] ARM: dts: rockchip: add Utgard Mali nodes for some socs Heiko Stuebner
2017-09-05 10:57 ` [PATCH 1/7] dt-bindings: gpu: mali-utgard: Add Rockchip Utgard Malis Heiko Stuebner
2017-09-12 22:02   ` Rob Herring
2017-09-05 10:57 ` [PATCH 2/7] dt-bindings: gpu: mali-utgard: add optional supply regulator Heiko Stuebner
2017-09-12 22:09   ` Rob Herring
2017-09-12 22:12     ` Heiko Stübner
2017-09-13 14:34       ` Rob Herring
2017-09-15  9:01         ` Heiko Stuebner [this message]
2017-09-05 10:57 ` [PATCH 3/7] ARM: dts: rockchip: add rk3036 gpu node Heiko Stuebner
2017-09-05 10:57 ` [PATCH 4/7] ARM: dts: rockchip: enable the gpu on rk3036-kylin boards Heiko Stuebner
2017-09-05 10:57 ` [PATCH 5/7] ARM: dts: rockchip: add rk322x gpu node Heiko Stuebner
2017-09-05 10:57 ` [PATCH 6/7] ARM: dts: rockchip: add gpu nodes on rk3066/rk3188 Heiko Stuebner
2017-09-05 10:57 ` [PATCH 7/7] ARM: dts: rockchip: enable gpu on rk3188-radxarock 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=11237143.FSQKKME6IQ@phil \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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).