From: Stephen Boyd <sboyd@kernel.org>
To: Doug Anderson <dianders@chromium.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Rob Herring <robh@kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
devicetree@vger.kernel.org,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
freedreno <freedreno@lists.freedesktop.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Viresh Kumar <vireshk@kernel.org>
Subject: Re: [PATCH v6 2/2] arm64: dts: sdm845: Add gpu and gmu device nodes
Date: Fri, 04 Jan 2019 12:59:02 -0800 [thread overview]
Message-ID: <154663554289.15366.16011609839106849298@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <dcb3e046-d0bd-af68-e42d-1db0db3bf2df@codeaurora.org>
Quoting Rajendra Nayak (2019-01-03 00:45:53)
>
> On 12/29/2018 6:59 AM, Stephen Boyd wrote:
> >> So I am guessing the conclusion is to use a fallback "operating-points-v2"
> >> compatible*only* when we do have opp-hz along with qcom,level (as in the
> >> case with gpu) and not have a fallback compatible in cases when we don't
> >> have opp-hz (as in the case of rpm power domains)?
> >> That seems a little inconsistent, and given Rob said either way is fine,
> >> just do one way or the other and not both, I am inclined to think we should
> >> just have a "operating-points-v2-qcom-level" and no fallback compatible.
> >> Does that make sense?
> >>
> > Are you going to update the skip table to not create platform devices?
> > Or introduce some generic property to indicate that this is just data
> > and not a device node?
>
> Is any of it really needed, given the bindings specify that the OPP table
> should actually be a child node of the device/power domain supporting
> it? I don't see who would end up creating platform devices for them.
>
Good point. If it's a child node then almost all the time we won't be
trying to populate the OPP node as another platform device so this isn't
really important to handle until that happens, which is probably never.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-04 20:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 21:18 [PATCH v6 0/2] arm64: dts: Add sdm845 GPU/GMU and SMMU Jordan Crouse
2018-12-12 21:18 ` [PATCH v6 1/2] dt-bindings: drm/msm/a6xx: Document GMU and update GPU bindings Jordan Crouse
2018-12-13 18:39 ` Doug Anderson
2018-12-17 21:20 ` Rob Herring
2018-12-17 22:01 ` Jordan Crouse
2018-12-12 21:18 ` [PATCH v6 2/2] arm64: dts: sdm845: Add gpu and gmu device nodes Jordan Crouse
2018-12-13 18:40 ` Doug Anderson
2018-12-14 4:40 ` Viresh Kumar
2018-12-14 17:04 ` Doug Anderson
2018-12-17 7:06 ` Viresh Kumar
2018-12-18 0:34 ` Doug Anderson
2018-12-18 18:40 ` Stephen Boyd
2018-12-18 19:05 ` Doug Anderson
2018-12-19 4:49 ` Viresh Kumar
2018-12-19 20:08 ` Rob Herring
2018-12-19 20:40 ` Doug Anderson
2018-12-19 22:40 ` Doug Anderson
2018-12-19 23:47 ` Rob Herring
2018-12-20 21:29 ` Stephen Boyd
2018-12-21 4:52 ` Rajendra Nayak
2018-12-29 1:29 ` Stephen Boyd
2019-01-03 8:45 ` Rajendra Nayak
2019-01-04 20:59 ` Stephen Boyd [this message]
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=154663554289.15366.16011609839106849298@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jcrouse@codeaurora.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=rnayak@codeaurora.org \
--cc=robh@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 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).