From: Rob Herring <robh@kernel.org>
To: Mikko Perttunen <mperttunen@nvidia.com>
Cc: mark.rutland@arm.com, thierry.reding@gmail.com,
jonathanh@nvidia.com, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster
Date: Wed, 7 Jun 2017 17:11:02 -0500 [thread overview]
Message-ID: <20170607221102.2bctvsdciv7y26lk@rob-hp-laptop> (raw)
In-Reply-To: <1496304245-24024-2-git-send-email-mperttunen@nvidia.com>
On Thu, Jun 01, 2017 at 11:04:04AM +0300, Mikko Perttunen wrote:
> The Tegra186 CCPLEX_CLUSTER area contains memory-mapped
> registers that initiate CPU frequency/voltage transitions.
What the block is should also go in the binding doc. With that,
Acked-by: Rob Herring <robh@kernel.org>
>
> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> ---
> .../arm/tegra/nvidia,tegra186-ccplex-cluster.txt | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-ccplex-cluster.txt
next prev parent reply other threads:[~2017-06-07 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 8:04 [PATCH v2 0/2] Device tree changes for Tegra186 cpufreq Mikko Perttunen
2017-06-01 8:04 ` [PATCH v2 1/2] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster Mikko Perttunen
2017-06-07 22:11 ` Rob Herring [this message]
2017-06-08 7:32 ` Mikko Perttunen
2017-06-09 20:54 ` Rob Herring
2017-06-12 8:25 ` Mikko Perttunen
2017-06-12 10:23 ` [PATCH v3 " Mikko Perttunen
2017-06-13 12:42 ` Thierry Reding
2017-06-13 12:46 ` Mikko Perttunen
2017-06-13 12:47 ` Mikko Perttunen
2017-06-13 14:10 ` Thierry Reding
2017-06-01 8:04 ` [PATCH v2 2/2] arm64: tegra: Add CCPLEX_CLUSTER area in Tegra186 Mikko Perttunen
2017-06-13 12:45 ` Thierry Reding
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=20170607221102.2bctvsdciv7y26lk@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mperttunen@nvidia.com \
--cc=thierry.reding@gmail.com \
/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
all inboxes | Powered by JetHome®