[PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm

David Heidelberg via B4 Relay posted 2 patches 2 months ago
drivers/input/rmi4/rmi_f12.c | 33 +++++++++++++++++++++++++++++----
1 file changed, 29 insertions(+), 4 deletions(-)
[PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm
Posted by David Heidelberg via B4 Relay 2 months ago
This series ensures, that when invalid value is detected or mismatch
between value defined in the device-tree and the read from the
touchscreen is observed, the user is notified and zero is ignored.

Signed-off-by: David Heidelberg <david@ixit.cz>
---
David Heidelberg (2):
      Input: rmi4 - report difference between platform data and detected coord in F12
      Input: rmi4 - fallback to platform data for x/y-mm in F12

 drivers/input/rmi4/rmi_f12.c | 33 +++++++++++++++++++++++++++++----
 1 file changed, 29 insertions(+), 4 deletions(-)
---
base-commit: 95d6a9ccef99117115e41e9adb271243bd5e985b
change-id: 20260731-respect-x-y-mm-f74a2970e9b7

Best regards,
--  
David Heidelberg <david@ixit.cz>
Re: [PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm
Posted by Dmitry Torokhov 1 month, 4 weeks ago
Hi David,

On Fri, Jul 31, 2026 at 08:13:40PM +0200, David Heidelberg via B4 Relay wrote:
> This series ensures, that when invalid value is detected or mismatch
> between value defined in the device-tree and the read from the
> touchscreen is observed, the user is notified and zero is ignored.

This seems very complicated. If board maker specifies these parameters,
they probably want to use them instead of what the firmware reports. So
wouldn't it be simpler to not try to match and report differences but
rather skip querying hardware and use device properties if they are
specified?

Thanks.

-- 
Dmitry
Re: [PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm
Posted by David Heidelberg 1 month, 3 weeks ago
On 05/08/2026 07:21, Dmitry Torokhov wrote:
> Hi David,
> 
> On Fri, Jul 31, 2026 at 08:13:40PM +0200, David Heidelberg via B4 Relay wrote:
>> This series ensures, that when invalid value is detected or mismatch
>> between value defined in the device-tree and the read from the
>> touchscreen is observed, the user is notified and zero is ignored.
> 
> This seems very complicated. If board maker specifies these parameters,
> they probably want to use them instead of what the firmware reports. So
> wouldn't it be simpler to not try to match and report differences but
> rather skip querying hardware and use device properties if they are
> specified?

Hi Dmitry.

Agree, I'll send next version just overriding the HW reported values.

David

> 
> Thanks.
> 

-- 
David Heidelberg