From: Rob Herring <robh@kernel.org>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bastien Nocera <hadess@hadess.net>,
Henrik Rydberg <rydberg@bitmath.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
linux-amarula@amarulasolutions.com,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH v5 1/4] dt-bindings: input: touchscreen: goodix: Document regulator properties
Date: Mon, 18 Feb 2019 09:45:40 -0600 [thread overview]
Message-ID: <20190218154540.GC28558@bogus> (raw)
In-Reply-To: <20190217091436.3702-2-jagan@amarulasolutions.com>
On Sun, Feb 17, 2019 at 02:44:33PM +0530, Jagan Teki wrote:
> Goodix CTP controllers support analog, digital and gpio regulator
> supplies on relevant controller pin configurations.
>
> Out of which AVDD28 regulator is mandatory supplied regulator in most
> of the board designs, so document AVDD28 as required property and
> rest marked as optional regulators.
>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> ---
> .../devicetree/bindings/input/touchscreen/goodix.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-02-18 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 9:14 [PATCH v5 0/4] input: touchscreen: Add goodix GT5553 CTP support Jagan Teki
2019-02-17 9:14 ` [PATCH v5 1/4] dt-bindings: input: touchscreen: goodix: Document regulator properties Jagan Teki
2019-02-18 15:45 ` Rob Herring [this message]
2019-02-18 19:04 ` Jagan Teki
2019-02-17 9:14 ` [PATCH v5 2/4] Input: goodix - Add regulators support Jagan Teki
2019-02-17 9:14 ` [PATCH v5 3/4] dt-bindings: input: touchscreen: goodix: Add GT5663 compatible Jagan Teki
2019-02-18 15:45 ` Rob Herring
2019-02-18 15:45 ` Rob Herring
2019-02-17 9:14 ` [PATCH v5 4/4] Input: goodix - Add GT5663 CTP support 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=20190218154540.GC28558@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=jagan@amarulasolutions.com \
--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=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 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.