From: Laxman Dewangan <ldewangan@nvidia.com>
To: <thierry.reding@gmail.com>, <robh+dt@kernel.org>,
<swarren@wwwdotorg.org>, <gnurou@gmail.com>
Cc: <linux-pwm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 4/5] pwm: tegra: Add DT node compatible for Tegra186
Date: Wed, 22 Jun 2016 17:17:22 +0530 [thread overview]
Message-ID: <1466596043-27262-5-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1466596043-27262-1-git-send-email-ldewangan@nvidia.com>
Tegra186 has 8 different PWM controller and each controller has only
one output. Earlier generation SoCs have the 4 PWM output per controller.
Add DT node compatible for Tegra186.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt b/Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt
index c52f03b..2851b2d 100644
--- a/Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt
+++ b/Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.txt
@@ -1,10 +1,12 @@
Tegra SoC PWFM controller
Required properties:
-- compatible: For Tegra20, must contain "nvidia,tegra20-pwm". For Tegra30,
- must contain "nvidia,tegra30-pwm". Otherwise, must contain
- "nvidia,<chip>-pwm", plus one of the above, where <chip> is tegra114,
- tegra124, tegra132, or tegra210.
+- compatible: For Tegra20, must contain "nvidia,tegra20-pwm".
+ For Tegra30, must contain "nvidia,tegra30-pwm".
+ For Tegra114, Tegra124, Tegra132, Tegra210 must contain
+ "nvidia,<chip>-pwm", plus one of the above, where <chip> is
+ tegra114, tegra124, tegra132, or tegra210.
+ For Tegra186, must contain "nvidia,tegra186-pwm".
- reg: physical base address and length of the controller's registers
- #pwm-cells: should be 2. See pwm.txt in this directory for a description of
the cells format.
--
2.1.4
next prev parent reply other threads:[~2016-06-22 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 11:47 [PATCH 0/5] pwm: Fixes and support for Tegra186 Laxman Dewangan
2016-06-22 11:47 ` [PATCH 1/5] pwm: tegra: Add support for reset control Laxman Dewangan
2016-06-22 12:40 ` Thierry Reding
2016-06-22 11:47 ` [PATCH 2/5] pwm: tegra: Allow 100% duty cycle Laxman Dewangan
2016-06-22 11:47 ` [PATCH 3/5] pwm: tegra: fix overflow when calculating " Laxman Dewangan
2016-06-22 11:47 ` Laxman Dewangan [this message]
2016-06-22 12:46 ` [PATCH 4/5] pwm: tegra: Add DT node compatible for Tegra186 Thierry Reding
2016-06-24 16:10 ` Rob Herring
2016-06-24 21:30 ` Stephen Warren
2016-06-22 11:47 ` [PATCH 5/5] pwm: tegra: Add support " Laxman Dewangan
2016-06-30 9:15 ` Alexandre Courbot
2016-07-11 9:31 ` [PATCH 0/5] pwm: Fixes and " 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=1466596043-27262-5-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).