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: <20250723155728.GA61254@francesco-nb>
Date: Wed, 23 Jul 2025 17:57:28 +0200
From: Francesco Dolcini <francesco@...cini.it>
To: Joe Hung (洪銘陽) <joe_hung@...tek.com>
Cc: "dmitry.torokhov@...il.com" <dmitry.torokhov@...il.com>,
	"francesco.dolcini@...adex.com" <francesco.dolcini@...adex.com>,
	"emanuele.ghidoli@...adex.com" <emanuele.ghidoli@...adex.com>,
	linux-input <linux-input@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Luca Hsu (徐嘉鍊) <luca_hsu@...tek.com>
Subject: Re: [PATCH] input: ilitek_ts_i2c: report key event for palm

On Mon, Jul 14, 2025 at 09:51:42AM +0000, Joe Hung (洪銘陽) wrote:
> From ec0d80214fee6acc0b38f33ad0b6b487098963bc Mon Sep 17 00:00:00 2001
> From: Joe Hong <joe_hung@...tek.com>
> Date: Mon, 14 Jul 2025 17:20:11 +0800
> Subject: [PATCH] input: ilitek_ts_i2c: report key event for palm

something wrong on this headers, check your setup

> Add support for reporting user-defined key event while getting palm event.
> 
> Signed-off-by: Joe Hong <joe_hung@...tek.com>
> ---
>  drivers/input/touchscreen/ilitek_ts_i2c.c | 42 +++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
> 
> diff --git a/drivers/input/touchscreen/ilitek_ts_i2c.c b/drivers/input/touchscreen/ilitek_ts_i2c.c
> index 0dd632724a00..fdcb4ab66fbb 100644
> --- a/drivers/input/touchscreen/ilitek_ts_i2c.c
> +++ b/drivers/input/touchscreen/ilitek_ts_i2c.c
> @@ -39,8 +39,13 @@
>  #define ILITEK_TP_I2C_REPORT_ID				0x48
>  
>  #define REPORT_COUNT_ADDRESS				61
> +#define ALGO_MODE_ADDRESS				62
>  #define ILITEK_SUPPORT_MAX_POINT			40
>  
> +static uint palm_key;
> +module_param(palm_key, uint, 0664);
> +MODULE_PARM_DESC(palm_key, "Set palm key code when palm is detected");

I do not think that putting some kind of configuration in a kernel
module param is an option

Francesco


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ