From: Sebastian Reichel <sre@kernel.org>
To: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Cc: nick@shmanahar.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, alexandre.belloni@bootlin.com,
dmitry.torokhov@gmail.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 3/3] Input: atmel_mxt_ts: Document optional voltage regulators
Date: Sun, 16 Dec 2018 23:41:51 +0100 [thread overview]
Message-ID: <20181216224151.h2kmm56a7yxolc2o@earth.universe> (raw)
In-Reply-To: <20181214151214.5391-4-pawel.mikolaj.chmiel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
Hi,
On Fri, Dec 14, 2018 at 04:12:14PM +0100, Paweł Chmiel wrote:
> Document new optional voltage regulators, which can be used
> to power down/up touchscreen.
>
> Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
-- Sebastian
> ---
> Changes from v1:
> - Added reviewed-by
> ---
> .../devicetree/bindings/input/atmel,maxtouch.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/atmel,maxtouch.txt b/Documentation/devicetree/bindings/input/atmel,maxtouch.txt
> index c88919480d37..17930ecadad3 100644
> --- a/Documentation/devicetree/bindings/input/atmel,maxtouch.txt
> +++ b/Documentation/devicetree/bindings/input/atmel,maxtouch.txt
> @@ -31,6 +31,12 @@ Optional properties for main touchpad device:
>
> - reset-gpios: GPIO specifier for the touchscreen's reset pin (active low)
>
> +- avdd-supply: Analog power supply. It powers up the analog channel block
> + of the controller to detect the touches.
> +
> +- vdd-supply: Digital power supply. It powers up the digital block
> + of the controller to enable i2c communication.
> +
> Example:
>
> touch@4b {
> @@ -38,4 +44,6 @@ Example:
> reg = <0x4b>;
> interrupt-parent = <&gpio>;
> interrupts = <TEGRA_GPIO(W, 3) IRQ_TYPE_LEVEL_LOW>;
> + avdd-supply = <&atsp_reg>;
> + vdd-supply = <&tsp_reg>;
> };
> --
> 2.17.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-12-16 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 15:12 [PATCH v5 0/3] Input: atmel_mxt_ts: Add support for optional regulators Paweł Chmiel
2018-12-14 15:12 ` [PATCH v5 1/3] " Paweł Chmiel
2018-12-14 15:12 ` [PATCH v5 2/3] Input: atmel_mxt_ts: Wait for device be ready for communication Paweł Chmiel
2019-01-15 0:42 ` Dmitry Torokhov
2018-12-14 15:12 ` [PATCH v5 3/3] Input: atmel_mxt_ts: Document optional voltage regulators Paweł Chmiel
2018-12-16 22:41 ` Sebastian Reichel [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=20181216224151.h2kmm56a7yxolc2o@earth.universe \
--to=sre@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nick@shmanahar.org \
--cc=pawel.mikolaj.chmiel@gmail.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;
as well as URLs for NNTP newsgroup(s).