From: Rob Herring <robh@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Jiada Wang <jiada_wang@mentor.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-tegra@vger.kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Nick Dyer <nick@shmanahar.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: input: atmel_mxt_ts: Document atmel,wakeup-method and WAKE line GPIO
Date: Fri, 5 Feb 2021 17:16:34 -0600 [thread overview]
Message-ID: <20210205231634.GA3944013@robh.at.kernel.org> (raw)
In-Reply-To: <20210122200659.7404-2-digetx@gmail.com>
On Fri, 22 Jan 2021 23:06:57 +0300, Dmitry Osipenko wrote:
> Some Atmel touchscreen controllers have a WAKE line that needs to be
> asserted low in order to wake up controller from a deep sleep. Document
> the wakeup methods and the new GPIO properties.
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> .../bindings/input/atmel,maxtouch.yaml | 29 +++++++++++++++++++
> include/dt-bindings/input/atmel-maxtouch.h | 10 +++++++
> 2 files changed, 39 insertions(+)
> create mode 100644 include/dt-bindings/input/atmel-maxtouch.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-02-06 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 20:06 [PATCH v4 0/3] Support wakeup methods of Atmel maXTouch controllers Dmitry Osipenko
2021-01-22 20:06 ` [PATCH v4 1/3] dt-bindings: input: atmel_mxt_ts: Document atmel,wakeup-method and WAKE line GPIO Dmitry Osipenko
2021-02-05 23:16 ` Rob Herring [this message]
2021-01-22 20:06 ` [PATCH v4 2/3] Input: atmel_mxt_ts - support wakeup methods Dmitry Osipenko
2021-01-23 22:59 ` Linus Walleij
2021-01-22 20:06 ` [PATCH v4 3/3] ARM: tegra: acer-a500: Add atmel,wakeup-method property Dmitry Osipenko
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=20210205231634.GA3944013@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jiada_wang@mentor.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nick@shmanahar.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.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 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.