linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Knecht <vincent.knecht@mailoo.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Henrik Rydberg <rydberg@bitmath.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Michael Srba <Michael.Srba@seznam.cz>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v4 2/2] Input: add MStar MSG2638 touchscreen driver
Date: Mon, 22 Feb 2021 21:51:39 +0100	[thread overview]
Message-ID: <a22fda89b5f97418e936655817f45bd55f6248ee.camel@mailoo.org> (raw)
In-Reply-To: <YDGaB6L5+Aa2snUM@google.com>

Le samedi 20 février 2021 à 15:23 -0800, Dmitry Torokhov a écrit :
> Hi Vincent,

Hi Dmitry, thank you for the review !

> On Wed, Feb 10, 2021 at 06:33:52PM +0100, Vincent Knecht wrote:
> > +
> > +       for (i = 0; i < MAX_SUPPORTED_FINGER_NUM; i++) {
> > +               p = &touch_event.pkt[i];
> > +               /* Ignore non-pressed finger data */
> > +               if (p->xy_hi == 0xFF && p->x_low == 0xFF && p->y_low == 0xFF)
> > +                       continue;
> > +
> > +               coord.x = (((p->xy_hi & 0xF0) << 4) | p->x_low) * msg2638->prop.max_x / TPD_WIDTH;
> > +               coord.y = (((p->xy_hi & 0x0F) << 8) | p->y_low) * msg2638->prop.max_y / TPD_HEIGHT;
> > +               msg2638_report_finger(msg2638, i, &coord);
> 
> We do not scale the coordinates in the kernel. Rather we provide
> resolution, if known, and min/max coordinates reported by the hardware,
> and let userspace handle the rest.

Ok, will remove scaling... I was able to test it's ok by setting 
touchscreen-size-{x,y} = <2048>;

> > +static int __maybe_unused msg2638_suspend(struct device *dev)
> > +{
> > +       struct i2c_client *client = to_i2c_client(dev);
> > +       struct msg2638_ts_data *msg2638 = i2c_get_clientdata(client);
> > +
> > +       mutex_lock(&msg2638->input_dev->mutex);
> > +
> > +       if (input_device_enabled(msg2638->input_dev))
> > +               msg2638_stop(msg2638);
> 
> I believe that you should power down the device only if it is not
> configures as wakeup source. In fact (and I think most drivers are
> wrong in this), you may want to power up the device if it is a wakeup
> source and it does not have any users.

I don't know much on this subject ; from downstream code, it seems
the touchscreen supports "wakeup gestures" (like "double click",
up/down/left/right directions and some characters/letters) and apparently
an irq-gpio which would be used to wakeup.
I don't handle that currently, is it required ?






      reply	other threads:[~2021-02-22 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 17:33 [PATCH v4 1/2] dt-bindings: input/touchscreen: add bindings for msg2638 Vincent Knecht
2021-02-10 17:33 ` [PATCH v4 2/2] Input: add MStar MSG2638 touchscreen driver Vincent Knecht
2021-02-20 23:23   ` Dmitry Torokhov
2021-02-22 20:51     ` Vincent Knecht [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=a22fda89b5f97418e936655817f45bd55f6248ee.camel@mailoo.org \
    --to=vincent.knecht@mailoo.org \
    --cc=Michael.Srba@seznam.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rydberg@bitmath.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).