From: Jagan Teki <jagan@amarulasolutions.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bastien Nocera <hadess@hadess.net>,
Rob Herring <robh+dt@kernel.org>
Cc: Henrik Rydberg <rydberg@bitmath.org>,
linux-input@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-amarula@amarulasolutions.com,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH v6 0/4] input: touchscreen: Add goodix GT5553 CTP support
Date: Tue, 26 Feb 2019 11:43:54 +0530 [thread overview]
Message-ID: <CAMty3ZDpy5YX3V+6e=UtY=a9Lgiw-NEP1JPQn4_LKL3mYFtrvQ@mail.gmail.com> (raw)
In-Reply-To: <20190219101629.15977-1-jagan@amarulasolutions.com>
Hi Dmitry,
On Tue, Feb 19, 2019 at 3:46 PM Jagan Teki <jagan@amarulasolutions.com> wrote:
>
> This is v6 patchset for supporting goodix GT5553 CTP. Here is the
> previous version[1]
>
> Changes for v5:
> - document bindings for required regulators, which are need during
> power-on sequence
> - enable, disable required regulators as described in power-on sequence
> using normal regulator calls
> - update the proper commi messages
> Changes for v4:
> - document AVDD22, DVDD12, VDDIO as optional properties
> - use regulator bulk calls, for get, enable and disable functionalities
> Changes for v4:
> - devm_add_action_or_reset for disabling regulator
> Changes for v3:
> - add cover-letter
> - s/ADVV28/AVDD28 on commit head
> - fix few typo
> Changes for v2:
> - Rename vcc-supply with AVDD28-supply
> - disable regulator in remove
> - fix to setup regulator in probe code
> - add chipdata
> - drop example node in dt-bindings
>
> [1] https://patchwork.kernel.org/cover/10816901/
>
> Jagan Teki (4):
> dt-bindings: input: touchscreen: goodix: Document regulator properties
> Input: goodix - Add regulators suppot
> dt-bindings: input: touchscreen: goodix: Add GT5663 compatible
> Input: goodix - Add GT5663 CTP support
>
> .../bindings/input/touchscreen/goodix.txt | 3 +
> drivers/input/touchscreen/goodix.c | 60 +++++++++++++++++++
> 2 files changed, 63 insertions(+)
Let me know if you have any further comments on regulator patch, fyi
Rob reviewed it already.
next prev parent reply other threads:[~2019-02-26 6:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 10:16 [PATCH v6 0/4] input: touchscreen: Add goodix GT5553 CTP support Jagan Teki
2019-02-19 10:16 ` [PATCH v6 1/4] dt-bindings: input: touchscreen: goodix: Document regulator properties Jagan Teki
2019-02-22 16:43 ` Rob Herring
2019-02-19 10:16 ` [PATCH v6 2/4] Input: goodix - Add regulators suppot Jagan Teki
2019-02-19 10:16 ` [PATCH v6 3/4] dt-bindings: input: touchscreen: goodix: Add GT5663 compatible Jagan Teki
2019-02-19 10:16 ` [PATCH v6 4/4] Input: goodix - Add GT5663 CTP support Jagan Teki
2019-02-26 6:13 ` Jagan Teki [this message]
2019-03-06 17:17 ` [PATCH v6 0/4] input: touchscreen: Add goodix GT5553 " Jagan Teki
2019-03-11 13:38 ` Jagan Teki
2019-03-17 18:32 ` Jagan Teki
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='CAMty3ZDpy5YX3V+6e=UtY=a9Lgiw-NEP1JPQn4_LKL3mYFtrvQ@mail.gmail.com' \
--to=jagan@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=rydberg@bitmath.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;
as well as URLs for NNTP newsgroup(s).