From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] Input: exc3000 - add EXC81W32 support
Date: Thu, 27 Jun 2024 09:51:09 -0700 [thread overview]
Message-ID: <Zn2Yfeaewi-Bxx83@google.com> (raw)
In-Reply-To: <20240626-input-exc3000-exc81w32-v1-1-ac42d3b87aff@pengutronix.de>
Hi Philipp,
On Wed, Jun 26, 2024 at 04:26:48PM +0200, Philipp Zabel wrote:
> This adds support for EXC81W32 controllers.
>
> Tested with firmware reported as type "PCAP81X32 Series",
> model "Orion_0183_1019", fw_version "8001280G".
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> .../devicetree/bindings/input/touchscreen/eeti,exc3000.yaml | 1 +
> drivers/input/touchscreen/exc3000.c | 7 +++++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/eeti,exc3000.yaml b/Documentation/devicetree/bindings/input/touchscreen/eeti,exc3000.yaml
> index 9dc25d30a0a8..c299838e2680 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/eeti,exc3000.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/eeti,exc3000.yaml
> @@ -18,6 +18,7 @@ properties:
> - eeti,exc3000
> - eeti,exc80h60
> - eeti,exc80h84
> + - eeti,exc81w32
> reg:
> const: 0x2a
> interrupts:
Could you please split this chunk into a separate patch so that DT folks
can chime in on it separately from the driver change?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-06-27 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 14:26 [PATCH] Input: exc3000 - add EXC81W32 support Philipp Zabel
2024-06-27 16:51 ` Dmitry Torokhov [this message]
2024-06-28 8:35 ` Philipp Zabel
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=Zn2Yfeaewi-Bxx83@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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).