linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: <sandeep@freescale.com>
To: <linuxppc-dev@ozlabs.org>
Subject: [3/3][PATCH] powerpc/85xx: Device tree entry for Freescale TDM controller.
Date: Thu, 2 Apr 2015 16:19:20 +0530	[thread overview]
Message-ID: <1427971760-32445-1-git-send-email-sandeep@freescale.com> (raw)

From: Sandeep Singh <sandeep@freescale.com>

Add device tree for TDM on QorIQ chips.

Signed-off-by: Sandeep Singh <sandeep@freescale.com>
Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
---
 arch/powerpc/boot/dts/fsl/qoriq-tdm1.0.dtsi | 41 +++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 arch/powerpc/boot/dts/fsl/qoriq-tdm1.0.dtsi

diff --git a/arch/powerpc/boot/dts/fsl/qoriq-tdm1.0.dtsi b/arch/powerpc/boot/dts/fsl/qoriq-tdm1.0.dtsi
new file mode 100644
index 0000000..f70ad37
--- /dev/null
+++ b/arch/powerpc/boot/dts/fsl/qoriq-tdm1.0.dtsi
@@ -0,0 +1,41 @@
+/*
+ * QorIQ TDM device tree stub [ controller @ offset 0x185000 ]
+ *
+ * Copyright 2013 Freescale Semiconductor Inc.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions are met:
+ *     * Redistributions of source code must retain the above copyright
+ *       notice, this list of conditions and the following disclaimer.
+ *     * Redistributions in binary form must reproduce the above copyright
+ *       notice, this list of conditions and the following disclaimer in the
+ *       documentation and/or other materials provided with the distribution.
+ *     * Neither the name of Freescale Semiconductor nor the
+ *       names of its contributors may be used to endorse or promote products
+ *       derived from this software without specific prior written permission.
+ *
+ *
+ * ALTERNATIVELY, this software may be distributed under the terms of the
+ * GNU General Public License ("GPL") as published by the Free Software
+ * Foundation, either version 2 of that License or (at your option) any
+ * later version.
+ *
+ * THIS SOFTWARE IS PROVIDED BY Freescale Semiconductor ``AS IS'' AND ANY
+ * EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+ * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+ * DISCLAIMED. IN NO EVENT SHALL Freescale Semiconductor BE LIABLE FOR ANY
+ * DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+ * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+ * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+ * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+ */
+
+tdm@185000 {
+	compatible = "fsl,tdm1.0";
+	reg = <0x185000 0x200 0x186000 0x2000>;
+	clock-frequency = <0>;
+	interrupts = <49 8 0 0>;
+	fsl,max-time-slots = <128>;
+};
-- 
1.8.1.4

                 reply	other threads:[~2015-04-02 11:05 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=1427971760-32445-1-git-send-email-sandeep@freescale.com \
    --to=sandeep@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).