From: Nick Dyer <nick.dyer@itdev.co.uk>
To: Dan Murphy <dmurphy@ti.com>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>
Subject: Re: atmel_mxt_ts driver DTS adoption
Date: Mon, 30 Sep 2013 16:41:48 +0100 [thread overview]
Message-ID: <52499BBC.2060801@itdev.co.uk> (raw)
In-Reply-To: <5241CC68.70909@ti.com>
Hi Dan-
Dan Murphy wrote:
> I have been looking around and I am finding numerous patches for the
> atmel_mxt_ts file to adopt it to DTS.
>
> The last status I have seen was we were waiting for some re-write of
> the file and that was in April.
>
> Are there any recent patches for this? And are they ready?
>
> I have not followed the input list so I am sorry for not being up to
> date on this.
There is a big pending update to atmel_mxt_ts that I sent to linux-input on
27th June this year. It is combination of work done by the Google Chromium
guys (for the Pixel laptop) and by myself (working for Atmel UK). Dimitry
Torokhov was working on merging it as of earlier this month, I don't know
how far along he is with it.
Latest version is here:
https://github.com/ndyer/linux/commits/for-next
Supporting DTS is very high on my priority list as the next item of work,
amongst various other small features and code improvements. I should say,
some of those patches make large changes to the platform data required. If
you would like to send me a patch on top of the current set I am happy to
generalise if necessary, include it in the set of changes and manage
forwarding it to Dimitry in due course.
cheers
Nick
prev parent reply other threads:[~2013-09-30 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 17:31 atmel_mxt_ts driver DTS adoption Dan Murphy
2013-09-30 15:41 ` Nick Dyer [this message]
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=52499BBC.2060801@itdev.co.uk \
--to=nick.dyer@itdev.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=dmurphy@ti.com \
--cc=linux-input@vger.kernel.org \
--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).