From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] ARM: dts: keystone: Add clock phandle to UART nodes
Date: Thu, 29 Aug 2013 19:36:42 -0400 [thread overview]
Message-ID: <1377819404-9671-3-git-send-email-santosh.shilimkar@ti.com> (raw)
In-Reply-To: <1377819404-9671-1-git-send-email-santosh.shilimkar@ti.com>
Now since the clock tree is added, update UART dt nodes with clock data.
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
---
arch/arm/boot/dts/keystone.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/keystone.dts b/arch/arm/boot/dts/keystone.dts
index 57a7cd9..5a2d632 100644
--- a/arch/arm/boot/dts/keystone.dts
+++ b/arch/arm/boot/dts/keystone.dts
@@ -102,6 +102,7 @@
reg-io-width = <4>;
reg = <0x02530c00 0x100>;
clock-frequency = <133120000>;
+ clocks = <&clkuart0>;
interrupts = <0 277 0xf01>;
};
@@ -112,6 +113,7 @@
reg-io-width = <4>;
reg = <0x02531000 0x100>;
clock-frequency = <133120000>;
+ clocks = <&clkuart1>;
interrupts = <0 280 0xf01>;
};
--
1.7.9.5
next prev parent reply other threads:[~2013-08-29 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 23:36 [PATCH v2 0/4] ARM: keystone: clock tree and PM bus support Santosh Shilimkar
2013-08-29 23:36 ` [PATCH v2 1/4] ARM: dts: keystone: Add clock tree data to devicetree Santosh Shilimkar
2013-08-29 23:36 ` Santosh Shilimkar [this message]
2013-08-29 23:36 ` [PATCH v2 3/4] ARM: keystone: Enable clock drivers Santosh Shilimkar
2013-08-29 23:36 ` [PATCH v2 4/4] ARM: keystone: add PM bus support for clock management Santosh Shilimkar
2013-08-30 16:18 ` Kevin Hilman
2013-08-30 16:25 ` Santosh Shilimkar
2013-10-11 0:15 ` Santosh Shilimkar
2013-10-14 17:32 ` Kevin Hilman
2013-10-14 18:00 ` Santosh Shilimkar
2013-10-14 18:18 ` Kevin Hilman
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=1377819404-9671-3-git-send-email-santosh.shilimkar@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).