All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 12 May 2014 14:02:24 -0600	[thread overview]
Message-ID: <537128D0.3060005@wwwdotorg.org> (raw)
In-Reply-To: <536BDFFD.4080009@itdev.co.uk>

On 05/08/2014 01:50 PM, Nick Dyer wrote:
> Stephen Warren wrote:
>> Anyway, I'd like to pull these patches into my local repo to build on.
>> Can you point me at a tree where Dmitry applied them even if not in
>> linux-next? Alternatively, does your github repo contain exactly the
>> patches from the recent mailing list posting you linked above?
> 
> https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/log/?h=atmel-mxt-ts
> 
> However, I have made minor updates on top of that to take account of API
> changes since he worked on them (reinit_completion).
> 
> The patches I posted at the end of March are the first 22 out of this tag:
> 
> https://github.com/ndyer/linux/tree/for-next-20140316-v8

I took those 22 patches, applied them on top of next-20150507 (which is
just what I happened to be developing on top of right now), and rebased
my patches which add DT support. You can find the result here if you want:

git://github.com/swarren/linux-tegra.git tegra_dev

However, with that code-base, the touchpad doesn't work for me. I see a
long pause and errors during boot:

> [    1.246253] atmel_mxt_ts 1-004b: Direct firmware load failed with error -2
> [    1.253120] atmel_mxt_ts 1-004b: Falling back to user helper
> [   61.394348] atmel_mxt_ts 1-004b: Failure to request config file maxtouch.cfg
> [   61.403717] atmel_mxt_ts 1-004b: Family: 130 Variant: 1 Firmware V1.0.AA Objects: 22

... and the touchpad doesn't work once X starts. With next-20140507 plus
the patches I sent to the mailing list, everything works.

I'm not sure if I'm supposed to have some configuration file now and
that's why it doesn't work, or whether some other problem has been
introduced? If I do need a config file, can you tell me what to put into it?

Thanks for any pointers.

  reply	other threads:[~2014-05-12 20:02 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 [this message]
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
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=537128D0.3060005@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.