On Tue, Mar 22, 2016 at 02:38:53PM +0800, jeffrey.lin wrote:
> Document the device tree binfings of Raydium I2C touch driver.
Is there a driver too?
> Signed-off-by: jeffrey.lin <jeffrey.lin@xxxxxxxxxx>
> ---
> .../devicetree/bindings/input/raydium_i2c_ts.txt | 21 +++++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> 2 files changed, 22 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/raydium_i2c_ts.txt
>
> diff --git a/Documentation/devicetree/bindings/input/raydium_i2c_ts.txt b/Documentation/devicetree/bindings/input/raydium_i2c_ts.txt
> new file mode 100644
> index 0000000..d7631d0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/raydium_i2c_ts.txt
> @@ -0,0 +1,21 @@
> +Raydium I2C touchscreen
> +
> +Required properties:
> +- compatible:
> + "raydium,rm3xxxx"
No wildcards in compatible strings please.
> +- reg: The I2C address of the device
> +- interrupts: interrupt to which the chip is connected
> + See ../interrupt-controller/interrupts.txt
> +Optional property:
properties
> + - avdd-supply : Analog power supply needed to power device
> + - vccio-supply : IO Power source
> +
> +Example:
> +
> + raydium_i2c@39 {
touchscreen@39
> + compatible = "raydium,rm3xxxx";\
Drop the \
> + reg = <0x39>;
> + interrupt-parent = <&gpio>;
> + interrupts = <0x0 IRQ_TYPE_EDGE_FALLING>;
> + };
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index af49e0f..5b6224b 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -126,6 +126,7 @@ radxa Radxa
> raidsonic RaidSonic Technology GmbH
> ralink Mediatek/Ralink Technology Corp.
> ramtron Ramtron International
> +raydium Raydium Semiconductor Corp.
> realtek Realtek Semiconductor Corp.
> renesas Renesas Electronics Corporation
> ricoh Ricoh Co. Ltd.
> --
> 2.1.2
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
