linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: leilk.liu@mediatek.com (leilk.liu at mediatek.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] dt-bindings: ARM: Mediatek: Document devicetree bindings for spi bus
Date: Fri, 8 May 2015 16:55:41 +0800	[thread overview]
Message-ID: <1431075343-7887-2-git-send-email-leilk.liu@mediatek.com> (raw)
In-Reply-To: <1431075343-7887-1-git-send-email-leilk.liu@mediatek.com>

From: Leilk Liu <leilk.liu@mediatek.com>

Signed-off-by: Leilk Liu <leilk.liu@mediatek.com>
---
 .../devicetree/bindings/spi/spi-mt65xx.txt         | 32 ++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/spi/spi-mt65xx.txt

diff --git a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt b/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
new file mode 100644
index 0000000..04c28fd
--- /dev/null
+++ b/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
@@ -0,0 +1,32 @@
+MTK SPI device
+
+Required properties:
+- compatible: should be one of the following.
+    - mediatek,mt8173-spi: for mt8173 platforms
+    - mediatek,mt8135-spi: for mt8135 platforms
+    - mediatek,mt6589-spi: for mt6589 platforms
+
+- reg: Address and length of the register set for the device
+
+- interrupts: Should contain spi interrupt
+
+- clock-names: tuple listing input clock names.
+	Required elements: "main"
+
+- clocks: phandles to input clocks.
+
+- pad-select: should specify spi pad used, only required for MT8173.
+	This value should be 0~3.
+
+Example:
+
+- SoC Specific Portion:
+spi: spi at 1100a000 {
+	compatible = "mediatek,mt8173-spi";
+	reg = <0 0x1100a000 0 0x1000>;
+	interrupts = <GIC_SPI 110 IRQ_TYPE_LEVEL_LOW>;
+	clocks = <&pericfg PERI_SPI0>;
+	clock-names = "main";
+	pad-select = <1>;
+	status = "disabled";
+};
-- 
1.8.1.1.dirty

  reply	other threads:[~2015-05-08  8:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  8:55 Add Mediatek SPI driver leilk.liu at mediatek.com
2015-05-08  8:55 ` leilk.liu at mediatek.com [this message]
2015-05-08  8:55 ` [PATCH 2/3] spi: mediatek: Add spi bus for Mediatek MT8173 leilk.liu at mediatek.com
2015-05-08 17:53   ` Mark Brown
2015-05-12 12:39     ` leilk liu
2015-05-12 16:05       ` Mark Brown
2015-05-13  9:26         ` Yingjoe Chen
2015-05-13 11:10           ` Mark Brown
2015-05-13 13:58             ` Yingjoe Chen
2015-05-15  7:38         ` leilk liu
2015-05-15  9:25           ` Mark Brown
2015-06-08 10:15             ` Eddie Huang
2015-06-08 17:59               ` Mark Brown
2015-06-09 10:05                 ` Eddie Huang
2015-06-09 10:39                   ` Mark Brown
2015-06-10  8:06                     ` Eddie Huang
2015-06-17  9:08                       ` Eddie Huang
2015-06-17 12:47                         ` Mark Brown
2015-06-17 14:10                           ` Eddie Huang
2015-06-17 16:35                             ` Mark Brown
2015-06-18  8:11                               ` Eddie Huang
2015-05-08  8:55 ` [PATCH 3/3] arm64: dts: Add spi bus dts leilk.liu at mediatek.com

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=1431075343-7887-2-git-send-email-leilk.liu@mediatek.com \
    --to=leilk.liu@mediatek.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).