From: Mikko Perttunen <mperttunen@nvidia.com>
To: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>
Cc: <devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH v2 0/2] Device tree changes for Tegra186 cpufreq
Date: Thu, 1 Jun 2017 11:04:03 +0300 [thread overview]
Message-ID: <1496304245-24024-1-git-send-email-mperttunen@nvidia.com> (raw)
Hi,
these are the device tree and bindings changes for the Tegra186 cpufreq
driver that was recently merged. The patches are the same as those that
were originally posted with the driver.
Mikko Perttunen (2):
dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster
arm64: tegra: Add CCPLEX_CLUSTER area in Tegra186
.../arm/tegra/nvidia,tegra186-ccplex-cluster.txt | 17 +++++++++++++++++
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 7 +++++++
2 files changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-ccplex-cluster.txt
--
2.1.4
next reply other threads:[~2017-06-01 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 8:04 Mikko Perttunen [this message]
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
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=1496304245-24024-1-git-send-email-mperttunen@nvidia.com \
--to=mperttunen@nvidia.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=robh+dt@kernel.org \
--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®