Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp871424ybl; Wed, 11 Dec 2019 08:46:49 -0800 (PST) X-Google-Smtp-Source: APXvYqzsezznahS7OJbcMgXv+YCtyT8inb7salAPSSjRaExOXp9xvVllgaT5IHtgz74wpSYmqO9W X-Received: by 2002:a05:6830:2142:: with SMTP id r2mr3103458otd.334.1576082809193; Wed, 11 Dec 2019 08:46:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576082809; cv=none; d=google.com; s=arc-20160816; b=rRP7WZ1TOJd3tp0TbavxF9IZh2hpuVvWtnChdMGJ99pk5s6cRFAlwLBBpIMZBNeMfy /LRfJrn0ZB0iZcKThsiazJBNjspsaPUyKqTCmJqo3jbl/U6VYv5ysycKAdvb5bCpJJj2 HypoxTSZfUDZtHiIt0G4VlVYAhvqONHk9Q6LSoLNkyBukFGkEMr5i58UrKG7Sg+zUlev dWuFW2Jiha2bNkLAkEEowlkYVJcJF+AVLT3JPDI4GxSHTC8JZL3RAio6tmys0NlikYXj iAjuSFUYIP/ouF8D3wnHaHTR6VqF5STFBhVeAfv/qPiHm/phDaGIUVJMNbyiktmOj+hD GXHA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=C8a0VPOiqokpN3ih8uUw4DeHqn4RTko5ijK0mmLPwf4=; b=dMS6JUEMdMMY89zZ8jbAhyaOhszKvOCrYp74NdbTRICYOOFgWF41rAsb1JQeiwg/2q 7h4YNQu7HBeq8MBhT0Dgqj/MW/wu9sALVc+VY5dXl2mb6Y5YuwyaMr5SZeQDLsDJSKaq jK8JYs9ENBs18eZgDilAV/2q1Ni5qZCgKAT5tat8NXvJrn0Nvk5xnoluVAp/65WnsCC9 XY1IJxgErPjdfOqDRwgkb9KKY817qugO807yDh2VDgE9eLkmMqtmNWuNPVthM2aIdgFm +sXCvXkTnBWtho4J5tayIN2HoGneDKhQwSDxS3I9oA0QCvFY1q858hT0/ZiyMMvXpSyY Ycjw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=NUtDKExS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i12si1491051oik.171.2019.12.11.08.46.27; Wed, 11 Dec 2019 08:46:49 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=NUtDKExS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732867AbfLKPtk (ORCPT + 99 others); Wed, 11 Dec 2019 10:49:40 -0500 Received: from mail.kernel.org ([198.145.29.99]:55946 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732853AbfLKPYg (ORCPT ); Wed, 11 Dec 2019 10:24:36 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 832C9208C3; Wed, 11 Dec 2019 15:24:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576077876; bh=TxFF3dCzgNZSD/LydwsZgVZni2PRmnqkI8Is8MlGsmM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=NUtDKExSN/43UmRVDiq6LkF0GspToMs6L8+5yJ+4fo2sRKqxUOXJaTR7H+c8p/c/0 +Fq1DLbel73Yi/TxosPe0Odpo+bD9bdfdF8wR+fjAENL+J2lDsyOb85tgH5/oW9SZS 5iqAclKyHzW/2k94IQjt/VFapLQ1nEeDIpN0Ej04= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Lucas Stach , Dmitry Torokhov Subject: [PATCH 4.19 205/243] Input: synaptics-rmi4 - re-enable IRQs in f34v7_do_reflash Date: Wed, 11 Dec 2019 16:06:07 +0100 Message-Id: <20191211150353.022799599@linuxfoundation.org> X-Mailer: git-send-email 2.24.1 In-Reply-To: <20191211150339.185439726@linuxfoundation.org> References: <20191211150339.185439726@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Lucas Stach commit 86bcd3a12999447faad60ec59c2d64d18d8e61ac upstream. 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 Link: https://lore.kernel.org/r/20191129133514.23224-1-l.stach@pengutronix.de Cc: stable@vger.kernel.org Signed-off-by: Dmitry Torokhov Signed-off-by: Greg Kroah-Hartman --- drivers/input/rmi4/rmi_f34v7.c | 3 +++ 1 file changed, 3 insertions(+) --- a/drivers/input/rmi4/rmi_f34v7.c +++ b/drivers/input/rmi4/rmi_f34v7.c @@ -1192,6 +1192,9 @@ int rmi_f34v7_do_reflash(struct f34_data { 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;