Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp6635235rdb; Tue, 2 Jan 2024 08:11:07 -0800 (PST) X-Google-Smtp-Source: AGHT+IHDJHhA5tcynvOFRVIveJ83WwusmAzmi+InQvZH3ACM7eS3x7lwW5bUTeq9722ewtpRQ++Z X-Received: by 2002:a05:6a20:bd19:b0:194:f03c:edd7 with SMTP id fy25-20020a056a20bd1900b00194f03cedd7mr5601464pzb.41.1704211867028; Tue, 02 Jan 2024 08:11:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704211867; cv=none; d=google.com; s=arc-20160816; b=CaUbCZahK9QfeLl8yFVrq0HJz3KD8ao7q9jyZatLTyWS3NKfdl4+31hQNcNRpZSn1w skWAjs0+2M+xkx4xMQ4onugSU+cktOUetgE78imo/mi+QZO7iNpVPz7psRphWMnQ7fqb uOny7jmdJotqxxTO95XtpuzH7cq7zvAE4e3BKdv4Zjt/sroYgQmBVKgNpwMJz/fDGQZO ZkP9JPA94OZOJwo7b9AHcISsejY4Ka/pQOUaWYUwgMyxwAQhaBcAH3oqAtdAtYK2dWvR Rtza6LC9piTx8wwbH/59IA/S3XoxnapbIWvSbqxHBRKOMmP/8bAO2BXqazjrcLOs+dXe hlEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=PdemGKmsalkwPp7S8dpB0hmSz/O0OOnaCPceSYpkrTc=; fh=NcE9MJCAbFvzUZy33GyuOrZpwmYeKAMo4ZZBk5XjaIg=; b=IjmgHLaxyViuq3rwmmKHWpj36X+EJaOtq6p9iUb1V0YJupYsDTrlDrgzg4pUFpFuph CF3GHBgUpBrm+0CEfpSvpSBRih1sDuGKzoq9r96YWAdo7LSbxdUYclQQmZl7EX7xjLbR 8h9v/v7J4i9/OFRmdkmHuEyk4waW1PH9GmMti8TX9jRtWqUlVjjUdN/ouy2CxUYeTFap PWnuJcRrxdySzygZnokh332yti5FdhiCeaeDYXq+qncaPECiOkOldmZpyvZ421DPqkbT 1teomA9YqGGsH8fgzDGzbzBYGMdDSebdjwzREFfFd+AKZgnF3nwZi7Xd1bouMOfKCGvm Nu+A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=OWW+ktHL; spf=pass (google.com: domain of linux-kernel+bounces-14580-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-14580-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id u12-20020a6540cc000000b005c289c5cb5esi20200700pgp.762.2024.01.02.08.11.06 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Jan 2024 08:11:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-14580-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=OWW+ktHL; spf=pass (google.com: domain of linux-kernel+bounces-14580-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-14580-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org 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 sv.mirrors.kernel.org (Postfix) with ESMTPS id 0B2B7284ABA for ; Tue, 2 Jan 2024 16:01:58 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 7277C14F69; Tue, 2 Jan 2024 16:01:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="OWW+ktHL" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 A87C514F62; Tue, 2 Jan 2024 16:01:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0B0D1C433C8; Tue, 2 Jan 2024 16:01:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704211309; bh=EKxAVuaNMTNcXkXewVpa9TOANWnXDrtM+9hkMCPMgdE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=OWW+ktHLreDhaySNF6kc2W2X19bMnX5W/x4xA3aAqn+n1Lu/WvK3axum8q75CfhaP d+dat0RsiBA/JDB74ZmHmXpEXBVFW+o9iAhltvwvJm/vxvR8eSFIZqc07GrLrtjajC M51+uK1zT+xXefXgslZ9jQoKHdYBEIYs3kWd4cK6lG05ufhNkdiO5je23SmMTsAnM5 4Bd2X3wNw+zay0gfgcZH3YHgiklyj53AHC2iA/1PQMTmrmBuMkNgdg8R3w/pTqsa7d 6eQiSMAvzswZgRZsgbgwPl+WZK3oOCeQCd6m0bcd9byWe37qPVzntC5+A8CK1G9R9i 5SzO2FRWSZ9Eg== Received: (nullmailer pid 2924825 invoked by uid 1000); Tue, 02 Jan 2024 16:01:46 -0000 Date: Tue, 2 Jan 2024 09:01:46 -0700 From: Rob Herring To: Mark Hasemeyer Cc: Krzysztof Kozlowski , AngeloGioacchino Del Regno , Raul Rangel , Konrad Dybcio , Sudeep Holla , Frank Rowand , Andy Shevchenko , devicetree@vger.kernel.org, Rob Herring , LKML , Tzung-Bi Shih Subject: Re: [PATCH v3 18/24] of: irq: add wake capable bit to of_irq_resource() Message-ID: <170421130510.2924738.11783263909956971432.robh@kernel.org> References: <20231226192149.1830592-1-markhas@chromium.org> <20231226122113.v3.18.I29b26a7f3b80fac0a618707446a10b6cc974fdaf@changeid> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231226122113.v3.18.I29b26a7f3b80fac0a618707446a10b6cc974fdaf@changeid> On Tue, 26 Dec 2023 12:21:22 -0700, Mark Hasemeyer wrote: > Add wake capability information to the IRQ resource. Wake capability is > assumed based on conventions provided in the devicetree wakeup-source > binding documentation. An interrupt is considered wake capable if the > following are true: > 1. A wakeup-source property exits in the same device node as the > interrupt. > 2. The IRQ is marked as dedicated by setting its interrupt-name to > "wakeup". > > The wakeup-source documentation states that dedicated interrupts can use > device specific interrupt names and device drivers are still welcome to > use their own naming schemes. This API is provided as a helper if one is > willing to conform to the above conventions. > > The ACPI subsystems already provides similar APIs that allow one to > query the wake capability of an IRQ. This brings closer feature parity > to the devicetree. > > Signed-off-by: Mark Hasemeyer > --- > > Changes in v3: > -Use DEFINE_RES_IRQ_NAMED_FLAGS macro > > Changes in v2: > -Update logic to return true only if wakeup-source property and > "wakeup" interrupt-name are defined > -irq->IRQ, api->API > > drivers/of/irq.c | 39 +++++++++++++++++++++++++++++++++++---- > 1 file changed, 35 insertions(+), 4 deletions(-) > Reviewed-by: Rob Herring