public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [Freedreno] [PATCH 2/2] arm64: dts: sdm845: Support GPU/GMU
Date: Wed, 7 Mar 2018 10:36:24 +0530	[thread overview]
Message-ID: <20180307050624.GR23018@vireshk-i7> (raw)
In-Reply-To: <20180306153757.GD15200@jcrouse-lnx.qualcomm.com>

On 06-03-18, 08:37, Jordan Crouse wrote:
> I'll try to explain but I might need Stephen or some of the other folks to jump
> in and save me.

Maybe you should start using his kernel.org address then ? :)

> On sdm845 there are shared power resources controlled by the RPMh which is
> programed by a series of commands from the regulator driver; but in the case
> of the GPU the votes are passed to the GMU (graphics management unit) which
> communicates with the RPMh on behalf of the GPU.
> 
> In order to construct the RPMh vote we need first need a voltage level that we
> can look up in a database. qcom,arc-level is the voltage level associated with
> a specific OPP.
> 
> I had previously been abusing this with opp-microvolt but that was wrong for
> obvious reasons and then Stephen pointed out that this would be a better way.

Glad that you shared that :)

A solution is already in progress for that and is partially merged as
well.

Look for "performance_state" in genpd and OPP cores (already merged),
followed by this series here:

https://lkml.kernel.org/r/cover.1513926033.git.viresh.kumar at linaro.org

-- 
viresh

  reply	other threads:[~2018-03-07  5:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 21:56 [PATCH 0/2] arm64: dts: Add sdm845 GPU/GMU and SMMU Jordan Crouse
2018-03-02 21:56 ` [PATCH 1/2] dt-bindings: Document qcom,adreno-gmu Jordan Crouse
2018-03-05 19:38   ` Rob Herring
2018-03-16 18:27     ` Jordan Crouse
2018-03-02 21:56 ` [PATCH 2/2] arm64: dts: sdm845: Support GPU/GMU Jordan Crouse
2018-03-05  4:42   ` Viresh Kumar
2018-03-05 15:28     ` Jordan Crouse
2018-03-06  4:26       ` Viresh Kumar
2018-03-06 15:37         ` [Freedreno] " Jordan Crouse
2018-03-07  5:06           ` Viresh Kumar [this message]
2018-03-08 20:14             ` Jordan Crouse
2018-03-09  3:43               ` Viresh Kumar
2018-03-09 10:19                 ` Rajendra Nayak
2018-03-09 15:47                   ` Jordan Crouse
2018-03-09 16:03                 ` Jordan Crouse
2018-03-09 17:18                   ` Stephen Boyd
2018-03-09 17:42                     ` Jordan Crouse
2018-03-12  5:54                       ` Viresh Kumar
2018-03-12  5:52                   ` Viresh Kumar
2018-03-13 18:23                     ` Stephen Boyd

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=20180307050624.GR23018@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --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