devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: thierry.reding@gmail.com, jonathanh@nvidia.com,
	robh+dt@kernel.org, mark.rutland@arm.com
Cc: talho@nvidia.com, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Mikko Perttunen <mperttunen@nvidia.com>
Subject: [PATCH v3 5/7] dt-bindings: tegra: Add documentation for nvidia,tegra194-pmc
Date: Thu, 15 Feb 2018 16:52:04 +0200	[thread overview]
Message-ID: <20180215145206.24775-6-mperttunen@nvidia.com> (raw)
In-Reply-To: <20180215145206.24775-1-mperttunen@nvidia.com>

The Tegra194 power management controller has one additional register
aperture to be specified in the device tree node.

Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
 Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt
index 078a58b0302f..5a3bf7c5a7a0 100644
--- a/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt
+++ b/Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-pmc.txt
@@ -3,6 +3,7 @@ NVIDIA Tegra Power Management Controller (PMC)
 Required properties:
 - compatible: Should contain one of the following:
   - "nvidia,tegra186-pmc": for Tegra186
+  - "nvidia,tegra194-pmc": for Tegra194
 - reg: Must contain an (offset, length) pair of the register set for each
   entry in reg-names.
 - reg-names: Must include the following entries:
@@ -10,6 +11,7 @@ Required properties:
   - "wake"
   - "aotag"
   - "scratch"
+  - "misc" (Only for Tegra194)
 
 Optional properties:
 - nvidia,invert-interrupt: If present, inverts the PMU interrupt signal.
-- 
2.16.1

  parent reply	other threads:[~2018-02-15 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 14:51 [PATCH v3 0/7] Initial support for NVIDIA Tegra194 Mikko Perttunen
2018-02-15 14:52 ` [PATCH v3 1/7] firmware: tegra: Simplify channel management Mikko Perttunen
2018-02-15 14:52 ` [PATCH v3 2/7] soc/tegra: Add Tegra194 SoC configuration option Mikko Perttunen
2018-02-15 14:52 ` [PATCH v3 3/7] soc/tegra: pmc: Add Tegra194 compatibility string Mikko Perttunen
2018-02-15 14:52 ` Mikko Perttunen [this message]
2018-02-15 14:52 ` [PATCH v3 6/7] arm64: tegra: Add Tegra194 chip device tree Mikko Perttunen
     [not found]   ` <20180215145206.24775-7-mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-16 12:33     ` Philippe Ombredanne
2018-02-19  9:32       ` Mikko Perttunen
     [not found] ` <20180215145206.24775-1-mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2018-02-15 14:52   ` [PATCH v3 4/7] dt-bindings: tegra: Add missing chips and NVIDIA boards Mikko Perttunen
2018-02-15 14:52   ` [PATCH v3 7/7] arm64: tegra: Add device tree for the Tegra194 P2972-0000 board Mikko Perttunen

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=20180215145206.24775-6-mperttunen@nvidia.com \
    --to=mperttunen@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=talho@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;
as well as URLs for NNTP newsgroup(s).