Linux wireless drivers development
 help / color / mirror / Atom feed
From: Shikha Singh <shikha.singh@st.com>
To: <sameo@linux.intel.com>, <aloisio.almeida@openbossa.org>,
	<lauro.venancio@openbossa.org>, <linux-wireless@vger.kernel.org>,
	<linux-nfc@lists.01.org>
Cc: <raunaque.quaiser@st.com>, <manoj.kumar@st.com>,
	<sylvain.fidelis@st.com>, <patrick.sohn@st.com>,
	<shikha.singh@st.com>
Subject: [[linux-nfc] PATCH v1.0 3/3] DT: bindings: net: nfc: ST95HF binding doc
Date: Sat, 12 Sep 2015 03:21:35 -0400	[thread overview]
Message-ID: <1442042495-2407-4-git-send-email-shikha.singh@st.com> (raw)
In-Reply-To: <1442042495-2407-1-git-send-email-shikha.singh@st.com>

This patch includes ST95HF binding doc that guides how to
make node entry of ST95HF in DT file of any platform.

Signed-off-by: Shikha Singh <shikha.singh@st.com>
---
 .../devicetree/bindings/net/nfc/st95hf.txt         | 55 ++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/net/nfc/st95hf.txt

diff --git a/Documentation/devicetree/bindings/net/nfc/st95hf.txt b/Documentation/devicetree/bindings/net/nfc/st95hf.txt
new file mode 100644
index 0000000..baa4819
--- /dev/null
+++ b/Documentation/devicetree/bindings/net/nfc/st95hf.txt
@@ -0,0 +1,55 @@
+STMicroelectronics NFC Transceiver ST95HF
+-----------------------------------------
+
+ST NFC Transceiver is required to attach with SPI bus.
+ST95HF should be defined in DT as SPI slave device of SPI master
+with which transceiver is physically connected.
+The properties defined below are required to be the part of DT
+to include transceiver into the platform.
+
+Required properties:
+
+- reg: Address of SPI slave "transceiver" on SPI master bus.
+
+- compatible: should be "st,st95hf" for ST NFC transceiver
+
+- spi-max-frequency: Max. operating SPI frequency for transceiver.
+
+- st,st95hf-enable-gpio: GPIO line used to enable transceiver.
+
+- interrupt-parent : Standard way to specify the controller to which
+		transceiver interrupt is routed.
+
+- interrupts : Standard way to define device (transceiver's out) interrupt.
+
+Optional property:
+
+- st95hfvin-supply : This is an optional property.It contains a phandle to
+		transceiver regulator supply node in DT.
+
+Example:
+	 spi@9840000 {
+                        compatible = "st,comms-ssc4-spi";
+                        reg = <0x9840000 0x110>;
+                        interrupts = <GIC_SPI 112 IRQ_TYPE_LEVEL_HIGH>;
+                        clocks = <&clk_s_c0_flexgen CLK_EXT2F_A9>;
+                        clock-names = "ssc";
+                        pinctrl-0 = <&pinctrl_spi0_default>;
+                        pinctrl-names = "default";
+                        #address-cells = <1>;
+                        #size-cells = <0>;
+                        cs-gpios = <&pio0 4>;
+                        status = "okay";
+
+                        st95hf@0{
+                                reg = <0>;
+                                compatible = "st,st95hf";
+                                status = "okay";
+                                spi-max-frequency = <1000000>;
+                                st,st95hf-enable-gpio = <&pio4 0>;
+                                interrupt-parent = <&pio0>;
+                                interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
+                        };
+
+                };
+
-- 
1.8.2.1


      parent reply	other threads:[~2015-09-12  7:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12  7:21 [[linux-nfc] PATCH v1.0 0/3] Add support for ST95HF Shikha Singh
2015-09-12  7:21 ` [[linux-nfc] PATCH v1.0 1/3] NFC: digital: Type4A tags support Shikha Singh
2015-09-12  7:21 ` [[linux-nfc] PATCH v1.0 2/3] driver: nfc: st95hf: ST NFC Transceiver support Shikha Singh
2015-10-22  6:24   ` Samuel Ortiz
2015-10-26  5:57     ` Shikha SINGH
2015-11-06  9:13     ` Shikha SINGH
2015-09-12  7:21 ` Shikha Singh [this message]

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=1442042495-2407-4-git-send-email-shikha.singh@st.com \
    --to=shikha.singh@st.com \
    --cc=aloisio.almeida@openbossa.org \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-nfc@lists.01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=manoj.kumar@st.com \
    --cc=patrick.sohn@st.com \
    --cc=raunaque.quaiser@st.com \
    --cc=sameo@linux.intel.com \
    --cc=sylvain.fidelis@st.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