From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marek Vasut <marex@denx.de>
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: Mon, 30 Aug 2021 16:21:53 -0700 [thread overview]
Message-ID: <YS1oEX75iIjQLn9r@google.com> (raw)
In-Reply-To: <bfc05564-38dd-d950-ed71-0599c48d57f4@denx.de>
On Tue, Aug 31, 2021 at 12:49:49AM +0200, Marek Vasut wrote:
> 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 ?
Look for INPUT_GENERATE_ABS_ACCESSORS in include/linux/input.h
Thanks.
--
Dmitry
next prev parent reply other threads:[~2021-08-30 23:21 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
2021-08-30 23:21 ` Dmitry Torokhov [this message]
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=YS1oEX75iIjQLn9r@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=ch@denx.de \
--cc=joe_hung@ilitek.com \
--cc=linux-input@vger.kernel.org \
--cc=luca_hsu@ilitek.com \
--cc=marex@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).