From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Duson Lin <dusonlin@emc.com.tw>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"bleung@chromium.org" <bleung@chromium.org>,
"agnescheng@chromium.org" <agnescheng@chromium.org>,
"phoenix@emc.com.tw" <phoenix@emc.com.tw>,
"jeff.chuang@emc.com.tw" <jeff.chuang@emc.com.tw>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] Input: add i2c/smbus driver for elan touchpad
Date: Mon, 6 Oct 2014 09:37:03 -0700 [thread overview]
Message-ID: <20141006163703.GB27115@dtor-glaptop> (raw)
In-Reply-To: <20141006092452.GA24686@leverpostej>
On Mon, Oct 06, 2014 at 10:24:52AM +0100, Mark Rutland wrote:
> On Fri, Oct 03, 2014 at 10:06:51PM +0100, Dmitry Torokhov wrote:
> > [adding devicetree folks...]
> >
> > On Fri, Oct 03, 2014 at 02:03:57PM -0700, Dmitry Torokhov wrote:
> > > diff --git a/Documentation/devicetree/bindings/input/elan_i2c.txt b/Documentation/devicetree/bindings/input/elan_i2c.txt
> > > new file mode 100644
> > > index 0000000..0a6ee7d
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/input/elan_i2c.txt
> > > @@ -0,0 +1,34 @@
> > > +Elantech I2C Touchpad
> > > +
> > > +Required properties:
> > > +- compatible: must be "elan,i2c_touchpad".
>
> s/_/-/ in DT strings and property names plase.
>
> The name seems very generic, and you mention the driver supports a
> variety of touchpads. Please choose a specific device name for the
> compatible string. Other devices can have that as a fallback entry in
> addition to a more specific string.
Duson, what would be a good model/device name here?
>
> > > +- reg: I2C address of the chip.
> > > +- interrupt-parent: a phandle for the gpio controller (see interrupt
> > > + binding[0]).
> > > +- interrupts: (gpio) interrupt to which the chip is connected (see interrupt
> > > + binding[0]).
>
> If this is an interrupt from the PoV of this device, it doesn't matter
> if the other end is connected to a hardwired interrupt controller or a
> gpio. So drop the mention of GPIOs frmom the interrupt properties.
>
> > > +
> > > +Optional properties:
> > > +- wakeup-source: touchpad should be configured as a wakeup source.
>
> s/should be configured as/can be used as/
>
> > > +- pinctrl-names: should be "default" (see pinctrl binding [1]).
> > > +- pinctrl-0: a phandle pointing to the pin settings for the device (see
> > > + pinctrl binding [1]).
> > > +- vcc-supply: a phandle for the regulator supplying 3.3V power.
> > > +
> > > +[0]: Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
> > > +[1]: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
> > > +
> > > +Example:
> > > + &i2c1 {
> > > + /* ... */
> > > +
> > > + touchpad@15 {
> > > + compatible = "elan,i2c_touchpad";
> > > + reg = <0x15>;
> > > + interrupt-parent = <&gpio4>;
> > > + interrupts = <0x0 IRQ_TYPE_EDGE_FALLING>;
> > > + wakeup-source;
> > > + };
> > > +
> > > + /* ... */
> > > + };
>
> Otherwise this looks ok.
Thanks Mark.
--
Dmitry
next prev parent reply other threads:[~2014-10-06 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 3:08 [PATCH v2] Input: add i2c/smbus driver for elan touchpad Duson Lin
2014-01-10 20:30 ` Benson Leung
2014-02-07 0:21 ` Benson Leung
2014-02-19 21:48 ` Benson Leung
2014-07-24 18:05 ` Dmitry Torokhov
2014-07-25 18:05 ` cheng wei Lin
2014-07-25 18:20 ` Dmitry Torokhov
2014-07-25 20:06 ` Dmitry Torokhov
2014-07-26 8:12 ` cheng wei Lin
2014-10-03 21:03 ` Dmitry Torokhov
2014-10-03 21:06 ` Dmitry Torokhov
2014-10-06 9:24 ` Mark Rutland
2014-10-06 16:37 ` Dmitry Torokhov [this message]
2014-10-03 21:30 ` Benson Leung
-- strict thread matches above, loose matches on Subject: below --
2013-12-18 3:46 Duson Lin
2014-02-07 0:10 ` Benson Leung
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=20141006163703.GB27115@dtor-glaptop \
--to=dmitry.torokhov@gmail.com \
--cc=agnescheng@chromium.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dusonlin@emc.com.tw \
--cc=jeff.chuang@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=phoenix@emc.com.tw \
/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