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] [day] [month] [year] [list]
Message-ID: <20251117-beautiful-pink-macaque-9fd441@kuoka>
Date: Mon, 17 Nov 2025 07:30:23 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: daniel_peng@...atron.corp-partner.google.com
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>, 
	linux-input@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Rob Herring <robh@...nel.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: input: i2c-hid: Introduce FocalTech
 FT8112

On Mon, Nov 17, 2025 at 11:02:10AM +0800, daniel_peng@...atron.corp-partner.google.com wrote:
> From: Daniel Peng <Daniel_Peng@...atron.corp-partner.google.com>
> 
> Create new binding file for the FocalTech FT8112 due to new touchscreen chip.
> Confirm its compatible, reg for the device via vendor, and set the interrupt
> and reset gpio to map for Skywalker platform.
> FocalTech FT8112 also uses vcc33/vccio power supply.
> 
> Signed-off-by: Daniel Peng <Daniel_Peng@...atron.corp-partner.google.com>
> > > From: Daniel Peng <Daniel_Peng@...atron.corp-partner.google.com>
> > >
> > > The FocalTech FT8112 touch screen chip same as Ilitek ili2901 controller
> >
> > So keep the device in that binding under enum. No need to create
> > document for every device, even if they were different but here it is
> > pretty obvious - same chip.
> >
> > Best regards,
> > Krzysztof
> 
> Re-describe the commit message to make more clear why to create new document
> for FocalTech FT8112 device.
> Sorry for the confusion.

No clue what's this, but try yourself - apply the patch and check the
results if it looks correct.

There are extensive guides how to send patches to Linux kernel,
including comprehensive guide on Linaro blog.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ