From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Sangwon Jee <jeesw@melfas.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Input: melfas_mip4 - add documentations
Date: Wed, 5 Oct 2016 22:58:18 -0700 [thread overview]
Message-ID: <20161006055818.GC36340@dtor-ws> (raw)
In-Reply-To: <1474953573-29327-1-git-send-email-jeesw@melfas.com>
Hi Sangwon,
On Tue, Sep 27, 2016 at 02:19:33PM +0900, Sangwon Jee wrote:
> Add maintainer and devicetree documentations.
>
> Signed-off-by: Sangwon Jee <jeesw@melfas.com>
> ---
> .../bindings/input/touchscreen/melfas_mip4.txt | 21 +++++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
Could you please split this in 2: separate patch for bindings and
separate for maintainers.
Thanks!
> MAINTAINERS | 7 +++++++
> 3 files changed, 29 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt b/Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt
> new file mode 100644
> index 0000000..4e4dfbe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/input/touchscreen/melfas_mip4.txt
> @@ -0,0 +1,21 @@
> +* MELFAS MIP4 Touchscreen
> +
> +Required properties:
> +- compatible: must be "melfas,mip4_ts"
> +- reg: I2C slave address of the chip (0x48 or 0x34)
> +- interrupt-parent: interrupt controller to which the chip is connected
> +- interrupts: interrupt to which the chip is connected
> +
> +Optional properties:
> +- ce-gpio: GPIO connected to the CE(chip enable) pin of the chip
> +
> +Example:
> + i2c@00000000 {
> + melfas_mip4_ts@48 {
> + compatible = "melfas,mip4_ts";
> + reg = <0x48>;
> + interrupt-parent = <&gpio>;
> + interrupts = <0 IRQ_TYPE_EDGE_FALLING>;
> + ce-gpio = <&gpio 0 GPIO_ACTIVE_HIGH>;
> + };
> + };
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index 99029cf..1457fd4 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -143,6 +143,7 @@ marvell Marvell Technology Group Ltd.
> maxim Maxim Integrated Products
> mediatek MediaTek Inc.
> melexis Melexis N.V.
> +melfas MELFAS Inc.
> merrii Merrii Technology Co., Ltd.
> micrel Micrel Inc.
> microchip Microchip Technology Inc.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 630151f..9627cab 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7155,6 +7155,13 @@ F: Documentation/scsi/megaraid.txt
> F: drivers/scsi/megaraid.*
> F: drivers/scsi/megaraid/
>
> +MELFAS MIP4 TOUCHSCREEN DRIVER
> +M: "Sangwon Jee" <jeesw@melfas.com>
> +W: http://www.melfas.com
> +S: Supported
> +F: drivers/input/touchscreen/melfas_mip4*
> +F: Documentation/devicetree/bindings/input/touchscreen/melfas_mip4*
> +
> MELLANOX ETHERNET DRIVER (mlx4_en)
> M: Eugenia Emantayev <eugenia@mellanox.com>
> L: netdev@vger.kernel.org
> --
> 1.9.1
>
--
Dmitry
prev parent reply other threads:[~2016-10-06 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 5:19 Input: melfas_mip4 - add documentations Sangwon Jee
2016-10-06 5:58 ` Dmitry Torokhov [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=20161006055818.GC36340@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=jeesw@melfas.com \
--cc=linux-input@vger.kernel.org \
/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).