Input: atmel_mxt_ts - remove unnecessary platform data
authorNick Dyer <nick.dyer@itdev.co.uk>
Mon, 19 May 2014 05:59:20 +0000 (22:59 -0700)
committerDmitry Torokhov <dmitry.torokhov@gmail.com>
Mon, 19 May 2014 06:27:21 +0000 (23:27 -0700)
commit2cefdb1f0a27150755ef2730bafc58bf2ed16571
tree127925ae0d0eea796f8ef9465c591678f7145790
parent7cdcb8d104e6f0ec5d253d29e4849cdb2cf03aed
Input: atmel_mxt_ts - remove unnecessary platform data

It is not necessary to download these values to the maXTouch chip on every
probe, since they are stored in NVRAM. It makes life difficult when tuning
the device to keep them in sync with the config array/file, and requires a
new kernel build for minor tweaks.

These parameters only represent a tiny subset of the available
configuration options, tracking all of these options in platform data would
be a endless task. In addition, different versions of maXTouch chips may
have these values in different places or may not even have them at all.

Having these values also makes life more complex for device tree and other
platforms where having to define a static configuration isn't helpful.

Signed-off-by: Nick Dyer <nick.dyer@itdev.co.uk>
Acked-by: Benson Leung <bleung@chromium.org>
Acked-by: Yufeng Shen <miletus@chromium.org>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
arch/arm/mach-s5pv210/mach-goni.c
drivers/input/touchscreen/atmel_mxt_ts.c
drivers/platform/chrome/chromeos_laptop.c
include/linux/i2c/atmel_mxt_ts.h
This page took 0.034372 seconds and 5 git commands to generate.