Hi Nick,
> The following patches are a large series of updates in functionality to the
> atmel_mxt_ts touch driver. They apply cleanly to input/next.
I guess this is no longer true.
> These changes address some of the same issues that appear in the patchsets
> submitted by Daniel Kurtz and Peter Meerwald. However, they go much further in
> adding support for new objects, improving performance, and increasing
> reliability. They have been regularly regression tested against old and new
> chips which use the same protocol.
>
> We also provide a set of user-space utilities as open source which are
> available from github and work well with this driver:
> https://github.com/atmel-maxtouch/obp-utils
>
> Most of my focus in working on these changes has been to support Atmel's
> customers, who tend not to be using the mainline kernel. Unfortunately this
> has generated somewhat of a backlog in getting these improvements into
> mainline. My current focus is to get these improvements upstream and I have
> time allocated to make any alterations as necessary. Since the scope of this
> patchset is so large any upstream delta tends to cause a big rebasing effort.
> I would suggest that I merge any useful improvements from the other patchsets
> to make a combined patchset.
Are you planning to submit a version for 3.9? If you do, please
consider sending a smaller set.
Thanks,
Henrik
Henrik Rydberg wrote:
>> Most of my focus in working on these changes has been to support Atmel's
>> customers, who tend not to be using the mainline kernel. Unfortunately this
>> has generated somewhat of a backlog in getting these improvements into
>> mainline. My current focus is to get these improvements upstream and I have
>> time allocated to make any alterations as necessary. Since the scope of this
>> patchset is so large any upstream delta tends to cause a big rebasing effort.
>> I would suggest that I merge any useful improvements from the other patchsets
>> to make a combined patchset.
>
> Are you planning to submit a version for 3.9? If you do, please
> consider sending a smaller set.
My goal is to try and get our changes into 3.10, we still have a couple of
bugs to shake out (unfortunately in the bootloading code, which is at the
front of the series), I will post an updated series once I have resolved that.
You can see the WIP here:
https://github.com/ndyer/linux/commits/for-next