From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: dmitry.torokhov@gmail.com,
"Mylène Josserand" <mylene.josserand@free-electrons.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, thomas.petazzoni@free-electrons.com
Subject: Re: [PATCH v4 1/2] Input: Add driver for Cypress Generation 5 touchscreen
Date: Mon, 22 Jan 2018 13:50:49 +0100 [thread overview]
Message-ID: <20180122125049.4bqqqbgdlkdadpjh@flea.lan> (raw)
In-Reply-To: <20171201153957.13053-2-mylene.josserand@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Dmitry,
On Fri, Dec 01, 2017 at 04:39:56PM +0100, Mylène Josserand wrote:
> This is the basic driver for the Cypress TrueTouch Gen5 touchscreen
> controllers. This driver supports only the I2C bus but it uses regmap
> so SPI support could be added later.
> The touchscreen can retrieve some defined zone that are handled as
> buttons (according to the hardware). That is why it handles
> button and multitouch events.
>
> Reviewed-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> Signed-off-by: Mylène Josserand <mylene.josserand@free-electrons.com>
Can we have some review here? This is the fourth iteration, with the
first having been sent back in May, and as far as I know we never got
any review from you. Can we please move forward on this?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-22 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 15:39 [PATCH v4 0/2] Input: Add Cypress Gen5 Touchscreen driver Mylène Josserand
2017-12-01 15:39 ` [PATCH v4 1/2] Input: Add driver for Cypress Generation 5 touchscreen Mylène Josserand
2017-12-03 14:29 ` [PATCH] Input: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-12-03 14:29 ` [PATCH v4 1/2] Input: Add driver for Cypress Generation 5 touchscreen kbuild test robot
2017-12-13 11:37 ` kbuild test robot
2017-12-13 11:37 ` [RFC PATCH] Input: hid_cmd_state can be static kbuild test robot
2018-01-22 12:50 ` Maxime Ripard [this message]
[not found] ` <20171201153957.13053-2-mylene.josserand-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2018-01-22 20:11 ` [PATCH v4 1/2] Input: Add driver for Cypress Generation 5 touchscreen Marcus Folkesson
2018-01-23 9:33 ` Mylene Josserand
2018-01-23 4:15 ` Dmitry Torokhov
2018-01-23 10:44 ` Mylene Josserand
[not found] ` <20180123114459.07cc3404-K8i4uRanGBt8XcdJbWeDu7NAH6kLmebB@public.gmane.org>
2018-01-23 10:50 ` landyn.lawrence-jHc5sQ61u836K7/ahGyk6A
2018-01-23 17:30 ` Dmitry Torokhov
2017-12-01 15:39 ` [PATCH v4 2/2] dt-bindings: input: Add documentation for cyttsp5 Mylène Josserand
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=20180122125049.4bqqqbgdlkdadpjh@flea.lan \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mylene.josserand@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).