linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Dyer <nick.dyer@itdev.co.uk>
To: Stephen Warren <swarren@wwwdotorg.org>
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: Fri, 16 May 2014 17:21:26 +0100	[thread overview]
Message-ID: <53763B06.7020100@itdev.co.uk> (raw)
In-Reply-To: <537128D0.3060005@wwwdotorg.org>

Stephen Warren wrote:
> On 05/08/2014 01:50 PM, Nick Dyer wrote:
>> 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

Thanks for this. Would you be happy for me to pick these changes up and
include them along with the other work I am sending to Dmitry? I am just
beginning to do various updates to the whole series, one of the things I
need to sort out is the device tree support.

I will need to add device tree parameters for the touchscreen as well as
the touchpad, of course.

By the way, the driver should work without any firmware file and just use
the firmware and configuration from NVRAM - request_firmware() returns a
failure and it continues through mxt_initialize().

In a later patch in my long series, I make the MXT_CFG_NAME configurable
from platform data (because you may have multiple devices needing different
configs), and leaving it null means the call to request_firmware() is skipped.

  parent reply	other threads:[~2014-05-16 16:21 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 [this message]
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=53763B06.7020100@itdev.co.uk \
    --to=nick.dyer@itdev.co.uk \
    --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=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.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 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).