Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp1162142rwl; Fri, 24 Mar 2023 07:06:17 -0700 (PDT) X-Google-Smtp-Source: AKy350bFX0KtqdlblRdg4UTFMZ4N8kWvAb0G+iX/PrJ4z8aTrD8rIAPIMRNaTSUmKdqXSNSFsHJz X-Received: by 2002:a17:906:806:b0:8b1:7841:9f28 with SMTP id e6-20020a170906080600b008b178419f28mr2940955ejd.55.1679666776867; Fri, 24 Mar 2023 07:06:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679666776; cv=none; d=google.com; s=arc-20160816; b=SQ1bPri/YKHcIPW5af8QEeWq5e3gmrMWn5sNoMBBA7fgdjp5S/G3wW0UvIqu8+Clwc XaHRK+w+rI+zofar2lAA6OVZhBb+7CnY27brhiCIimbqG588N0aLqK2jjJR1vVCtz2RK h/5o2M5FqJnugA7/Zn+4i28BvDB5yJCfO+39R3/XqgMyd+Vw4t6e5dh+xGd2qioUEAql EhKn2WxRApH7oWh3/JU92wxMTLqgHMJmWpL+Z2XZnSgHCkdXb5Cz5n0ZGWXG8YhXZfLj jrh0mIw0YMsVQFkKw5Nd1PB3VBJa82LuwQs7S8tIR9uA1Wuena04wdDT0U89zNv4zuV4 tluQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=PnbpfcqGanbrwxTimMfIRYuXDJDuBG+s0gPnBVVk/Bo=; b=TlrBiAdkVg9wM8BAxhLQ/Xya93K+lw5ZexYZSKqeOd67wVtk2TQEfKADdExCPxp0qj ABkJLnHQSgvXSIeZ53sQei/pDFU3SKFOWhl+xdelXwn3gXsrkC8eIpD3wyJLQeYlOCv8 5K+dSIHgtHaE+2/EKooDHD8sOYNVkL0k7FC+M6WTuwWulT5UJkgz8RCW1BEdEdaYBAGX ZT0Za2yOVudCDZOOMdR3UE90phPUUNZW5yCSuUHyy+XZrkuSpTVMLxveUfJxliMUodaO S4Nc3HQ1wVdp5pBkX4w/w2CVe/m9N40VyLtRY04JvGXX73mSPPXTYCesyjcgMhMNqZgP BLGQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20210112.gappssmtp.com header.s=20210112 header.b=vHBto2XQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id dm5-20020a170907948500b0093e4b4e40c5si1767147ejc.996.2023.03.24.07.05.33; Fri, 24 Mar 2023 07:06:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@bgdev-pl.20210112.gappssmtp.com header.s=20210112 header.b=vHBto2XQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232178AbjCXOEo (ORCPT + 99 others); Fri, 24 Mar 2023 10:04:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54436 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232160AbjCXOER (ORCPT ); Fri, 24 Mar 2023 10:04:17 -0400 Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7F1B815CB1 for ; Fri, 24 Mar 2023 07:03:19 -0700 (PDT) Received: by mail-ua1-x92a.google.com with SMTP id v48so1463896uad.6 for ; Fri, 24 Mar 2023 07:03:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20210112.gappssmtp.com; s=20210112; t=1679666590; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=PnbpfcqGanbrwxTimMfIRYuXDJDuBG+s0gPnBVVk/Bo=; b=vHBto2XQMyBoDyv2V3lWV93YknLET2STEkfA7BDeD0Rib/Bfn9J/fWb2Ikjp1f+TuE TJpJR1VryraL97ejyEKLYhaYXWaEzKTVZ4B5fA5fXspfeiCFjpX1GheQOvw1+qoaX1zN P7B0fsSpK0OV4Neu8d1gEnVoKPkHKcZDKAeqyz1G4UEv5CdQaN0MvHzPT3jGwDcuIt/K PS7bOPrJ+HgAXeBSYTywBwveDk93HLiiGJc6mI3pb7iP3ZcucuJcbhNYb8Xw/cUYkOGv DAp9Gw3TQddBAz4EfEnKG1f2xq+PyZOJv5Yrjv8Z7MdWU+blpCox61DdDcatzW9+3lEr ydMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679666590; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=PnbpfcqGanbrwxTimMfIRYuXDJDuBG+s0gPnBVVk/Bo=; b=xE0uKXRIzYz2t8HMC4K8uxwGtPDG3EIRrfgaUJUnfwk7oqV+Nk0poq6X/h1BSpAKuH gQ9DKWMemx4Vk/i4wRh5Q2O5Dyg94a/JJZQhn7A8LBieWRCG+9jPhxArydo3fFgd/BwO T+dDRTMR3TG+vCZowUnAq+MZmMh3lR1mBq1BcB4dCONOSuxHTs8g+bdPia97vVajj13s msOJPXl+kWBgDalpPSMF6VPmk9yKrTg6PnXCld+n7p5zVZBsdl2bjMjbfOzRRHOXYr5/ l2ju05T6D/yJe3z13ts2yCDZeEcuZmHZzm8cjKcaeEJM+3W1ojpjs1BvM8IH+yWoNCG9 +2cA== X-Gm-Message-State: AO0yUKW1h2YZTNh43kgVDCvDGeCN5601fIJOrap5COkk0E70OGmkTqmD NY0KLKW+gZvIMcyKS/ANR/3IOB2OSGj6gFRVYO1DNw== X-Received: by 2002:a05:6122:11af:b0:401:d1f4:bccf with SMTP id y15-20020a05612211af00b00401d1f4bccfmr5291512vkn.0.1679666590340; Fri, 24 Mar 2023 07:03:10 -0700 (PDT) MIME-Version: 1.0 References: <20230322121547.14997-1-wse@tuxedocomputers.com> In-Reply-To: <20230322121547.14997-1-wse@tuxedocomputers.com> From: Bartosz Golaszewski Date: Fri, 24 Mar 2023 15:02:59 +0100 Message-ID: Subject: Re: [PATCH] gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xNU To: Werner Sembach Cc: Mika Westerberg , Andy Shevchenko , Linus Walleij , linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 22, 2023 at 1:16=E2=80=AFPM Werner Sembach wrote: > > commit 1796f808e4bb ("HID: i2c-hid: acpi: Stop setting wakeup_capable") > changed the policy such that I2C touchpads may be able to wake up the > system by default if the system is configured as such. > > However on Clevo NL5xNU there is a mistake in the ACPI tables that the > TP_ATTN# signal connected to GPIO 9 is configured as ActiveLow and level > triggered but connected to a pull up. As soon as the system suspends the > touchpad loses power and then the system wakes up. > > To avoid this problem, introduce a quirk for this model that will prevent > the wakeup capability for being set for GPIO 9. > > This patch is analoge to a very similar patch for NL5xRU, just the DMI > string changed. > > Signed-off-by: Werner Sembach > Cc: stable@vger.kernel.org > --- > drivers/gpio/gpiolib-acpi.c | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c > index 34ff048e70d0e..055013f959b25 100644 > --- a/drivers/gpio/gpiolib-acpi.c > +++ b/drivers/gpio/gpiolib-acpi.c > @@ -1624,6 +1624,19 @@ static const struct dmi_system_id gpiolib_acpi_qui= rks[] __initconst =3D { > .ignore_interrupt =3D "AMDI0030:00@18", > }, > }, > + { > + /* > + * Spurious wakeups from TP_ATTN# pin > + * Found in BIOS 1.7.8 > + * https://gitlab.freedesktop.org/drm/amd/-/issues/1722#n= ote_1720627 > + */ > + .matches =3D { > + DMI_MATCH(DMI_BOARD_NAME, "NL5xNU"), > + }, > + .driver_data =3D &(struct acpi_gpiolib_dmi_quirk) { > + .ignore_wake =3D "ELAN0415:00@9", > + }, > + }, > { > /* > * Spurious wakeups from TP_ATTN# pin > -- > 2.34.1 > Queued for fixes. Bart