From: David Heidelberg <david@ixit.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm
Date: Thu, 6 Aug 2026 19:06:36 +0200 [thread overview]
Message-ID: <2dcce6ca-fd78-4438-966b-deedea6cda25@ixit.cz> (raw)
In-Reply-To: <anLH8cYpnvN_DYZu@google.com>
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
prev parent reply other threads:[~2026-08-06 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 18:13 [PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm David Heidelberg via B4 Relay
2026-07-31 18:13 ` [PATCH 1/2] Input: rmi4 - report difference between platform data and detected coord in F12 David Heidelberg via B4 Relay
2026-07-31 18:25 ` sashiko-bot
2026-07-31 18:13 ` [PATCH 2/2] Input: rmi4 - fallback to platform data for x/y-mm " David Heidelberg via B4 Relay
2026-07-31 18:23 ` sashiko-bot
2026-08-05 5:21 ` [PATCH 0/2] Input: rmi4 - honor touchscreen-{x,y}-mm Dmitry Torokhov
2026-08-06 17:06 ` David Heidelberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2dcce6ca-fd78-4438-966b-deedea6cda25@ixit.cz \
--to=david@ixit.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox