From: Stephen Warren <swarren@wwwdotorg.org>
To: Nick Dyer <nick.dyer@itdev.co.uk>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benson Leung <bleung@chromium.org>,
Yufeng Shen <miletus@chromium.org>,
Daniel Kurtz <djkurtz@chromium.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
"Bowens, Alan" <Alan.Bowens@atmel.com>
Subject: Re: [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra
Date: Thu, 12 Jun 2014 11:12:22 -0600 [thread overview]
Message-ID: <5399DF76.8020108@wwwdotorg.org> (raw)
In-Reply-To: <53998E12.8050408@itdev.co.uk>
On 06/12/2014 05:25 AM, Nick Dyer wrote:
> Stephen Warren wrote:
>>> I will test this on my setup and see if I can figure out what is causing
>>> the problem.
>>
>> Nick, did you get anywhere reproducing my problem? Unfortunately with
>> your recent patches merged, I can't get the touchpad working at all,
>> whereas before I had a few simple patches that made it work:-(
>
> I haven't been able to reproduce your issue, I have a devicetree based
> system that will successfully probe without a config file.
>
> Could you send me the dmesg output with all of the driver debug enabled? It
> would be good to see how far it is getting.
My apologies; I should have retested before asking about this again. I
guess something must have changed in linux-next since the last time I
tested this.
With next-20140611 plus the following patches on top:
d3168ccd7d57 ARM: tegra: enable Atmel touchpad in defconfig
fc1d7c4aefe0 ARM: tegra: add touchpad to Venice2 DT
da5f283a52ea Input: atmel_mxt_ts: implement device tree parsing
22911ed92e76 Input: atmel_mxt_ts: define a device tree binding
57f79f65a8f9 Input: atmel_mxt_ts - Set pointer emulation on touchpads
... the driver built into the kernel, and no firmware available in
/lib/firmware, the touchpad now works.
Are you still expecting to take my DT binding patches above and resend them?
One bug I see is that the mouse doesn't seem to release when I drag it
(either through double clicking and holding on the second click, or by a
two-finger drag). Is that a known issue?
next prev parent reply other threads:[~2014-06-12 17:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:13 [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra Stephen Warren
2014-05-06 22:13 ` [PATCH 1/4] Input: atmel_mxt_ts - Set pointer emulation if is_tp Stephen Warren
2014-05-06 22:13 ` [PATCH 2/4] Input: atmel_mxt_ts - Read resolution from device memory Stephen Warren
2014-05-06 22:13 ` [PATCH 3/4] Input: atmel_mxt_ts: define a device tree binding Stephen Warren
2014-05-06 22:13 ` [PATCH 4/4] Input: atmel_mxt_ts: implement device tree parsing Stephen Warren
2014-05-06 22:16 ` [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra Benson Leung
2014-05-06 22:35 ` Stephen Warren
2014-05-08 16:01 ` Nick Dyer
2014-05-08 16:41 ` Stephen Warren
2014-05-08 17:26 ` Dmitry Torokhov
2014-05-08 19:56 ` Nick Dyer
2014-05-09 18:49 ` Mark Brown
2014-05-13 1:17 ` Dmitry Torokhov
2014-05-08 19:50 ` Nick Dyer
2014-05-12 20:02 ` Stephen Warren
2014-05-13 1:16 ` Dmitry Torokhov
2014-05-13 2:31 ` Stephen Warren
2014-05-16 16:21 ` Nick Dyer
2014-05-16 16:40 ` Stephen Warren
2014-05-20 16:19 ` Nick Dyer
2014-06-11 18:17 ` Stephen Warren
2014-06-12 11:25 ` Nick Dyer
2014-06-12 17:12 ` Stephen Warren [this message]
2014-06-12 17:37 ` Stephen Warren
2014-06-30 16:11 ` Stephen Warren
2014-06-02 9:50 ` Sekhar Nori
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=5399DF76.8020108@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Alan.Bowens@atmel.com \
--cc=bleung@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=nick.dyer@itdev.co.uk \
--cc=swarren@nvidia.com \
/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.