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.si...@st.com> --- .../devicetree/bindings/net/nfc/st95hf.txt | 48 ++++++++++++++++++++++ 1 file changed, 48 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..4f90536 --- /dev/null +++ b/Documentation/devicetree/bindings/net/nfc/st95hf.txt @@ -0,0 +1,48 @@ +* 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. + +- 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 { + reg = <0x9840000 0x110>; + #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>; + enable-gpio = <&pio4 0>; + interrupt-parent = <&pio0>; + interrupts = <7 IRQ_TYPE_EDGE_FALLING>; + }; + + }; + -- 1.8.2.1 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html