public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: ivan.khoronzhuk@ti•com (ivan.khoronzhuk)
To: linux-arm-kernel@lists•infradead.org
Subject: Fwd: [PATCH 7/8] watchdog: davinci: add "clocks" property
Date: Wed, 6 Nov 2013 13:32:56 +0200	[thread overview]
Message-ID: <527A28E8.4010204@ti.com> (raw)
In-Reply-To: <1383680783-12114-8-git-send-email-ivan.khoronzhuk@ti.com>

The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.

Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti•com>
---
 .../devicetree/bindings/watchdog/davinci-wdt.txt   |    5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt b/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
index fddced9..4db4d0e 100644
--- a/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
+++ b/Documentation/devicetree/bindings/watchdog/davinci-wdt.txt
@@ -7,6 +7,10 @@ Required properties:
 
 - reg : Should contain WDT registers location and length
 
+- clocks: phandle reference to the controller clock.
+	  Required only for Keystone arch.
+	  See clock-bindings.txt
+
 Optional properties:
 
 - timeout-sec:		Contains the watchdog timeout in seconds
@@ -21,4 +25,5 @@ wdt: wdt at 2320000 {
 	compatible = "ti,davinci-wdt";
 	reg = <0x02320000 0x80>;
 	timeout-sec = <30>;
+	clocks = <&clkwdtimer0>;
 };
-- 
1.7.9.5

       reply	other threads:[~2013-11-06 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1383680783-12114-8-git-send-email-ivan.khoronzhuk@ti.com>
2013-11-06 11:32 ` ivan.khoronzhuk [this message]
2013-11-12 15:40   ` Fwd: [PATCH 7/8] watchdog: davinci: add "clocks" property Santosh Shilimkar
2013-11-17  2:28   ` Guenter Roeck
2013-11-18 15:26     ` ivan.khoronzhuk
2013-11-23 17:57   ` Arnd Bergmann
2013-11-25 10:59     ` ivan.khoronzhuk
2013-11-25 12:15       ` Mark Rutland
2013-11-25 12:41         ` ivan.khoronzhuk

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=527A28E8.4010204@ti.com \
    --to=ivan.khoronzhuk@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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