devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jassisinghbrar@gmail.com
To: linux-spi@vger.kernel.org, devicetree@vger.kernel.org
Cc: tpiepho@impinj.com, broonie@kernel.org,
	ard.biesheuvel@linaro.org, robh+dt@kernel.org,
	mark.rutland@arm.com, masami.hiramatsu@linaro.org,
	Jassi Brar <jaswinder.singh@linaro.org>
Subject: [PATCHv4 1/3] dt-bindings: spi: Add DT bindings for Synquacer
Date: Tue, 27 Feb 2018 18:28:35 +0530	[thread overview]
Message-ID: <1519736315-3931-1-git-send-email-jassisinghbrar@gmail.com> (raw)
In-Reply-To: <1519736182-3650-1-git-send-email-jassisinghbrar@gmail.com>

From: Jassi Brar <jaswinder.singh@linaro.org>

This patch adds documentation for Device-Tree bindings for the
Socionext Synquacer spi driver.

Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
Reviewed-by: Rob Herring <robh@kernel.org>
---
 .../devicetree/bindings/spi/spi-synquacer.txt      | 23 ++++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/spi/spi-synquacer.txt

diff --git a/Documentation/devicetree/bindings/spi/spi-synquacer.txt b/Documentation/devicetree/bindings/spi/spi-synquacer.txt
new file mode 100644
index 0000000..d945a4a
--- /dev/null
+++ b/Documentation/devicetree/bindings/spi/spi-synquacer.txt
@@ -0,0 +1,23 @@
+* Socionext Synquacer HS-SPI bindings
+
+Required Properties:
+- compatible: should be "socionext,synquacer-spi"
+- reg: physical base address of the controller and length of memory mapped
+       region.
+- clocks: core clock iHCLK. Optional rate clock iPCLK (default is iHCLK)
+- clock-names: Shall be "iHCLK" and "iPCLK" respectively
+
+Optional Properties:
+- socionext,use-rtm: boolean, if required to use "retimed clock" for RX
+- socionext,set-aces: boolean, if same active clock edges field to be set.
+
+Example:
+
+	spi0: spi@ff110000 {
+		compatible = "socionext,synquacer-spi";
+		reg = <0xff110000 0x1000>;
+		clocks = <&clk_fip006_spi>;
+		clock-names = "iHCLK";
+		socionext,use-rtm;
+		socionext,set-aces;
+	};
-- 
2.7.4

  reply	other threads:[~2018-02-27 12:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 12:56 [PATCHv4 0/3] spi: support for Socionext Synquacer platform jassisinghbrar
2018-02-27 12:58 ` jassisinghbrar [this message]
2018-02-27 12:58 ` [PATCHv4 2/3] spi: Add spi driver " jassisinghbrar
2018-02-28 11:17   ` Geert Uytterhoeven
2018-02-28 18:35     ` Jassi Brar
2018-02-28 17:55   ` Trent Piepho
2018-02-28 18:29     ` Jassi Brar
2018-02-28 18:36       ` Ard Biesheuvel
2018-03-01 14:11         ` Jassi Brar
2018-02-28 18:57       ` Trent Piepho
2018-03-01 10:02   ` Andy Shevchenko
2018-03-01 10:04     ` Andy Shevchenko
2018-02-27 12:59 ` [PATCHv4 3/3] MAINTAINERS: Add entry for Synquacer SPI driver jassisinghbrar
2018-02-27 13:49 ` [PATCHv4 0/3] spi: support for Socionext Synquacer platform 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=1519736315-3931-1-git-send-email-jassisinghbrar@gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masami.hiramatsu@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=tpiepho@impinj.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).