Received: by 2002:a05:7208:9594:b0:7e:5202:c8b4 with SMTP id gs20csp2365133rbb; Tue, 27 Feb 2024 22:08:14 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCViV5KfMbd8iSKuzzw9zsQN9uKOvSmB5CXhtyn9C04VZbSOnRmXRTefDMCRCeznrRse1dwCYMx8N71W4WF240/erAn+OAmBdVis2vPAlA== X-Google-Smtp-Source: AGHT+IGj16TSlwK+glmZ126JiRJyLuAam5/Uwflnfn0hkqT7IP4m6t5mDNcba7/CK7nbQKy9IHuD X-Received: by 2002:a05:6830:208:b0:6e4:71de:aea4 with SMTP id em8-20020a056830020800b006e471deaea4mr12083060otb.3.1709100494274; Tue, 27 Feb 2024 22:08:14 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1709100494; cv=pass; d=google.com; s=arc-20160816; b=XqjgE+1NOIi49+4Vyy/lFYMyZxDSK5qTZdN5On5YEi9ct9B5+QgrzLD2A1zVWmuoHL JxYp74EqL7Luq4gi52NTPLBKTpjhtviPsRpTIR3BquOtGsjtbOKwQavzU202wCXBX8ku 7rywYHAja8WxkuPBv3mZYz8/4MyF+FIJrO4ItTik2jUgmDc3b0g8Yu/cUduGnOhstCPn irMDP9w0j8HZHm6CKYJ9OpkdmvzYTAw8J8f228/fPE8mqzmQZoJNR4wz7lyC/eIWBUIy eMWIpKMvT7Yc+ZJNRSR1+jhCCiFDfLRZkHaXZA12v/5DUy7RU+qhJkY/6psKACIj9djx bKoQ== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:date:message-id:dkim-signature; bh=dlFX39e4Le6PT/fbfEe1U4Pxl4yfCvn/ID1DA6HRvSk=; fh=TSciPreNWGU1ofHMVwL4bX0XuU5FLXdOiGUw7GZt6g0=; b=ypYg3XZV+iyZTPKGxvPYwibRxNjRb76QfHl+Gd1OEHK8wDhkcklciRg6LrmDID0UvY w0arEz3IguejaaByfeDWJNTddUjbgPK2ZD/o5incHws+0sh+tQJaZwUD1gIMjX4599ni bjPBdU+pTbVvdV7MU/wJ9FirJcj5Atn1vF1V3JPg2PoYdM8UfYvMAIHbOCVUahUbKxaI SSFzpwnUfzCvJbykxNGmdloyFS11qMnvEyShmh7zq4GqfoNhAXUAMTrnjCBARpeb8qK2 n/LftgfRxbLDLNB5HDdGaoct1JFFM8x6J6t84qqeCJt4bKq0JeN14xBG2FW2VMdV4LBL Or5A==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=GtWFzRk9; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-84551-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-84551-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [147.75.48.161]) by mx.google.com with ESMTPS id i22-20020a632216000000b005dc42ad5d65si6857807pgi.622.2024.02.27.22.08.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Feb 2024 22:08:14 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-84551-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=GtWFzRk9; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-84551-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-84551-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 7FDFDB21DD2 for ; Wed, 28 Feb 2024 06:05:10 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 3483521A1C; Wed, 28 Feb 2024 06:05:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="GtWFzRk9" Received: from lelv0142.ext.ti.com (lelv0142.ext.ti.com [198.47.23.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B3C8C21362; Wed, 28 Feb 2024 06:04:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.23.249 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709100300; cv=none; b=F1DbAe2XN6zCVzZXBLXdsCKJcKVL1IvZ6dvYBDFVZXGJHonennnroRJhh91if78LAjU8veSsGf38H736SGbqhQ6+B+FvkW2sogSKldcmBq6wApkYn2v13e5wQM+szqmyn7EFZ8v3FkaPpp0/kPao+tjoRwzXLk9+XDXhFvi1Hp4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709100300; c=relaxed/simple; bh=Bx/72HQNWWv+7pa7o40RHu5kyjc1ZrMEMUJaH4AtW+0=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=rERwsHzDGWTT6LAWoga2KLH2Bos7ihARgRolraHKTZ707z713WsmqLwLhOIQUMh3g/mWOgHogAOzWU6OPo3oJTRZw7E4/tkYkDqb98rS+bLkDmhTpS2LDkZVw3ReRMr0Dal5PdFLCdI9C0NSb6Z9FrxgPoSDSA70nxyIa5LJiNI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=GtWFzRk9; arc=none smtp.client-ip=198.47.23.249 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 41S64T3S055457; Wed, 28 Feb 2024 00:04:29 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1709100269; bh=dlFX39e4Le6PT/fbfEe1U4Pxl4yfCvn/ID1DA6HRvSk=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=GtWFzRk9RjdIo1EqAe+uxMjXXCgkL8SCURhE2rKK+g1fRXleQnQYwFIpfgvGQjBC7 E4YStneUeimUG2Z806Dq+VReRykRKQ2bCMOQyMvRzo9F9uQJnNVkunBWGjLSjWhSqf XfxroEYiojgz8po2EUSuERBof8qZdyF5Fy3xBOVE= Received: from DFLE105.ent.ti.com (dfle105.ent.ti.com [10.64.6.26]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 41S64Taw097518 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 28 Feb 2024 00:04:29 -0600 Received: from DFLE103.ent.ti.com (10.64.6.24) by DFLE105.ent.ti.com (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 28 Feb 2024 00:04:28 -0600 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 28 Feb 2024 00:04:28 -0600 Received: from [172.24.227.68] (dhruva.dhcp.ti.com [172.24.227.68]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 41S64O8F115774; Wed, 28 Feb 2024 00:04:25 -0600 Message-ID: <1390e743-2216-4435-b2ef-7d92a55605b1@ti.com> Date: Wed, 28 Feb 2024 11:34:23 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] PM: wakeirq: fix wake irq warning in system suspend stage To: Qingliang Li , "Rafael J . Wysocki" , Pavel Machek , Len Brown , Greg Kroah-Hartman , Matthias Brugger , AngeloGioacchino Del Regno , Johan Hovold , Tony Lindgren , Dhruva Gole CC: , , , References: <20240228020040.25815-1-qingliang.li@mediatek.com> Content-Language: en-US From: Dhruva Gole In-Reply-To: <20240228020040.25815-1-qingliang.li@mediatek.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Hi, On 28/02/24 07:30, Qingliang Li wrote: > When driver registers the wake irq with reverse enable ordering, > the wake irq will be re-enabled when entering system suspend, triggering > an 'Unbalanced enable for IRQ xxx' warning. The wake irq will be > enabled in both dev_pm_enable_wake_irq_complete() and dev_pm_arm_wake_irq() > > To fix this issue, complete the setting of WAKE_IRQ_DEDICATED_ENABLED flag > in dev_pm_enable_wake_irq_complete() to avoid redundant irq enablement. Just trying to understand, why not in dev_pm_arm_wake_irq ? Is it cuz it's called much after dev_pm_enable_wake_irq_complete ? Not sure what's the exact call order, but I am assuming dev_pm_enable_wake_irq_complete is more of a runtime thing and dev_pm_arm_wake_irq happens finally at system suspend? > > Fixes: 8527beb12087 ("PM: sleep: wakeirq: fix wake irq arming") > Signed-off-by: Qingliang Li > --- $subject: Most recent convention used for this file is: "PM: sleep: wakeirq: ..." > drivers/base/power/wakeirq.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/base/power/wakeirq.c b/drivers/base/power/wakeirq.c > index 42171f766dcb..5a5a9e978e85 100644 > --- a/drivers/base/power/wakeirq.c > +++ b/drivers/base/power/wakeirq.c > @@ -313,8 +313,10 @@ void dev_pm_enable_wake_irq_complete(struct device *dev) > return; > > if (wirq->status & WAKE_IRQ_DEDICATED_MANAGED && > - wirq->status & WAKE_IRQ_DEDICATED_REVERSE) > + wirq->status & WAKE_IRQ_DEDICATED_REVERSE) { > enable_irq(wirq->irq); > + wirq->status |= WAKE_IRQ_DEDICATED_ENABLED; > + } But this does make sense to make sure status is updated, You can pick my R-by. Reviewed-by: Dhruva Gole -- Thanks and Regards, Dhruva Gole