linux-kernel - Re: [PATCH v6 2/2] HID: i2c-hid: Add FocalTech FT8112

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]

Message-ID: <eb47h436johngo3bz5b5cn6tyvwqoplg55uhk2siftxk6n547n@4rgwokhtrcec>
Date: Tue, 20 Jan 2026 21:39:41 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: daniel_peng@...atron.corp-partner.google.com, 
	Benjamin Tissoires <bentiss@...nel.org>, Jiri Kosina <jikos@...nel.org>
Cc: linux-input@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, 
	Douglas Anderson <dianders@...omium.org>, Pin-yen Lin <treapking@...omium.org>
Subject: Re: [PATCH v6 2/2] HID: i2c-hid: Add FocalTech FT8112

On Mon, Nov 17, 2025 at 05:40:41PM +0800, daniel_peng@...atron.corp-partner.google.com wrote:
> From: Daniel Peng <Daniel_Peng@...atron.corp-partner.google.com>
> 
> Information for touchscreen model HKO/RB116AS01-2 as below:
> - HID :FTSC1000
> - slave address:0X38
> - Interface:HID over I2C
> - Touch control lC:FT8112
> - I2C ID: PNP0C50
> 
> Signed-off-by: Daniel Peng <Daniel_Peng@...atron.corp-partner.google.com>

Jiri, Benjamin, do you want to take it (and the binding) through the HID
tree or should I take it through input?

> ---
> 
> Changes in v6:
> - No changed with the v5 due to relation chain.
> 
>  drivers/hid/i2c-hid/i2c-hid-of-elan.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/hid/i2c-hid/i2c-hid-of-elan.c b/drivers/hid/i2c-hid/i2c-hid-of-elan.c
> index 0215f217f6d8..b81fcc6ff49e 100644
> --- a/drivers/hid/i2c-hid/i2c-hid-of-elan.c
> +++ b/drivers/hid/i2c-hid/i2c-hid-of-elan.c
> @@ -168,6 +168,13 @@ static const struct elan_i2c_hid_chip_data elan_ekth6a12nay_chip_data = {
>  	.power_after_backlight = true,
>  };
>  
> +static const struct elan_i2c_hid_chip_data focaltech_ft8112_chip_data = {
> +	.post_power_delay_ms = 10,
> +	.post_gpio_reset_on_delay_ms = 150,
> +	.hid_descriptor_address = 0x0001,
> +	.main_supply_name = "vcc33",
> +};
> +
>  static const struct elan_i2c_hid_chip_data ilitek_ili9882t_chip_data = {
>  	.post_power_delay_ms = 1,
>  	.post_gpio_reset_on_delay_ms = 200,
> @@ -191,6 +198,7 @@ static const struct elan_i2c_hid_chip_data ilitek_ili2901_chip_data = {
>  static const struct of_device_id elan_i2c_hid_of_match[] = {
>  	{ .compatible = "elan,ekth6915", .data = &elan_ekth6915_chip_data },
>  	{ .compatible = "elan,ekth6a12nay", .data = &elan_ekth6a12nay_chip_data },
> +	{ .compatible = "focaltech,ft8112", .data = &focaltech_ft8112_chip_data },
>  	{ .compatible = "ilitek,ili9882t", .data = &ilitek_ili9882t_chip_data },
>  	{ .compatible = "ilitek,ili2901", .data = &ilitek_ili2901_chip_data },
>  	{ }

Thanks.

-- 
Dmitry