From: Xiubo Li <Li.Xiubo@freescale.com>
To: daniel.lezcano@linaro.org, tglx@linutronix.de,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rob@landley.net
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Xiubo Li <Li.Xiubo@freescale.com>,
Shawn Guo <shawn.guo@linaro.org>,
Jingchang Lu <b35083@freescale.com>
Subject: [PATCH] clocksource: pit: Add Freescale PIT-RTI devicetree Documentation
Date: Thu, 17 Apr 2014 13:59:49 +0800 [thread overview]
Message-ID: <1397714389-10263-1-git-send-email-Li.Xiubo@freescale.com> (raw)
This add Freescale Periodic Interrupt Timer (PIT-RTI) devicetree
Documentation, The PIT-RTI binding has already been used on Vybrid,
so this add a binding document for it.
Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
Cc: Shawn Guo <shawn.guo@linaro.org>
Cc: Jingchang Lu <b35083@freescale.com>
---
.../devicetree/bindings/timer/fsl,vf610-pit.txt | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/fsl,vf610-pit.txt
diff --git a/Documentation/devicetree/bindings/timer/fsl,vf610-pit.txt b/Documentation/devicetree/bindings/timer/fsl,vf610-pit.txt
new file mode 100644
index 0000000..67df182
--- /dev/null
+++ b/Documentation/devicetree/bindings/timer/fsl,vf610-pit.txt
@@ -0,0 +1,21 @@
+Freescale Periodic Interrupt Timer (PIT-RTI)
+
+Required properties:
+
+- compatible : should be "fsl,vf610-pit"
+- reg : Specifies base physical address and size of the register set for the
+ clock event device and clock source device.
+- interrupts : Should be the clock event device interrupt.
+- clocks : The clocks provided by the SoC to drive the timer, must contain an
+ entry for each entry in clock-names.
+- clock-names : Must include the "pit" entry.
+
+Example:
+
+pit: pit@40037000 {
+ compatible = "fsl,vf610-pit";
+ reg = <0x40037000 0x1000>;
+ interrupts = <0 39 IRQ_TYPE_LEVEL_HIGH>;
+ clocks = <&clks VF610_CLK_PIT>;
+ clock-names = "pit";
+};
--
1.8.4
reply other threads:[~2014-04-17 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1397714389-10263-1-git-send-email-Li.Xiubo@freescale.com \
--to=li.xiubo@freescale.com \
--cc=b35083@freescale.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
/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).