From: Vignesh R <vigneshr@ti.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Vignesh R <vigneshr@ti.com>, <linux-pwm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 3/4] ARM: dts: keystone-k2g-evm: Enable PWM ECAP0
Date: Mon, 7 Aug 2017 17:19:42 +0530 [thread overview]
Message-ID: <20170807114943.22612-4-vigneshr@ti.com> (raw)
In-Reply-To: <20170807114943.22612-1-vigneshr@ti.com>
Enable PWM ECAP0 which will be used for display backlight.
Signed-off-by: Vignesh R <vigneshr@ti.com>
---
arch/arm/boot/dts/keystone-k2g-evm.dts | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/keystone-k2g-evm.dts b/arch/arm/boot/dts/keystone-k2g-evm.dts
index 61883cb969d2..3ce8010622ff 100644
--- a/arch/arm/boot/dts/keystone-k2g-evm.dts
+++ b/arch/arm/boot/dts/keystone-k2g-evm.dts
@@ -34,6 +34,12 @@
K2G_CORE_IOPAD(0x11d0) (BUFFER_CLASS_B | PIN_PULLDOWN | MUX_MODE0) /* uart0_txd.uart0_txd */
>;
};
+
+ ecap0_pins: ecap0_pins {
+ pinctrl-single,pins = <
+ K2G_CORE_IOPAD(0x1374) (BUFFER_CLASS_B | MUX_MODE4) /* pr1_mdio_data.ecap0_in_apwm0_out */
+ >;
+ };
};
&uart0 {
@@ -41,3 +47,9 @@
pinctrl-0 = <&uart0_pins>;
status = "okay";
};
+
+&ecap0 {
+ status = "okay";
+ pinctrl-names = "default";
+ pinctrl-0 = <&ecap0_pins>;
+};
--
2.13.3
next prev parent reply other threads:[~2017-08-07 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 11:49 [PATCH 0/4] K2G: Add support for PWM ECAP Vignesh R
2017-08-07 11:49 ` [PATCH 1/4] pwm: pwm-tiecap: Add TI 66AK2G SoC specific compatible Vignesh R
2017-08-10 20:52 ` Rob Herring
2017-08-21 6:12 ` Thierry Reding
2017-08-07 11:49 ` [PATCH 2/4] ARM: dts: keystone-k2g: Add ECAP PWM DT nodes Vignesh R
2017-08-07 11:49 ` Vignesh R [this message]
2017-08-07 11:49 ` [PATCH 4/4] ARM: configs: keystone: Enable TIECAP PWM driver Vignesh R
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=20170807114943.22612-4-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ssantosh@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;
as well as URLs for NNTP newsgroup(s).