From: Bastien Nocera <hadess@hadess.net>
To: Rob Herring <robh@kernel.org>, Franklin S Cooper Jr <fcooper@ti.com>
Cc: dmitry.torokhov@gmail.com, octavian.purdila@intel.com,
irina.tirdea@intel.com, merker@debian.org,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, nsekhar@ti.com, nm@ti.com
Subject: Re: [PATCH 4/4] Input: goodix - Support interchanging x and y coordinates in hardware
Date: Thu, 27 Oct 2016 12:34:31 +0200 [thread overview]
Message-ID: <1477564471.2458.11.camel@hadess.net> (raw)
In-Reply-To: <20161026231816.a35orxe3mpsvcx3m@rob-hp-laptop>
On Wed, 2016-10-26 at 18:18 -0500, Rob Herring wrote:
> On Thu, Oct 20, 2016 at 02:59:17PM -0500, Franklin S Cooper Jr wrote:
> >
<snip>
> I'm not sure I follow why existing properties don't cover this.
Me neither. I certainly don't understand why the driver can't mangle
the data from the touchscreen all it wants. It's not like user-space is
talking to the touchscreen directly.
next prev parent reply other threads:[~2016-10-27 10:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:59 [PATCH 0/4] Input: goodix - Support dynamic reconfiguration Franklin S Cooper Jr
2016-10-20 19:59 ` Franklin S Cooper Jr
2016-10-20 19:59 ` [PATCH 1/4] Input: goodix - Restructure cfg checksum function Franklin S Cooper Jr
2016-10-20 19:59 ` Franklin S Cooper Jr
[not found] ` <20161020195917.20051-2-fcooper-l0cyMroinI0@public.gmane.org>
2016-10-27 10:32 ` Bastien Nocera
2016-10-27 10:32 ` Bastien Nocera
2016-10-20 19:59 ` [PATCH 2/4] Input: goodix - Allow tweaking of configuration file dynamically Franklin S Cooper Jr
2016-10-20 19:59 ` Franklin S Cooper Jr
2016-10-27 10:33 ` Bastien Nocera
[not found] ` <1477564424.2458.9.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2016-10-27 16:58 ` Franklin S Cooper Jr
2016-10-27 16:58 ` Franklin S Cooper Jr
2016-10-27 17:41 ` Bastien Nocera
2016-10-20 19:59 ` [PATCH 3/4] Input: goodix - Tweak configuration to use passed in touchscreen resolution Franklin S Cooper Jr
2016-10-20 19:59 ` Franklin S Cooper Jr
2016-10-26 23:10 ` Rob Herring
[not found] ` <20161020195917.20051-4-fcooper-l0cyMroinI0@public.gmane.org>
2016-10-27 10:34 ` Bastien Nocera
2016-10-27 10:34 ` Bastien Nocera
[not found] ` <1477564458.2458.10.camel-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
2016-10-27 17:03 ` Franklin S Cooper Jr
2016-10-27 17:03 ` Franklin S Cooper Jr
[not found] ` <20161020195917.20051-1-fcooper-l0cyMroinI0@public.gmane.org>
2016-10-20 19:59 ` [PATCH 4/4] Input: goodix - Support interchanging x and y coordinates in hardware Franklin S Cooper Jr
2016-10-20 19:59 ` Franklin S Cooper Jr
[not found] ` <20161020195917.20051-5-fcooper-l0cyMroinI0@public.gmane.org>
2016-10-26 23:18 ` Rob Herring
2016-10-26 23:18 ` Rob Herring
2016-10-27 10:34 ` Bastien Nocera [this message]
2016-10-27 17:42 ` Franklin S Cooper Jr
2016-10-27 17:42 ` Franklin S Cooper Jr
[not found] ` <317acd32-f363-3b2b-9e30-106d5b335342-l0cyMroinI0@public.gmane.org>
2016-10-28 0:08 ` Bastien Nocera
2016-10-28 0:08 ` Bastien Nocera
2016-10-27 17:54 ` Franklin S Cooper Jr
2016-10-27 17:54 ` Franklin S Cooper Jr
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=1477564471.2458.11.camel@hadess.net \
--to=hadess@hadess.net \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fcooper@ti.com \
--cc=irina.tirdea@intel.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=merker@debian.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=octavian.purdila@intel.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.