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: Fri, 9 Mar 2018 09:13:32 +0530	[thread overview]
Message-ID: <20180309034332.GO6842@vireshk-i7> (raw)
In-Reply-To: <20180308201438.GA10589@jcrouse-lnx.qualcomm.com>

On 08-03-18, 13:14, Jordan Crouse wrote:
> It seems to me that performance_state has a direct relationship with genpd
> which is good for CPU votes but in this case, we're just passing along raw data
> to an independent microcontroller. The 'qcom,arc-level' is used to construct
> the actual values that the GMU will program into the RPMh. Since these are

The "genpd" here is created specially for this RPM. The performance-state thing
is designed to solve this very specific problem of qualcomm SoCs and there is no
way we are going to add another property for this now.

> informational (from the CPU perspective) rather than functional I feel like
> that using performance_state for this would be as hacky as using opp-microvolt
> or something else.

There is some WIP stuff here Rajendra is testing currently.

ssh://git at git.linaro.org/people/viresh.kumar/mylinux.git opp/genpd/qcom

Please have a talk with Rajendra who can help you understand on how this can be
used for GPUs.

-- 
viresh

  reply	other threads:[~2018-03-09  3:43 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
2018-03-08 20:14             ` Jordan Crouse
2018-03-09  3:43               ` Viresh Kumar [this message]
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=20180309034332.GO6842@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