From: Rob Herring <robh@kernel.org>
To: "jeffrey.lin" <yajohn@gmail.com>
Cc: pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
dmitry.torokhov@gmail.com, djkurtz@chromium.org,
drinkcat@chromium.org, treding@nvidia.com,
ajaykumar.rs@samsung.com, dusonlin@emc.com.tw,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
jeffrey.lin@rad-ic.com, roger.yang@rad-ic.com, KP.li@rad-ic.com,
albert.shieh@rad-ic.com
Subject: Re: [PATCH] dt-bindings: input: add Raydium I2C touch driver bindings
Date: Wed, 23 Mar 2016 10:06:35 -0500 [thread overview]
Message-ID: <20160323150635.GA14699@rob-hp-laptop> (raw)
In-Reply-To: <1458628733-2277-1-git-send-email-jeffrey.lin@rad-ic.com>
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@rad-ic.com>
> ---
> .../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
>
prev parent reply other threads:[~2016-03-23 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 6:38 [PATCH] dt-bindings: input: add Raydium I2C touch driver bindings jeffrey.lin
2016-03-23 15:06 ` Rob Herring [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=20160323150635.GA14699@rob-hp-laptop \
--to=robh@kernel.org \
--cc=KP.li@rad-ic.com \
--cc=ajaykumar.rs@samsung.com \
--cc=albert.shieh@rad-ic.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=drinkcat@chromium.org \
--cc=dusonlin@emc.com.tw \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jeffrey.lin@rad-ic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=roger.yang@rad-ic.com \
--cc=treding@nvidia.com \
--cc=yajohn@gmail.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