From: Bastien Nocera <hadess@hadess.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Input: goodix - Fix touch coords on WinBook TW100 and TW700
Date: Fri, 24 Jul 2015 13:13:24 +0200 [thread overview]
Message-ID: <1437736404.2863.27.camel@hadess.net> (raw)
In-Reply-To: <20150723215637.GF12733@dtor-ws>
On Thu, 2015-07-23 at 14:56 -0700, Dmitry Torokhov wrote:
> Hi Bastien,
>
> On Thu, Jul 23, 2015 at 04:13:28PM +0200, Bastien Nocera wrote:
> > The touchscreen on the WinBook TW100 and TW700 don't match the
> > default
> > display, with 0,0 touches being reported when touching at the
> > bottom
> > right of the screen.
> >
> > 1280,800 0,800
> > +-------------+
> > | |
> > | |
> > | |
> > +-------------+
> > 1280,0 0,0
> >
> > It's unfortunately impossible to detect this problem with data from
> > the
> > DSDT, or other auxiliary metadata, so fallback to quirking this
> > specific
> > model of tablet instead.
> >
> > Signed-off-by: Bastien Nocera <hadess@hadess.net>
> > Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > ---
> > drivers/input/touchscreen/goodix.c | 31
> > +++++++++++++++++++++++++++++++
> > 1 file changed, 31 insertions(+)
> >
> > diff --git a/drivers/input/touchscreen/goodix.c
> > b/drivers/input/touchscreen/goodix.c
> > index b4d12e2..3722806 100644
> > --- a/drivers/input/touchscreen/goodix.c
> > +++ b/drivers/input/touchscreen/goodix.c
> > @@ -15,6 +15,7 @@
> > */
> >
> > #include <linux/kernel.h>
> > +#include <linux/dmi.h>
> > #include <linux/i2c.h>
> > #include <linux/input.h>
> > #include <linux/input/mt.h>
> > @@ -34,6 +35,7 @@ struct goodix_ts_data {
> > int abs_y_max;
> > unsigned int max_touch_num;
> > unsigned int int_trigger_type;
> > + bool rotated_screen;
> > };
> >
> > #define GOODIX_MAX_HEIGHT 4096
> > @@ -60,6 +62,24 @@ static const unsigned long goodix_irq_flags[] =
> > {
> > IRQ_TYPE_LEVEL_HIGH,
> > };
> >
> > +/* Those tablets have their coords origin at the bottom right
> > + * of the tablet, as if rotated 180 degrees */
>
> /*
> * Multi
> * line
> * comment
> */
>
> please.
Would be good if checkpatch could check for that, or is it a personal
request?
> > +static const struct dmi_system_id rotated_screen[] = {
>
> #if defined(CONFIG_DMI) && defined(CONFIG_X86)
Sure.
> > + {
> > + .ident = "WinBook TW100",
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "WinBook"),
> > + DMI_MATCH(DMI_PRODUCT_NAME, "TW100")
> > + },
> > + .ident = "WinBook TW700",
> > + .matches = {
> > + DMI_MATCH(DMI_SYS_VENDOR, "WinBook"),
> > + DMI_MATCH(DMI_PRODUCT_NAME, "TW100")
> > + },
>
> This does not do what you want it to do... First of all you probably
> wanted TW700 on the second entry, second you need separate them into
> 2
> entries into array (right now it is one still).
Duh!
Thanks, coming in v3 shortly.
next prev parent reply other threads:[~2015-07-24 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 14:13 [PATCH v2] Input: goodix - Fix touch coords on WinBook TW100 and TW700 Bastien Nocera
2015-07-23 21:56 ` Dmitry Torokhov
2015-07-24 11:13 ` Bastien Nocera [this message]
2015-07-24 16:08 ` Dmitry Torokhov
2015-07-24 16:09 ` Bastien Nocera
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=1437736404.2863.27.camel@hadess.net \
--to=hadess@hadess.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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