Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp407542rdb; Thu, 21 Dec 2023 12:44:52 -0800 (PST) X-Google-Smtp-Source: AGHT+IEi/HGtR39JyxHx52DWwneMmRoQER7JGpXYVHUI34K+4RnVvEYb+fEPsAhnLGusemy3/CNX X-Received: by 2002:ad4:5de2:0:b0:67f:3c70:f714 with SMTP id jn2-20020ad45de2000000b0067f3c70f714mr346639qvb.115.1703191492439; Thu, 21 Dec 2023 12:44:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703191492; cv=none; d=google.com; s=arc-20160816; b=qfPPfM+S4v/jL+7AL/gOwm6R4pUUnE/S4P6HvVHMBqk+z2O3GS1q5yGaHQsChYu8tk TXKMFObtMRTVN3nrheHXNRNUqrxXJ5E/FSqireY/veWV5FcWqMvbcblbp9KywB53Wp2K 8KNm8CxCWXLVP4abFAnMeMj0BuNuw8inmX+JvPSkZWvjen0eqyfX0fWekDkvEk3+v9EN Kgnsdue7QV5G0M8ze3TyldRKW6jorzDvDPsfP+Jj/uMRr+ZFBDIBGicqNWB3gUGOMMHi X43efa2jw0Flv2RxKbKRSJatuhwIVercygO8wiLZbybimpwsVcRSgkxq/lpxQIUJSyfT cWIQ== 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=Irfuk/T1Xph4jwhhOkCGIGVSjW9gHNnoFXXH+k14A38=; fh=6y26jj6K83wQ9XwiMXNnmU5Lgly3+obTpAOK/dypqXw=; b=emv1dHIr+SPibdBnK4JXl6B2BnIBR89aC6QCVNvJcd23+okoDdqi1c8sNRXfct08BM yZp72Sli3NgBephCfIACrtjI6FnJnOQq4ZPbcGFx1NFi6v+jTPZGvY5v0LbFW3iE0qt7 11gDuDRd1ocd1acRdUmXtlMPC4TxtNnwlwOw6PsES8AvbSEbtXjdB25iq4Jqtb7cijgp gFkCC+JSVE5JutsPxVihx5Gz9iR+mulpCwLRrozZK7DR7/QMCBAHKPjOvK6OzuNteJVC vd5xdYsipnXHHEjo1u9KV0arZJdujAKu79nvtMGidcTag3zhCCfQD0Jpetp9GbQgnLkS 3a7g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=ThAR0Zp2; spf=pass (google.com: domain of linux-kernel+bounces-9059-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-9059-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id b7-20020a0cb3c7000000b0067eaa22160bsi2849710qvf.530.2023.12.21.12.44.52 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Dec 2023 12:44:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-9059-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=ThAR0Zp2; spf=pass (google.com: domain of linux-kernel+bounces-9059-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-9059-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 ny.mirrors.kernel.org (Postfix) with ESMTPS id 33D351C22FCA for ; Thu, 21 Dec 2023 20:44:52 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 337BB76918; Thu, 21 Dec 2023 20:44:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ThAR0Zp2" 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 61F3A760B8; Thu, 21 Dec 2023 20:44:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D1B51C433C8; Thu, 21 Dec 2023 20:44:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703191483; bh=C4ND45O9VtPdCGNJbKtbMUJR3Ewk4KrDe0AszFJgI1g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ThAR0Zp2s0BlXasxoqe33EdMx7uI1VwY7bMLPoQWjvgdLlZLx6FC7vKTSQ36Oweg7 FwHF1Egu0a+Sbchnw8lN6yK1zN3YTNdreVvWzLygo8ZSP9iJL4T1E0Kz1xi+mlXgxq 3ydHgZM6fQhaWXwO4leH2bLvTcjbv1s1F1mRFqNWP/mceguB7ZPUvrNiCDfuHI8uR0 IVbjUjlXGqG0GtvJfQwMn04i+djj0nxNNpfyzG1mOYa7y05GCjOfjplLrKrelHqF8j amA3kEgvreefhUeG/sEBnHg0sUqp2cufG8hZZBBY5Jrn6iM56koQtUpr+k/O9McPfZ Yjqx5JudQPJ/A== Received: (nullmailer pid 62496 invoked by uid 1000); Thu, 21 Dec 2023 20:44:41 -0000 Date: Thu, 21 Dec 2023 14:44:41 -0600 From: Rob Herring To: Mark Hasemeyer Cc: Krzysztof Kozlowski , Raul Rangel , Frank Rowand , devicetree@vger.kernel.org, Rob Herring , AngeloGioacchino Del Regno , Andy Shevchenko , Tzung-Bi Shih , Sudeep Holla , Konrad Dybcio , LKML Subject: Re: [PATCH v2 17/22] of: irq: add wake capable bit to of_irq_resource() Message-ID: <170319148087.62439.16254774276035197827.robh@kernel.org> References: <20231220235459.2965548-1-markhas@chromium.org> <20231220165423.v2.17.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: <20231220165423.v2.17.I29b26a7f3b80fac0a618707446a10b6cc974fdaf@changeid> On Wed, 20 Dec 2023 16:54:31 -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 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 | 32 +++++++++++++++++++++++++++++++- > 1 file changed, 31 insertions(+), 1 deletion(-) > Reviewed-by: Rob Herring