From: Rajendra Nayak <rnayak@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org, vireshk@kernel.org, nm@ti.com,
sboyd@codeaurora.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, dianders@chromium.org,
linux-arm-kernel@lists.infradead.org, sboyd@kernel.org
Subject: Re: [Freedreno] [PATCH 2/2] arm64: dts: sdm845: Support GPU/GMU
Date: Fri, 9 Mar 2018 15:49:00 +0530 [thread overview]
Message-ID: <4fd61bd2-757b-ef30-a07f-ed74af031ff5@codeaurora.org> (raw)
In-Reply-To: <20180309034332.GO6842@vireshk-i7>
Hey Jordan/Viresh,
On 03/09/2018 09:13 AM, Viresh Kumar wrote:
> 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.
What I am doing is a powerdomain driver to communicate magic values from
CPU to rpmh, looks like we need another one to communicate from CPU to
GMU now :)
A few things,
* someone will need to map these larger magic values into something that
rpmh would understand (between 0 to 15 on the sdm845), thats done by
reading the command db level maps. Is this done by GMU?
* are these communicated just once for every OPP at init/boot, or for
every OPP switch?
* whats the communication mechanism we use between CPU and GMU?
regards
Rajendra
>
> ssh://git@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.
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@codeaurora.org (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [Freedreno] [PATCH 2/2] arm64: dts: sdm845: Support GPU/GMU
Date: Fri, 9 Mar 2018 15:49:00 +0530 [thread overview]
Message-ID: <4fd61bd2-757b-ef30-a07f-ed74af031ff5@codeaurora.org> (raw)
In-Reply-To: <20180309034332.GO6842@vireshk-i7>
Hey Jordan/Viresh,
On 03/09/2018 09:13 AM, Viresh Kumar wrote:
> 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.
What I am doing is a powerdomain driver to communicate magic values from
CPU to rpmh, looks like we need another one to communicate from CPU to
GMU now :)
A few things,
* someone will need to map these larger magic values into something that
rpmh would understand (between 0 to 15 on the sdm845), thats done by
reading the command db level maps. Is this done by GMU?
* are these communicated just once for every OPP at init/boot, or for
every OPP switch?
* whats the communication mechanism we use between CPU and GMU?
regards
Rajendra
>
> 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.
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2018-03-09 10:19 UTC|newest]
Thread overview: 40+ 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 ` Jordan Crouse
[not found] ` <20180302215638.6145-1-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-03-02 21:56 ` [PATCH 1/2] dt-bindings: Document qcom,adreno-gmu Jordan Crouse
2018-03-02 21:56 ` Jordan Crouse
[not found] ` <20180302215638.6145-2-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-03-05 19:38 ` Rob Herring
2018-03-05 19:38 ` Rob Herring
2018-03-16 18:27 ` Jordan Crouse
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-02 21:56 ` Jordan Crouse
[not found] ` <20180302215638.6145-3-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-03-05 4:42 ` Viresh Kumar
2018-03-05 4:42 ` Viresh Kumar
2018-03-05 15:28 ` Jordan Crouse
2018-03-05 15:28 ` Jordan Crouse
[not found] ` <20180305152818.GC15200-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-03-06 4:26 ` Viresh Kumar
2018-03-06 4:26 ` Viresh Kumar
2018-03-06 15:37 ` [Freedreno] " Jordan Crouse
2018-03-06 15:37 ` Jordan Crouse
[not found] ` <20180306153757.GD15200-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-03-07 5:06 ` Viresh Kumar
2018-03-07 5:06 ` [Freedreno] " Viresh Kumar
2018-03-08 20:14 ` Jordan Crouse
2018-03-08 20:14 ` [Freedreno] " Jordan Crouse
[not found] ` <20180308201438.GA10589-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-03-09 3:43 ` Viresh Kumar
2018-03-09 3:43 ` [Freedreno] " Viresh Kumar
2018-03-09 10:19 ` Rajendra Nayak [this message]
2018-03-09 10:19 ` Rajendra Nayak
[not found] ` <4fd61bd2-757b-ef30-a07f-ed74af031ff5-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-03-09 15:47 ` Jordan Crouse
2018-03-09 15:47 ` [Freedreno] " Jordan Crouse
2018-03-09 16:03 ` Jordan Crouse
2018-03-09 16:03 ` [Freedreno] " Jordan Crouse
2018-03-09 17:18 ` Stephen Boyd
2018-03-09 17:18 ` Stephen Boyd
[not found] ` <152061592175.13890.6455929815877326231-n1Xw8LXHxjTHt/MElyovVYaSKrA+ACpX0E9HWUfgJXw@public.gmane.org>
2018-03-09 17:42 ` Jordan Crouse
2018-03-09 17:42 ` [Freedreno] " Jordan Crouse
[not found] ` <20180309174246.GD10589-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-03-12 5:54 ` Viresh Kumar
2018-03-12 5:54 ` [Freedreno] " Viresh Kumar
[not found] ` <20180309160355.GC10589-9PYrDHPZ2Orvke4nUoYGnHL1okKdlPRT@public.gmane.org>
2018-03-12 5:52 ` Viresh Kumar
2018-03-12 5:52 ` [Freedreno] " Viresh Kumar
2018-03-13 18:23 ` Stephen Boyd
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=4fd61bd2-757b-ef30-a07f-ed74af031ff5@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.