devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: addy ke <addy.ke@rock-chips.com>
To: broonie@kernel.org, heiko@sntech.de, grant.likely@linaro.org,
	robh+dt@kernel.org
Cc: huangtao@rock-chips.com, devicetree@vger.kernel.org,
	addy ke <addy.ke@rock-chips.com>,
	yzq@rock-chips.com, linux-kernel@vger.kernel.org,
	linux-spi@vger.kernel.org, kever.yang@rock-chips.com,
	zyw@rock-chips.com, xjq@rock-chips.com,
	zhenfu.fang@rock-chips.com, olof@lixom.net, cf@rock-chips.com,
	hj@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] documentation: add rockchip spi documentation
Date: Tue, 24 Jun 2014 11:58:43 +0800	[thread overview]
Message-ID: <1403582324-9485-2-git-send-email-addy.ke@rock-chips.com> (raw)
In-Reply-To: <1403582324-9485-1-git-send-email-addy.ke@rock-chips.com>

Signed-off-by: addy ke <addy.ke@rock-chips.com>
---
 .../devicetree/bindings/spi/spi-rockchip.txt       | 51 ++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/spi/spi-rockchip.txt

diff --git a/Documentation/devicetree/bindings/spi/spi-rockchip.txt b/Documentation/devicetree/bindings/spi/spi-rockchip.txt
new file mode 100644
index 0000000..ce9c881
--- /dev/null
+++ b/Documentation/devicetree/bindings/spi/spi-rockchip.txt
@@ -0,0 +1,51 @@
+* Rockchip SPI Controller
+
+The Rockchip SPI controller is used to interface with various devices such as flash
+and display controllers using the SPI communication interface.
+
+Required SoC Specific Properties:
+
+- compatible: should be one of the following.
+    - rockchip,rk3066-spi: for rk3066, rk3188 and rk3288 platforms.
+- reg: physical base address of the controller and length of memory mapped
+       region.
+- interrupts: The interrupt number to the cpu. The interrupt specifier format
+              depends on the interrupt controller.
+- clocks: Must contain an entry for each entry in clock-names.
+- clock-names: Shall be "spiclk" for the transfer-clock, and "apb_pclk" for
+			   the peripheral clock.
+
+Optional properties:
+- dmas: DMA specifiers for tx and rx dma. See the DMA client binding,
+		Documentation/devicetree/bindings/dma/dma.txt
+- dma-names: DMA request names should include "tx" and "rx" if present.
+
+Example:
+
+- SoC Specific Portion:
+
+	spi0: spi@ff110000 {
+		compatible = "rockchip,rockchip-spi";
+		reg = <0xff110000 0x1000>;
+		dmas = <&pdma1 11>, <&pdma1 12>;
+		dma-names = "tx", "rx";
+		#address-cells = <1>;
+		#size-cells = <0>;
+		interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&spi0_clk &spi0_tx &spi0_rx &spi0_cs0 &spi0_cs1>;
+		clocks = <&cru SCLK_SPI0>, <&cru PCLK_SPI0>;
+		clock-names = "spiclk", "apb_pclk";
+		status = "disabled";
+	};
+
+- Board Specific Portion:
+
+	&spi0 {
+		status = "okay";
+		spi_test@00 {
+			compatible = "rockchip,spi_test";
+			reg = <0>;
+			spi-max-frequency = <24000000>;
+		};
+	};
-- 
1.8.3.2

  reply	other threads:[~2014-06-24  3:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  3:58 [PATCH 0/2] add rockchip spi drive addy ke
2014-06-24  3:58 ` addy ke [this message]
     [not found]   ` <1403582324-9485-2-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-06-24 10:18     ` [PATCH 1/2] documentation: add rockchip spi documentation Mark Rutland
2014-06-24 10:32       ` Heiko Stübner
2014-06-24 10:47         ` Mark Rutland
2014-06-24 10:33       ` Mark Brown
2014-07-01  1:02     ` [PATCH v2 " addy ke
     [not found] ` <1403582324-9485-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-06-24  4:07   ` [PATCH 2/2] spi: add driver for Rockchip RK3xxx SoCs integrated SPI addy ke
     [not found]     ` <1403582852-9751-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-06-24 10:56       ` Mark Brown
2014-07-01  1:03       ` [PATCH v2 " addy ke
     [not found]         ` <1404176639-3315-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-04 18:32           ` Mark Brown
     [not found]             ` <20140704183249.GC14896-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-05 18:56               ` Jonas Gorski
2014-07-07  1:42               ` addy ke
2014-07-07  7:08                 ` Heiko Stübner
2014-07-07  7:21                   ` Mark Brown
     [not found]                     ` <20140707072140.GB30458-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-07  7:26                       ` Heiko Stübner
     [not found]                 ` <53B9FB1C.7080008-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-07  7:16                   ` Mark Brown
2014-07-08  1:53           ` [PATCH v3 " Addy Ke
     [not found]             ` <1404784397-5157-1-git-send-email-addy.ke-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-08 14:56               ` Mark Brown

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=1403582324-9485-2-git-send-email-addy.ke@rock-chips.com \
    --to=addy.ke@rock-chips.com \
    --cc=broonie@kernel.org \
    --cc=cf@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=heiko@sntech.de \
    --cc=hj@rock-chips.com \
    --cc=huangtao@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=robh+dt@kernel.org \
    --cc=xjq@rock-chips.com \
    --cc=yzq@rock-chips.com \
    --cc=zhenfu.fang@rock-chips.com \
    --cc=zyw@rock-chips.com \
    /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).