mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-10 06:09:23 -04:00
Optimize zinitix touch firmware upgrade flow
Found that zinitix touch firmware upgrade failed due to checksum error,but now firmware version check right and touch works well. It's not sram broken or burst upgrade problem, suspect "0x55aa" check sum not stable. Change the firmware check to a more stable way after burst upgrade. Change-Id: I1edb0dc608179e3d64c8ac931603aae9e28cd78d Signed-off-by: Wenge Zhu <zhuwg1@motorola.com> Reviewed-on: https://gerrit.mot.com/2604234 SME-Granted: SME Approvals Granted SLTApproved: Slta Waiver Tested-by: Jira Key Reviewed-by: Jichao Zou <zoujc@motorola.com> Submit-Approved: Jira Key
This commit is contained in:
parent
7f6626a7ca
commit
e12191b812
1 changed files with 6 additions and 10 deletions
|
|
@ -1421,25 +1421,21 @@ static bool ts_upgrade_firmware(struct bt541_ts_info *info,
|
|||
struct i2c_client *client = info->client;
|
||||
u16 flash_addr;
|
||||
int retry_cnt = 0;
|
||||
#ifndef BURST_UPGRADE
|
||||
int i;
|
||||
#else
|
||||
#ifdef BURST_UPGRADE
|
||||
struct bt541_ts_platform_data *pdata = info->pdata;
|
||||
#endif
|
||||
int page_sz = 64;
|
||||
u16 chip_code;
|
||||
|
||||
#ifndef BURST_UPGRADE
|
||||
u8 *verify_data;
|
||||
#else
|
||||
#ifdef VERIFY_CHECKSUM
|
||||
u16 year, chip_fw_year;
|
||||
u16 month, chip_fw_month;
|
||||
u16 day, chip_fw_day;
|
||||
u16 total_version, chip_fw_total_version;
|
||||
u16 chip_check_sum;
|
||||
#endif
|
||||
#else
|
||||
int i;
|
||||
u8 *verify_data;
|
||||
|
||||
#ifndef BURST_UPGRADE
|
||||
verify_data = kzalloc(size, GFP_KERNEL);
|
||||
if (verify_data == NULL) {
|
||||
zinitix_printk(KERN_ERR "cannot alloc verify buffer\n");
|
||||
|
|
@ -1638,7 +1634,7 @@ retry_upgrade:
|
|||
goto fail_upgrade;
|
||||
}
|
||||
#endif
|
||||
#ifndef BURST_UPGRADE
|
||||
#ifndef VERIFY_CHECKSUM
|
||||
zinitix_printk("read firmware data\n");
|
||||
|
||||
for (flash_addr = 0; flash_addr < size; ) {
|
||||
|
|
|
|||
Loading…
Reference in a new issue