From: Bastien Nocera <hadess@hadess.net>
To: Irina Tirdea <irina.tirdea@intel.com>, linux-input@vger.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Aleksei Mamlin <mamlinav@gmail.com>,
Karsten Merker <merker@debian.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Octavian Purdila <octavian.purdila@intel.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v12 0/5] Goodix touchscreen enhancements
Date: Thu, 27 Oct 2016 15:44:07 +0200 [thread overview]
Message-ID: <1477575847.2458.18.camel@hadess.net> (raw)
In-Reply-To: <1473530257-7495-1-git-send-email-irina.tirdea@intel.com>
On Sat, 2016-09-10 at 20:57 +0300, Irina Tirdea wrote:
> This is an update for a previous set of patches [1] with enhancements
> for the Goodix touchscreens. The first 3 patches are leftovers from
> the previous patchset (with minor changes due to rebase), while the
> last 2 patches are new.
>
> Thanks,
> Irina
>
> [1] https://lkml.org/lkml/2015/11/19/241
>
> Changes in v12:
> - add documentation for configuration firmware update
> - minor changes due to rebase
> - add 2 new patches to fix reset sequence and add support for gt9157
>
> Previous changes:
> https://lkml.org/lkml/2015/11/19/241
>
> Irina Tirdea (5):
> Input: goodix - add sysfs interface to dump config
> Input: goodix - add support for ESD
> Input: goodix - add runtime power management support
I tested those 3 patches in their v11, but my test tablet's software is
currently broken. Until I find the time to regenerate install images,
I'll just do code reviews.
I assume the first 3 patches don't break anything on the device I
tested this on, but I'd like to make sure it was at least tested on
ACPI-based systems.
Can you mention somewhere on which devices those patches were tested?
Cheers
> Input: goodix - fix reset sequence
> Input: goodix - add support for gt9157
>
> .../bindings/input/touchscreen/goodix.txt | 5 +
> Documentation/input/goodix.txt | 84 +++++
> drivers/input/touchscreen/goodix.c | 346
> +++++++++++++++++++--
> 3 files changed, 415 insertions(+), 20 deletions(-)
> create mode 100644 Documentation/input/goodix.txt
>
prev parent reply other threads:[~2016-10-27 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 17:57 [PATCH v12 0/5] Goodix touchscreen enhancements Irina Tirdea
2016-09-10 17:57 ` [PATCH v12 1/5] Input: goodix - add sysfs interface to dump config Irina Tirdea
2016-10-27 13:44 ` Bastien Nocera
2016-09-10 17:57 ` [PATCH v12 2/5] Input: goodix - add support for ESD Irina Tirdea
2016-10-27 13:44 ` Bastien Nocera
2016-09-10 17:57 ` [PATCH v12 3/5] Input: goodix - add runtime power management support Irina Tirdea
2016-10-27 13:44 ` Bastien Nocera
2016-09-10 17:57 ` [PATCH v12 4/5] Input: goodix - fix reset sequence Irina Tirdea
2016-10-27 13:44 ` Bastien Nocera
2016-09-10 17:57 ` [PATCH v12 5/5] Input: goodix - add support for gt9157 Irina Tirdea
2016-09-19 21:41 ` Rob Herring
2016-10-27 13:44 ` Bastien Nocera
2016-10-27 13:44 ` Bastien Nocera [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=1477575847.2458.18.camel@hadess.net \
--to=hadess@hadess.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=irina.tirdea@intel.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamlinav@gmail.com \
--cc=mark.rutland@arm.com \
--cc=merker@debian.org \
--cc=octavian.purdila@intel.com \
--cc=robh+dt@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