linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: linux-input@vger.kernel.org, kernel@pengutronix.de,
	patchwork-lst@pengutronix.de
Subject: Re: [PATCH] Input: synaptics-rmi4 - re-enable IRQs in f34v7_do_reflash
Date: Mon, 2 Dec 2019 10:27:51 -0800	[thread overview]
Message-ID: <20191202182751.GH50317@dtor-ws> (raw)
In-Reply-To: <20191129133514.23224-1-l.stach@pengutronix.de>

On Fri, Nov 29, 2019 at 02:35:14PM +0100, Lucas Stach wrote:
> F34 is a bit special as it reinitializes the device and related driver
> structs during the firmware update. This clears the fn_irq_mask which
> will then prevent F34 from receiving further interrupts, leading to
> timeouts during the firmware update. Make sure to reinitialize the
> IRQ enables at the appropriate times.
> 
> The issue is in F34 code, but the commit in the fixes tag exposed the
> issue, as before this commit things would work by accident.
> 
> Fixes: 363c53875aef (Input: synaptics-rmi4 - avoid processing unknown IRQs)
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>

Applied, thank you.

> ---
>  drivers/input/rmi4/rmi_f34v7.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/input/rmi4/rmi_f34v7.c b/drivers/input/rmi4/rmi_f34v7.c
> index a4cabf52740c..74f7c6f214ff 100644
> --- a/drivers/input/rmi4/rmi_f34v7.c
> +++ b/drivers/input/rmi4/rmi_f34v7.c
> @@ -1189,6 +1189,9 @@ int rmi_f34v7_do_reflash(struct f34_data *f34, const struct firmware *fw)
>  {
>  	int ret;
>  
> +	f34->fn->rmi_dev->driver->set_irq_bits(f34->fn->rmi_dev,
> +					       f34->fn->irq_mask);
> +
>  	rmi_f34v7_read_queries_bl_version(f34);
>  
>  	f34->v7.image = fw->data;
> -- 
> 2.20.1
> 

-- 
Dmitry

      reply	other threads:[~2019-12-02 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 13:35 [PATCH] Input: synaptics-rmi4 - re-enable IRQs in f34v7_do_reflash Lucas Stach
2019-12-02 18:27 ` Dmitry Torokhov [this message]

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=20191202182751.GH50317@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-input@vger.kernel.org \
    --cc=patchwork-lst@pengutronix.de \
    /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).