linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Henrik Rydberg" <rydberg@euromail.se>
Cc: linux-input@vger.kernel.org, Markus Pargmann <mpa@pengutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] input: ft5x06: Fix userspace reported maximum value
Date: Mon, 23 Mar 2015 17:10:02 -0700	[thread overview]
Message-ID: <20150324001002.GJ15676@lukather> (raw)
In-Reply-To: <1425390646-31196-1-git-send-email-maxime.ripard@free-electrons.com>

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

Hi Lothar, Dmitry,

On Tue, Mar 03, 2015 at 02:50:42PM +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.

Do you have any comments on that?

Thanks,
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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

  parent reply	other threads:[~2015-03-24  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 13:50 [PATCH v3 0/4] input: ft5x06: Fix userspace reported maximum value Maxime Ripard
2015-03-03 13:50 ` [PATCH v3 1/4] input: touchscreen: of: Use input_set_abs_params Maxime Ripard
2015-03-03 13:50 ` [PATCH v3 2/4] input: touchscreen: of: Register multitouch axes Maxime Ripard
2015-03-03 13:50 ` [PATCH v3 3/4] input: ft5x06: Allow to set the maximum axes value through the DT Maxime Ripard
2015-03-03 13:50 ` [PATCH v3 4/4] input: edt-ft5x06: Remove EV_SYN event report Maxime Ripard
2015-03-12 14:30 ` [PATCH v3 0/4] input: ft5x06: Fix userspace reported maximum value Markus Pargmann
2015-03-24  0:10 ` Maxime Ripard [this message]
2015-03-24 16:47   ` Dmitry Torokhov
2015-03-24 18:45     ` Maxime Ripard
2015-03-24 18:56       ` Dmitry Torokhov
2015-03-24 19:05         ` Maxime Ripard

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=20150324001002.GJ15676@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=LW@KARO-electronics.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpa@pengutronix.de \
    --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).