All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: dmitry.torokhov@gmail.com, robh+dt@kernel.org,
	mark.rutland@arm.com, devicetree@vger.kernel.org,
	kernel@pengutronix.de, linux-input@vger.kernel.org,
	hdegoede@redhat.com, simon.budig@kernelconcepts.de
Subject: Re: [PATCH 1/5] dt-bindings: Input: edt-ft5x06 - add support for FT5726
Date: Fri, 11 Jan 2019 11:02:37 -0600	[thread overview]
Message-ID: <20190111170237.GA5628@bogus> (raw)
In-Reply-To: <20190103192327.6170-2-m.felsch@pengutronix.de>

On Thu,  3 Jan 2019 20:23:23 +0100, Marco Felsch wrote:
> The FT5726 controller has up to 72 channels, 42 Tx-channels and 30
> Rx-channels. The recommended touchpoint size is less equal 11.6".
> 
> This adds the support for the FT5726 controller flashed with the
> Evervision firmware.
> 
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
>  .../devicetree/bindings/input/touchscreen/edt-ft5x06.txt      | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2019-01-11 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 19:23 [PATCH 0/5] Input: edt-ft5x06 - Add support for Evervision FT devices Marco Felsch
2019-01-03 19:23 ` [PATCH 1/5] dt-bindings: Input: edt-ft5x06 - add support for FT5726 Marco Felsch
2019-01-11 17:02   ` Rob Herring [this message]
2019-01-03 19:23 ` [PATCH 2/5] Input: edt-ft5x06 - add support for Evervision FT5726 Marco Felsch
2019-01-03 19:23 ` [PATCH 3/5] Input: edt-ft5x06 - Add support to update ev-ft5726 registers Marco Felsch
2019-01-03 19:23 ` [PATCH 4/5] dt-bindings: Input: edt-ft5x06 - add offset bindings for ft5726 Marco Felsch
2019-01-11 17:04   ` Rob Herring
2019-01-03 19:23 ` [PATCH 5/5] Input: edt-ft5x06 - add offset support for ev-ft5726 Marco Felsch
2019-01-14  7:42 ` [PATCH 0/5] Input: edt-ft5x06 - Add support for Evervision FT devices Dmitry Torokhov

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=20190111170237.GA5628@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-input@vger.kernel.org \
    --cc=m.felsch@pengutronix.de \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=simon.budig@kernelconcepts.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.