Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp874565pxb; Tue, 1 Feb 2022 12:12:17 -0800 (PST) X-Google-Smtp-Source: ABdhPJyXYuMCn5kjX7d5f2Q1qbiNlCVibVpzqswccMs6DkuYQHMU3UIRu/s0l1POrSEzTuAngm1o X-Received: by 2002:a17:907:1c0d:: with SMTP id nc13mr22799222ejc.657.1643746337384; Tue, 01 Feb 2022 12:12:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643746337; cv=none; d=google.com; s=arc-20160816; b=yGJ11FAVKaZpUgW5mdxsDgcMB/BbVvT6sZfuKCPjIHHvC+0Z43o0PYN5BmCBH29ZJR H1UWllgEeShk6BQiyqrl0q7o9uWwjpGpEZaMGz0T0RmMDb2EF62xGsDpKzS32xcEKAzF kemUkcapj9cFt1B7X41paeg1qi6LBC4UbCRmwCUqBY17iou7SkZL1SS85hMzUAC6ZtS4 h7mw3+Nxm+JaxG651dAZW3DaBoYtdop/0QRtGtup6TuXtAwjhWGw/PRAoK5P4IjiONYz CnpmZJncERH8liJdLmIJDxw16GD0S/dyxnZcRq3LoVZjbsjuabEHK7fxBUbPB7YKBRsa pzwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=i+azSqo26FBS1YDJltL8aLhxm9DQqOHkO1G8WSfNRoQ=; b=Kfh/JO0zPL16KtMpDFo5VH7SUaXXZafn8uHwCx+TqpcYYKwrOk4HQNuKomESItvItQ IPsKifJFCqJQSlwKzA2jzERmNr2P434tFSPDZGLHE6EJy/Eg+jGjzsTRVCvhRFo0H76q I+2W1d8eqfvvRdViXUVvix206iG2cB3nkNQpCw+XzngqobwD6jDIu5s7lRTfYWkOjxMc tGGyNVKREJlye4/yFloc8BFwJ+tOhJT9G6kW13HEDCl1Nu7Yva46/0Dx2fztGC2UjutS sOM9K6VU7KO9rdxVXF1ZcblQGfEU8wHqimpzkPbtV76f8/U+T8Zp+n7n3tI3GyNwNbyj uRMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=U2hU0I6u; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i7si10228260edr.106.2022.02.01.12.11.51; Tue, 01 Feb 2022 12:12:17 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=U2hU0I6u; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378028AbiAaLhM (ORCPT + 99 others); Mon, 31 Jan 2022 06:37:12 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47974 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350380AbiAaLYy (ORCPT ); Mon, 31 Jan 2022 06:24:54 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C3ABC08E90D; Mon, 31 Jan 2022 03:15:21 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 2DCAEB82A76; Mon, 31 Jan 2022 11:15:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6DD92C340E8; Mon, 31 Jan 2022 11:15:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1643627719; bh=6KaW5Y5nA33xZyeLXiMYIERa4OTwAfNGh5VGj+IhCh8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=U2hU0I6uLWLpaqXRk0tfG0DwbjAmUm+ldsR1rW1L2fd18gb0Q4ZTsdWG5MSiIVRqs 7qQpAtTzt3qNQOAlk0Dn2aFhyapNLiyyTlDpC9vKC1m2n+s1L1dcl6uNY1bEPyp1Vo 3OPY5wUoLStyutdK/BXwy99f+6LqGUaQfyof6AGE= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Dmitry Osipenko , Guenter Roeck , Sasha Levin Subject: [PATCH 5.15 132/171] hwmon: (lm90) Re-enable interrupts after alert clears Date: Mon, 31 Jan 2022 11:56:37 +0100 Message-Id: <20220131105234.476637088@linuxfoundation.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20220131105229.959216821@linuxfoundation.org> References: <20220131105229.959216821@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Guenter Roeck [ Upstream commit bc341a1a98827925082e95db174734fc8bd68af6 ] If alert handling is broken, interrupts are disabled after an alert and re-enabled after the alert clears. However, if there is an interrupt handler, this does not apply if alerts were originally disabled and enabled when the driver was loaded. In that case, interrupts will stay disabled after an alert was handled though the alert handler even after the alert condition clears. Address the situation by always re-enabling interrupts after the alert condition clears if there is an interrupt handler. Fixes: 2abdc357c55d9 ("hwmon: (lm90) Unmask hardware interrupt") Cc: Dmitry Osipenko Signed-off-by: Guenter Roeck Signed-off-by: Sasha Levin --- drivers/hwmon/lm90.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c index cc5e48fe304b1..e4ecf3440d7cf 100644 --- a/drivers/hwmon/lm90.c +++ b/drivers/hwmon/lm90.c @@ -848,7 +848,7 @@ static int lm90_update_device(struct device *dev) * Re-enable ALERT# output if it was originally enabled and * relevant alarms are all clear */ - if (!(data->config_orig & 0x80) && + if ((client->irq || !(data->config_orig & 0x80)) && !(data->alarms & data->alert_alarms)) { if (data->config & 0x80) { dev_dbg(&client->dev, "Re-enabling ALERT#\n"); -- 2.34.1