From: Marek Vasut <marex@denx.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, ch@denx.de,
Joe Hung <joe_hung@ilitek.com>, Luca Hsu <luca_hsu@ilitek.com>
Subject: Re: [PATCH v2 1/3] Input: ili210x - use resolution from ili251x firmware
Date: Tue, 31 Aug 2021 00:49:49 +0200 [thread overview]
Message-ID: <bfc05564-38dd-d950-ed71-0599c48d57f4@denx.de> (raw)
In-Reply-To: <YS1FsJROzDkm/0Ky@google.com>
On 8/30/21 10:55 PM, Dmitry Torokhov wrote:
[...]
>> + return -EINVAL;
>> +
>> + priv->input->absinfo[ABS_X].maximum = resx - 1;
>> + priv->input->absinfo[ABS_Y].maximum = resy - 1;
>> + priv->input->absinfo[ABS_MT_POSITION_X].maximum = resx - 1;
>> + priv->input->absinfo[ABS_MT_POSITION_Y].maximum = resy - 1;
>
> There is
>
> input_set_abs_max(priv->input, ABS_X, resx - 1);
git grep finds nothing in linux-next / your tree on k.org / patchwork.
Where is that ?
[...]
next prev parent reply other threads:[~2021-08-30 22:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 21:12 [PATCH v2 1/3] Input: ili210x - use resolution from ili251x firmware Marek Vasut
2021-08-27 21:12 ` [PATCH v2 2/3] Input: ili210x - export ili251x version details via sysfs Marek Vasut
2021-08-30 21:01 ` Dmitry Torokhov
2021-08-30 23:02 ` Marek Vasut
2021-08-30 23:20 ` Dmitry Torokhov
2021-08-30 23:33 ` Marek Vasut
2021-08-30 23:45 ` Dmitry Torokhov
2021-08-27 21:12 ` [PATCH v2 3/3] Input: ili210x - add ili251x firmware update support Marek Vasut
2021-08-30 21:14 ` Dmitry Torokhov
2021-08-30 23:27 ` Marek Vasut
2021-08-31 2:05 ` Dmitry Torokhov
2021-08-30 20:55 ` [PATCH v2 1/3] Input: ili210x - use resolution from ili251x firmware Dmitry Torokhov
2021-08-30 22:49 ` Marek Vasut [this message]
2021-08-30 23:21 ` Dmitry Torokhov
2021-08-30 23:31 ` Marek Vasut
2021-08-30 23:46 ` Dmitry Torokhov
2021-08-31 0:01 ` Marek Vasut
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=bfc05564-38dd-d950-ed71-0599c48d57f4@denx.de \
--to=marex@denx.de \
--cc=ch@denx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=joe_hung@ilitek.com \
--cc=linux-input@vger.kernel.org \
--cc=luca_hsu@ilitek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.