kernel-fxtec-pro1x/drivers/platform/chrome
Dmitry Torokhov 96cba9b00e 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>
2015-04-24 22:07:14 -07:00
..
chromeos_laptop.c platform/chrome: chromeos_laptop - instantiate Atmel at primary address 2015-04-24 22:07:14 -07:00
chromeos_pstore.c platform/chrome: pstore: fix dmi table to match all chrome systems 2014-07-10 10:38:41 -07:00
cros_ec_dev.c platform/chrome: cros_ec_dev - fix Unknown escape '%' warning 2015-03-04 11:23:10 -08:00
cros_ec_dev.h platform/chrome: Expose Chrome OS Lightbar to users 2015-02-26 15:45:16 -08:00
cros_ec_lightbar.c platform/chrome: cros_ec_lightbar - fix duplicate const warning 2015-03-04 11:23:13 -08:00
cros_ec_lpc.c platform/chrome: cros_ec_lpc - Include linux/io.h header file 2015-03-04 11:28:28 -08:00
cros_ec_sysfs.c platform/chrome: Create sysfs attributes for the ChromeOS EC 2015-02-26 15:45:12 -08:00
Kconfig platform/chrome: cros_ec_lpc - Depend on X86 || COMPILE_TEST 2015-03-04 11:29:45 -08:00
Makefile platform/chrome: Expose Chrome OS Lightbar to users 2015-02-26 15:45:16 -08:00