linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Henrik Rydberg <rydberg@euromail.se>,
	Benson Leung <bleung@chromium.org>,
	Yufeng Shen <miletus@chromium.org>,
	Nick Dyer <nick.dyer@itdev.co.uk>,
	Joonyoung Shim <jy0922.shim@samsung.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	olofj@chromium.org
Subject: Re: [PATCH 06/10] Input: atmel_mxt_ts - destroy state before fw update and restore after
Date: Wed, 13 Feb 2013 13:47:42 -0800	[thread overview]
Message-ID: <20130213214742.GD23390@core.coreip.homeip.net> (raw)
In-Reply-To: <1359706312-24642-7-git-send-email-djkurtz@chromium.org>

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 afterward.
> 
> Two benefits of this:
>  1) Since there is no input device during fw update, no need to worry
> about device open/close events.
>  2) If firmware update fails, the device and driver will still be in
> bootloader mode and an improperly configured input device will not exist.
> 
> Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> ---
>  drivers/input/touchscreen/atmel_mxt_ts.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
> index 76a25d3..c74f5a5 100644
> --- a/drivers/input/touchscreen/atmel_mxt_ts.c
> +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
> @@ -1001,6 +1001,13 @@ static int mxt_load_fw(struct device *dev, const char *fn)
>  		client->addr = MXT_BOOT_HIGH;
>  
>  bootloader_ready:
> +	/* Free any driver state. It will get reinitialized after fw update. */
> +	mxt_free_object_table(data);
> +	if (data->input_dev) {
> +		input_unregister_device(data->input_dev);
> +		data->input_dev = NULL;
> +	}
> +
>  	ret = mxt_check_bootloader(client, MXT_WAITING_BOOTLOAD_CMD);
>  	if (ret)
>  		goto out;
> @@ -1068,9 +1075,8 @@ static ssize_t mxt_update_fw_store(struct device *dev,
>  		/* Wait for reset */
>  		msleep(MXT_FWRESET_TIME);
>  
> -		mxt_free_object_table(data);
> -
>  		mxt_initialize(data);
> +		mxt_input_dev_create(data);

What if it fails?

>  	}
>  
>  	enable_irq(data->irq);
> -- 
> 1.8.1
> 

-- 
Dmitry

  reply	other threads:[~2013-02-13 21:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01  8:11 [PATCH 00/10] Input: atmel_mxt_ts - make fw update more robust Daniel Kurtz
2013-02-01  8:11 ` [PATCH 01/10] Input: atmel_mxt_ts - refactor i2c error handling Daniel Kurtz
2013-02-09 17:25   ` Henrik Rydberg
2013-02-01  8:11 ` [PATCH 02/10] Input: atmel_mxt_ts - register input device before request_irq Daniel Kurtz
2013-02-13 21:42   ` Dmitry Torokhov
2013-02-01  8:11 ` [PATCH 03/10] Input: atmel_mxt_ts - refactor input device creation Daniel Kurtz
2013-02-01  8:11 ` [PATCH 04/10] Input: atmel_mxt_ts - handle bootloader mode at probe Daniel Kurtz
2013-02-13 21:46   ` Dmitry Torokhov
2013-02-13 22:24     ` Benson Leung
2013-02-01  8:11 ` [PATCH 05/10] Input: atmel_mxt_ts - handle errors during fw update Daniel Kurtz
2013-02-01  8:11 ` [PATCH 06/10] Input: atmel_mxt_ts - destroy state before fw update and restore after Daniel Kurtz
2013-02-13 21:47   ` Dmitry Torokhov [this message]
2013-02-01  8:11 ` [PATCH 07/10] Input: atmel_mxt_ts - refactor bootloader entry/exit Daniel Kurtz
2013-02-01  8:11 ` [PATCH 08/10] Input: atmel_mxt_ts - wait for CHG assert in mxt_check_bootloader Daniel Kurtz
2013-02-01  8:11 ` [PATCH 09/10] Input: atmel_mxt_ts - wait for CHG after bootloader resets Daniel Kurtz
2013-02-01  8:11 ` [PATCH 10/10] Input: atmel_mxt_ts - increase FWRESET_TIME Daniel Kurtz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130213214742.GD23390@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=bleung@chromium.org \
    --cc=djkurtz@chromium.org \
    --cc=jy0922.shim@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miletus@chromium.org \
    --cc=nick.dyer@itdev.co.uk \
    --cc=olofj@chromium.org \
    --cc=rydberg@euromail.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).