linux-kernel - Re: [PATCH] Input: exc3000

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 27 Jun 2024 09:51:09 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Philipp Zabel <p.zabel@...gutronix.de>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, linux-input@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	kernel@...gutronix.de
Subject: Re: [PATCH] Input: exc3000 - add EXC81W32 support

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@...gutronix.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