From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: webgeek1234@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: edt-ft5x06 - Support label device property for input name
Date: Sun, 12 Apr 2026 20:58:05 -0700 [thread overview]
Message-ID: <adxpdaSXYAa9dLPD@google.com> (raw)
In-Reply-To: <20260409-ft5x06-label-v1-1-21e8a9ae9a60@gmail.com>
Hi Aaron,
On Thu, Apr 09, 2026 at 06:16:08PM -0500, Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
>
> The AYN Thor uses a ft5426 and a ft5452 for each screen respectively and
> these currently get the same input name, making them indistinguishable
> from userspace. Support setting a label in kernel dt to make these
> report uniquely.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> drivers/input/touchscreen/edt-ft5x06.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/edt-ft5x06.c b/drivers/input/touchscreen/edt-ft5x06.c
> index ba8ff65f7ea671..c36497571b1aa1 100644
> --- a/drivers/input/touchscreen/edt-ft5x06.c
> +++ b/drivers/input/touchscreen/edt-ft5x06.c
> @@ -1285,7 +1285,9 @@ static int edt_ft5x06_ts_probe(struct i2c_client *client)
> "Model \"%s\", Rev. \"%s\", %dx%d sensors\n",
> tsdata->name, tsdata->fw_version, tsdata->num_x, tsdata->num_y);
>
> - input->name = tsdata->name;
> + if (device_property_read_string(&client->dev, "label", &input->name))
> + input->name = tsdata->name;
> +
You should be able to differentiate them by their sysfs path.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-04-13 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 23:16 [PATCH] Input: edt-ft5x06 - Support label device property for input name Aaron Kling via B4 Relay
2026-04-13 3:58 ` Dmitry Torokhov [this message]
2026-04-13 4:02 ` Aaron Kling
2026-04-13 4:06 ` Dmitry Torokhov
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=adxpdaSXYAa9dLPD@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=webgeek1234@gmail.com \
/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