From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C6065C6FA86 for ; Thu, 15 Sep 2022 10:43:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229738AbiIOKnn (ORCPT ); Thu, 15 Sep 2022 06:43:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49662 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229497AbiIOKnm (ORCPT ); Thu, 15 Sep 2022 06:43:42 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89BF958DCE; Thu, 15 Sep 2022 03:43:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663238620; x=1694774620; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wLWgR64O2sMHHi4b8YpQoNd7rQDRs8Hs5xyjBuOfPko=; b=mdalCxHl3qLFn7p3gofcLV9SZQHcVV2Lj37cQCBRXdM+PyeSO5l/KtH8 FqEspZKgB/6eod178qrPtSMM1XjMNOejny5gch+TF8Eib40d79vEe/f8H Dx/3sPwNALQT3T6Txc+MXCeNT/OL9afw/CXk8eOcberxBb3SA1McUl1vh CKnB4TrTtW3Quua4OZP6hJCKG5AITJqssQo1VGaHZk+ZlUiIoNteP/Pgv cFkRDDO2iI+wv5rQfV5CSRYdPnDMcY21qY0sUf82boejXqJOb1xinJgYh X5JpyZxlsQwI2c6TedYOfscI420xdz/I2WCGNfrXaHawjzP4oppS01MTy g==; X-IronPort-AV: E=McAfee;i="6500,9779,10470"; a="362638027" X-IronPort-AV: E=Sophos;i="5.93,317,1654585200"; d="scan'208";a="362638027" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Sep 2022 03:43:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.93,317,1654585200"; d="scan'208";a="647779489" Received: from black.fi.intel.com ([10.237.72.28]) by orsmga008.jf.intel.com with ESMTP; 15 Sep 2022 03:43:36 -0700 Received: by black.fi.intel.com (Postfix, from userid 1001) id 1CE3F235; Thu, 15 Sep 2022 13:43:52 +0300 (EEST) Date: Thu, 15 Sep 2022 13:43:52 +0300 From: Mika Westerberg To: Raul E Rangel Cc: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org, jingle.wu@emc.com.tw, rafael@kernel.org, andriy.shevchenko@linux.intel.com, mario.limonciello@amd.com, hdegoede@redhat.com, linus.walleij@linaro.org, timvp@google.com, dmitry.torokhov@gmail.com, Bartosz Golaszewski , Len Brown , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 05/13] gpiolib: acpi: Add wake_capable variants of acpi_dev_gpio_irq_get Message-ID: References: <20220914235801.1731478-1-rrangel@chromium.org> <20220914155914.v3.5.I4ff95ba7e884a486d7814ee888bf864be2ebdef4@changeid> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220914155914.v3.5.I4ff95ba7e884a486d7814ee888bf864be2ebdef4@changeid> Precedence: bulk List-ID: X-Mailing-List: linux-input@vger.kernel.org On Wed, Sep 14, 2022 at 05:57:53PM -0600, Raul E Rangel wrote: > The ACPI spec defines the SharedAndWake and ExclusiveAndWake share type > keywords. This is an indication that the GPIO IRQ can also be used as a > wake source. This change exposes the wake_capable bit so drivers can > correctly enable wake functionality instead of making an assumption. > > Signed-off-by: Raul E Rangel Reviewed-by: Mika Westerberg