linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Pargmann <mpa@pengutronix.de>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: "Lothar Waßmann" <LW@KARO-electronics.de>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Henrik Rydberg" <rydberg@euromail.se>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] input: ft5x06: Fix userspace reported maximum value
Date: Thu, 26 Feb 2015 16:26:17 +0100	[thread overview]
Message-ID: <20150226152617.GC10070@pengutronix.de> (raw)
In-Reply-To: <20150224165508.GY25269@lukather>

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

Hi Maxime,

On Tue, Feb 24, 2015 at 05:55:08PM +0100, Maxime Ripard wrote:
> Hi Markus,
> 
> On Mon, Feb 23, 2015 at 10:49:36PM +0100, Markus Pargmann wrote:
> > Hi,
> > 
> > On Thu, Nov 13, 2014 at 03:06:54PM +0100, Maxime Ripard wrote:
> > > Hi,
> > > 
> > > The current ft5x06 reports to the user-space that its maximum
> > > coordinates are, on both X and Y, way higher than what could be
> > > actually usable on the screen (in my case, 5759x1151 instead of
> > > 480x800).
> > > 
> > > This causes trouble on some userspace stacks that then try to re-scale
> > > these coordinates back to the framebuffer resolution, like QT does.
> > > 
> > > Use the of_touchscreen code to find the real touchscreen limits in the
> > > DT case, and report that to the userspace.
> > > 
> > > Thanks,
> > > Maxime
> > 
> > any news on this?
> 
> Unfortunately, no.
> 
> I never got any review on this, and somehow forgot about it.
> 
> I will rebase the patches on 4.0, and resend them.

That's great, thanks. I will have some hardware next week to test it.

Best Regards,

Markus

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-02-26 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 14:06 [PATCH v2 0/4] input: ft5x06: Fix userspace reported maximum value Maxime Ripard
2014-11-13 14:06 ` [PATCH v2 1/4] input: touchscreen: of: Use input_set_abs_params Maxime Ripard
2014-11-13 14:06 ` [PATCH v2 2/4] input: touchscreen: of: Register multitouch axes Maxime Ripard
2014-11-13 14:06 ` [PATCH v2 3/4] input: ft5x06: Allow to set the maximum axes value through the DT Maxime Ripard
2014-11-13 14:06 ` [PATCH v2 4/4] input: edt-ft5x06: Remove EV_SYN event report Maxime Ripard
2015-02-23 21:49 ` [PATCH v2 0/4] input: ft5x06: Fix userspace reported maximum value Markus Pargmann
2015-02-24 16:55   ` Maxime Ripard
2015-02-26 15:26     ` Markus Pargmann [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=20150226152617.GC10070@pengutronix.de \
    --to=mpa@pengutronix.de \
    --cc=LW@KARO-electronics.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=rydberg@euromail.se \
    /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).