Re: [PATCH 06/10] Input: atmel_mxt_ts - destroy state before fw update and restore after

2013-02-13 Thread Dmitry Torokhov
On Fri, Feb 01, 2013 at 04:11:48PM +0800, Daniel Kurtz wrote: > After firmware update, the device may have a completely different object > table which corresponds to an input device with different properties. > So, destroy the old state before firmware update, and completely > reinitialize the

Re: [PATCH 06/10] Input: atmel_mxt_ts - destroy state before fw update and restore after

2013-02-13 Thread Dmitry Torokhov
On Fri, Feb 01, 2013 at 04:11:48PM +0800, Daniel Kurtz wrote: After firmware update, the device may have a completely different object table which corresponds to an input device with different properties. So, destroy the old state before firmware update, and completely reinitialize the driver

[PATCH 06/10] Input: atmel_mxt_ts - destroy state before fw update and restore after

2013-02-01 Thread Daniel Kurtz
After firmware update, the device may have a completely different object table which corresponds to an input device with different properties. So, destroy the old state before firmware update, and completely reinitialize the driver afterward. Two benefits of this: 1) Since there is no input

[PATCH 06/10] Input: atmel_mxt_ts - destroy state before fw update and restore after

2013-02-01 Thread Daniel Kurtz
After firmware update, the device may have a completely different object table which corresponds to an input device with different properties. So, destroy the old state before firmware update, and completely reinitialize the driver afterward. Two benefits of this: 1) Since there is no input