From: Rob Herring <robh@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
patchwork-lst@pengutronix.de, kernel@pengutronix.de,
Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH 3/4] Input: egalax_ts - add property for protocol version
Date: Mon, 24 Sep 2018 15:28:56 -0700 [thread overview]
Message-ID: <20180924222844.GA10118@bogus> (raw)
In-Reply-To: <20180920142256.2788-3-l.stach@pengutronix.de>
On Thu, Sep 20, 2018 at 04:22:55PM +0200, Lucas Stach wrote:
> EETI changed the i2c protocol in an incompatible way at some point. The
> documentation doesn't state if there is a way to autodetect the used
> protocol. Thus we introduce a DT property to let the driver know about
> the protocol version used by the touch controller.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> .../devicetree/bindings/input/touchscreen/egalax-ts.txt | 8 ++++++++
> drivers/input/touchscreen/egalax_ts.c | 4 ++++
> 2 files changed, 12 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt b/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt
> index 92fb2620f5e2..41be6287589d 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt
> +++ b/Documentation/devicetree/bindings/input/touchscreen/egalax-ts.txt
> @@ -7,6 +7,13 @@ Required properties:
> - wakeup-gpios: the gpio pin to be used for waking up the controller
> and also used as irq pin
>
> +Optional properties:
> +- eeti,protocol-version: protocol version used by the controller
> + 0: This is the default protocol used when the property is absent. This
> + protocol supports up to 5 touch points with 1 points per report.
> + 1: Protocol supports up to 10 touch points with a maximum of 5 points
> + per report.
This should be part of the compatible property. If we're not doing
compatibles for each version of the chip, then we should at least do it
for the protocol.
Rob
next prev parent reply other threads:[~2018-09-24 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 14:22 [PATCH 1/4] Input: egalax_ts - clean up capability initialization Lucas Stach
2018-09-20 14:22 ` [PATCH 2/4] Input: egalax_ts - use touchscreen helpers Lucas Stach
2018-09-20 14:22 ` [PATCH 3/4] Input: egalax_ts - add property for protocol version Lucas Stach
2018-09-24 22:28 ` Rob Herring [this message]
2018-09-20 14:22 ` [PATCH 4/4] Input: egalax_ts - add support for new " Lucas Stach
2018-11-05 17:19 ` [PATCH 1/4] Input: egalax_ts - clean up capability initialization Lucas Stach
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=20180924222844.GA10118@bogus \
--to=robh@kernel.org \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-input@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
/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).