public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Mikko Perttunen <mperttunen@nvidia.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, jonathanh@nvidia.com,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: tegra: Add CCPLEX_CLUSTER area in Tegra186
Date: Tue, 13 Jun 2017 14:45:52 +0200	[thread overview]
Message-ID: <20170613124552.GD16758@ulmo.fritz.box> (raw)
In-Reply-To: <1496304245-24024-3-git-send-email-mperttunen@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 380 bytes --]

On Thu, Jun 01, 2017 at 11:04:05AM +0300, Mikko Perttunen wrote:
> The Tegra186 CCPLEX_CLUSTER area contains memory-mapped
> registers that initiate CPU frequency/voltage transitions.
> 
> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> ---
>  arch/arm64/boot/dts/nvidia/tegra186.dtsi | 7 +++++++
>  1 file changed, 7 insertions(+)

Applied, thanks.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-06-13 12:45 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
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 [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=20170613124552.GD16758@ulmo.fritz.box \
    --to=thierry.reding@gmail.com \
    --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=robh+dt@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