Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp1015468ybv; Fri, 7 Feb 2020 12:42:59 -0800 (PST) X-Google-Smtp-Source: APXvYqyM0YNqyHuaq9ghb7tH469Ojj4sAu8ZBBKpzUzEl4kiKv+R+jerDsjhh9Bd9LuaWeF/pbPo X-Received: by 2002:a05:6830:1353:: with SMTP id r19mr985445otq.288.1581108179164; Fri, 07 Feb 2020 12:42:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581108179; cv=none; d=google.com; s=arc-20160816; b=osZ7Rlg2c6teBHzgy4ZKbTFaLLt7p+WHGEW2kiHqZ+jkOm1XF5NmQihnQMQ6PzLG/7 yH7ZuQ6hNPzMz4OkX5M8IDm4O1fYCAm4pmddMuYPPdTk5rcPuaiiyjFyCzpn4+629z2m Bbl7KUn3ql7xLlL+irXBa0VkhQin8Nt3nl81G2jJ28fY3p6dO4ZExManzYnaci9YzjqE Sqs5oNjGnZzKhcVum83YSaQ+CUwG6F35HTfyx7TuNHaYjYS4g+VVHE4pPBtX2sZLkt7+ 8io9bDmHHYEg5PMwGqVrISzZzoKOM/nvn0/+Is4QG7eOLqSE633iBpNwP0WJBGoQx+3a HCIg== 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 :robot-unsubscribe:robot-id:message-id:mime-version:references :in-reply-to:cc:subject:to:reply-to:from:date; bh=FtlWqkKXRlKfx5GKnrxzX5u9DSX2kR7XU38SIBHy8Wk=; b=NxjNC07KLdTi69SGYPzIVe1HyYbJkFjCWvEHAWLC1yi6jUobZ43NKR2aM0C/un3fGT oTjACVfRsukpupWzBHhVeNSEC2FZkQ64irLPERrm5ukjIusJNqxbtbpUlVdXwX1ckR8E xq54UUZsR28ip6dkhNCdlsyHg2Owji2DrYukl4M9m2vro1k+PXH5yha7JspnAJmfnhPn dPtPaG2mt51ERHO2trhL6pRb/K6FwvyHJdEz9e5aQ3RZQAMEJ/9/McQr4AEINOAMfuij vP4XmS9fmfUCbHmg/up9pKe7tJdm5/dGshl9ko5r72LhEL9xOZSS4jFNZ4VOs/neks49 lbRg== ARC-Authentication-Results: i=1; mx.google.com; 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 s15si4367274oih.252.2020.02.07.12.42.46; Fri, 07 Feb 2020 12:42:59 -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; 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 S1727507AbgBGUk6 (ORCPT + 99 others); Fri, 7 Feb 2020 15:40:58 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:41560 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726947AbgBGUk6 (ORCPT ); Fri, 7 Feb 2020 15:40:58 -0500 Received: from [5.158.153.53] (helo=tip-bot2.lab.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1j0AQo-0002F4-Qb; Fri, 07 Feb 2020 21:40:54 +0100 Received: from [127.0.1.1] (localhost [IPv6:::1]) by tip-bot2.lab.linutronix.de (Postfix) with ESMTP id 040321C1EEE; Fri, 7 Feb 2020 21:40:54 +0100 (CET) Date: Fri, 07 Feb 2020 20:40:53 -0000 From: "tip-bot2 for Stephen Boyd" Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: irq/urgent] genirq: Clarify that irq wake state is orthogonal to enable/disable Cc: Stephen Boyd , Thomas Gleixner , Douglas Anderson , x86 , LKML In-Reply-To: <20200206191521.94559-1-swboyd@chromium.org> References: <20200206191521.94559-1-swboyd@chromium.org> MIME-Version: 1.0 Message-ID: <158110805373.411.379070256193790267.tip-bot2@tip-bot2> X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following commit has been merged into the irq/urgent branch of tip: Commit-ID: f9f21cea311340f38074ff93a8d89b4a9cae6bcc Gitweb: https://git.kernel.org/tip/f9f21cea311340f38074ff93a8d89b4a9cae6bcc Author: Stephen Boyd AuthorDate: Thu, 06 Feb 2020 11:15:21 -08:00 Committer: Thomas Gleixner CommitterDate: Fri, 07 Feb 2020 21:37:08 +01:00 genirq: Clarify that irq wake state is orthogonal to enable/disable There's some confusion around if an irq that's disabled with disable_irq() can still wake the system from sleep states such as "suspend to RAM". Clarify this in the kernel documentation for irq_set_irq_wake() so that it's clear that an irq can be disabled and still wake the system if it has been marked for wakeup. Signed-off-by: Stephen Boyd Signed-off-by: Thomas Gleixner Reviewed-by: Douglas Anderson Link: https://lkml.kernel.org/r/20200206191521.94559-1-swboyd@chromium.org --- kernel/irq/manage.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c index 818b280..3089a60 100644 --- a/kernel/irq/manage.c +++ b/kernel/irq/manage.c @@ -731,6 +731,13 @@ static int set_irq_wake_real(unsigned int irq, unsigned int on) * * Wakeup mode lets this IRQ wake the system from sleep * states like "suspend to RAM". + * + * Note: irq enable/disable state is completely orthogonal + * to the enable/disable state of irq wake. An irq can be + * disabled with disable_irq() and still wake the system as + * long as the irq has wake enabled. If this does not hold, + * then the underlying irq chip and the related driver need + * to be investigated. */ int irq_set_irq_wake(unsigned int irq, unsigned int on) {