summaryrefslogtreecommitdiffstats
path: root/drivers/input
diff options
context:
space:
mode:
authorDmitry Torokhov <dmitry.torokhov@gmail.com>2015-04-14 13:50:09 -0700
committerOlof Johansson <olof@lixom.net>2015-04-24 22:07:14 -0700
commit96cba9b00e297303774bec59e192064d20adeb3d (patch)
tree6b72ce956c4fc8c8017cb8cf60812321883e765a /drivers/input
parent8ce580932f8ee40903017a6f1408ccfff319a6a5 (diff)
downloadlinux-96cba9b00e297303774bec59e192064d20adeb3d.tar.bz2
platform/chrome: chromeos_laptop - instantiate Atmel at primary address
The new Atmel MXT driver expects i2c client's address contain the primary (main address) of the chip, and calculates the expected bootloader address form the primary address. Unfortunately chrome_laptop does probe the devices and if touchpad (or touchscreen, or both) comes up in bootloader mode the i2c device gets instantiated with the bootloader address which confuses the driver. To work around this issue let's probe the primary address first. If the device is not detected at the primary address we'll probe alternative addresses as "dummy" devices. If any of them are found, destroy the dummy client and instantiate client with proper name at primary address still. Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> Signed-off-by: Olof Johansson <olof@lixom.net>
Diffstat (limited to 'drivers/input')
0 files changed, 0 insertions, 0 deletions