From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: sdm845: Support GPU/GMU
Date: Tue, 6 Mar 2018 09:56:56 +0530 [thread overview]
Message-ID: <20180306042656.GJ23018@vireshk-i7> (raw)
In-Reply-To: <20180305152818.GC15200@jcrouse-lnx.qualcomm.com>
On 05-03-18, 08:28, Jordan Crouse wrote:
> I'm glad you brought this up - I was trying to find a place in the documentation
> to put it, but since target specific nodes would be a new trick for OPP I didn't
> quite know how to go about doing it. Do we just list them as Optional: or
> should we add a target specific section to the documentation and list them out
> there instead?
Something like this and you need to have your own compatible string as
well:
Documentation/devicetree/bindings/opp/ti-omap5-opp-supply.txt
But first, what's the purpose of this field? Just to check if it can
be handled by current bindings.
--
viresh
next prev parent reply other threads:[~2018-03-06 4:26 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 [this message]
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
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=20180306042656.GJ23018@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