Input: atmel_mxt_ts - add bootloader addresses for new chips
Later chips (for example mXT1664S) different mappings for bootloader addresses. This means that we must look at the family ID to determine which address to use. 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>
This commit is contained in:
parent
385deb962a
commit
44a0bab215
|
@ -387,6 +387,12 @@ static int mxt_lookup_bootloader_address(struct mxt_data *data)
|
|||
switch (appmode) {
|
||||
case 0x4a:
|
||||
case 0x4b:
|
||||
/* Chips after 1664S use different scheme */
|
||||
if (data->info.family_id >= 0xa2) {
|
||||
bootloader = appmode - 0x24;
|
||||
break;
|
||||
}
|
||||
/* Fall through for normal case */
|
||||
case 0x4c:
|
||||
case 0x4d:
|
||||
case 0x5a:
|
||||
|
|
Loading…
Reference in New Issue