Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp5876831rwn; Mon, 12 Sep 2022 16:15:09 -0700 (PDT) X-Google-Smtp-Source: AA6agR6bgbtIJ1hHe55f+E01KtOO1deJIMJBid6CTS25t+wzESS3A/lz8U0Y05gjt5b5Ma7OW3R4 X-Received: by 2002:a65:5b4c:0:b0:439:b3a:e8e6 with SMTP id y12-20020a655b4c000000b004390b3ae8e6mr5725808pgr.330.1663024509072; Mon, 12 Sep 2022 16:15:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663024509; cv=none; d=google.com; s=arc-20160816; b=qWvVvEBlbE+7K7AMQkMkBcJ8OIHmozYNnL71UXTpq5S+NVTyaJFz2r/94tL9a7jk+1 qFcu0tLMEZpJf2AF/GynLE+a+xXzwR7cYztR0Xs1WVGeOEyu4KOdVHVyYDfiG26nzShB OdZPVzUTE+ot+csNigMOpB6HU+f/ePj02aqpqBOW1GdB3j7sIjX2R44jYDo9fDa3hxbI FYnFawlAHaRQ/CMbr/04x0bq5eB+1wR13JhYVK1xKYkBp+6jiVVmuZXdfGGHckCfzqB1 mZmZ51nJhlMpp08oI0GKItSl9l8ascaunzUdfZm3RpmghkXiDj0kCwapGUSc91983/Ca Jq3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=WtBz2ZjAbdVsCXaJ14UBh6dPKQNQTEXbXV+WGkY+jwg=; b=bRQdJfyym4yai+zzjFOe/DkD3gzLddW5hkXbEYH70K5awgdviKNwFTIkuJNzlQUmpq 166dbKy9jhOxe9Mohcj8l357HyMVkL/mJpZW9NeVlhnt6XwI65jEHXsNEWYYZBqajYHn 8eWryGqXUNOSQvVZLhgQiNq0gh1Z+U5dQ/CXnvyaJrdE4Rf9H14Li3RV5WdxBf29uqh0 jvVOfUB7C7pZdbXCVRWswX4eL7ltWYsdbM5pyfYONefbyACL7p0nCCygYal+CD7n3z8D h/d4xJ/b3q01vbi6GEfsMjAiG4IejhbzJuSOmb2yWznAXom7H3oWcDEHy5I0sKjwngnX Glgg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=nfBNhUl+; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id qb16-20020a17090b281000b001fdb6cfb4c2si9700270pjb.26.2022.09.12.16.14.56; Mon, 12 Sep 2022 16:15:09 -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=@chromium.org header.s=google header.b=nfBNhUl+; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229915AbiILWNp (ORCPT + 99 others); Mon, 12 Sep 2022 18:13:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33874 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229945AbiILWNn (ORCPT ); Mon, 12 Sep 2022 18:13:43 -0400 Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 86A644DB6F for ; Mon, 12 Sep 2022 15:13:40 -0700 (PDT) Received: by mail-il1-x132.google.com with SMTP id k9so5281488ils.12 for ; Mon, 12 Sep 2022 15:13:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date; bh=WtBz2ZjAbdVsCXaJ14UBh6dPKQNQTEXbXV+WGkY+jwg=; b=nfBNhUl+5qqTsJR9FKSY2gYY9fcN0IrZCSEpHl+lpRb/6P9ffCToyjYvaHnUQTneH2 0s6d7JIfEG3LJ2CuHlrfcg2lwaYvYAXOm+BfilrDAIFQDpaecYlgWf9V3OvQSIJ7hub2 bCLpWIF4W6FmS40ggFgGwjD1YL2JGLpYRqHK4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date; bh=WtBz2ZjAbdVsCXaJ14UBh6dPKQNQTEXbXV+WGkY+jwg=; b=G1XevptlLx7S8RG+wLDcSvip13C+UFyIGVmKEiwwoR4saTci+77mf6dH5xxClf/j38 iWS4UivyoWijgQKL2ziWh9GaW+12fQ/1gYPCVpzhzJSWowOE6pMXWbnfVwJPmYasEmo7 fdnomdnrR186DZ6P2H+S8G+w2Mh/z73oJROf597XQBtHjIUo7E5MGmXjwYwa0ocHdW1p bhcDMVS8Y+PZRPUkapdBtTVj0038VJlghoiFJ0ri/hMhep9nVD3p9pcsWWfdjFmOOL0y ziE+RWUOE7fSKV45CuaTLVzif324CT5rlBl7b2D1GwroIRrXTRaRRwXNwMPHTWXyEZPg rPig== X-Gm-Message-State: ACgBeo33kbZMnddn3RxV2WnlVzjlIDYdh4BlCHxHDXMZasX0sVogtULm 7HPUlqv7uEvJYSuofMaZBS5LpA== X-Received: by 2002:a05:6e02:214b:b0:2ec:f24f:5272 with SMTP id d11-20020a056e02214b00b002ecf24f5272mr11230667ilv.169.1663020819876; Mon, 12 Sep 2022 15:13:39 -0700 (PDT) Received: from rrangel920.bld.corp.google.com (h24-56-189-219.arvdco.broadband.dynamic.tds.net. [24.56.189.219]) by smtp.gmail.com with ESMTPSA id 18-20020a056e020cb200b002f16e7021f6sm4077334ilg.22.2022.09.12.15.13.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Sep 2022 15:13:38 -0700 (PDT) From: Raul E Rangel To: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org Cc: andriy.shevchenko@linux.intel.com, jingle.wu@emc.com.tw, mario.limonciello@amd.com, timvp@google.com, linus.walleij@linaro.org, hdegoede@redhat.com, rafael@kernel.org, Raul E Rangel , Alistair Francis , Angela Czubak , Asmaa Mnebhi , Bartosz Golaszewski , Bartosz Szczepanek , Benjamin Tissoires , Cai Huoqing , Dan Williams , "David S. Miller" , David Thompson , Dmitry Torokhov , Eric Dumazet , Greg Kroah-Hartman , Guenter Roeck , Jakub Kicinski , Jiri Kosina , Johnny Chuang , Jonathan Cameron , Len Brown , Lu Wei , Matthias Kaehlcke , Mika Westerberg , Paolo Abeni , Rob Herring , Terry Bowman , Wolfram Sang , linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: [PATCH v2 00/13] acpi: i2c: Use SharedAndWake and ExclusiveAndWake to enable wake irq Date: Mon, 12 Sep 2022 16:13:04 -0600 Message-Id: <20220912221317.2775651-1-rrangel@chromium.org> X-Mailer: git-send-email 2.37.2.789.g6183377224-goog MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Today, i2c drivers are making the assumption that their IRQs can also be used as wake IRQs. This isn't always the case and it can lead to spurious wakes. This has recently started to affect AMD Chromebooks. With the introduction of d62bd5ce12d7 ("pinctrl: amd: Implement irq_set_wake"), the AMD GPIO controller gained the capability to set the wake bit on each GPIO. The ACPI specification defines two ways to inform the system if a device is wake capable: 1) The _PRW object defines the GPE that can be used to wake the system. 2) Setting ExclusiveAndWake or SharedAndWake in the _CRS GpioInt. Currently only the first method is supported. The i2c drivers don't have any indication that the IRQ is wake capable, so they guess. This causes spurious interrupts, for example: * We have an ACPI HID device that has `_PR0` and `_PR3`. It doesn't have `_PRW` or `ExclusiveAndWake` so that means the device can't wake the system. * The IRQ line is active level low for this device and is pulled up by the power resource defined in `_PR0`/`_PR3`. * The i2c driver will (incorrectly) arm the GPIO for wake by calling `enable_irq_wake` as part of its suspend hook. * ACPI will power down the device since it doesn't have a wake GPE associated with it. * When the device is powered down, the IRQ line will drop, and it will trigger a wake event. See the following debug log: [ 42.335804] PM: Suspending system (s2idle) [ 42.340186] amd_gpio AMD0030:00: RX: Setting wake for pin 89 to enable [ 42.467736] power-0416 __acpi_power_off : Power resource [PR00] turned off [ 42.467739] device_pm-0280 device_set_power : Device [H05D] transitioned to D3cold [ 42.475210] PM: pm_system_irq_wakeup: 11 triggered pinctrl_amd [ 42.535293] PM: Wakeup unrelated to ACPI SCI [ 42.535294] PM: resume from suspend-to-idle In order to fix this, we need to take into account the wake capable bit defined on the Interrupt/GpioInt. This is accomplished by: * Migrating some of the i2c drivers over to using the PM subsystem to manage the wake IRQ. * Expose the wake_capable bit from the ACPI Interrupt/GpioInt resource to the i2c core. * Use the wake_capable bit in the i2c core to call `dev_pm_set_wake_irq`. This reuses the existing device tree flow. * Make the i2c drivers stop calling `dev_pm_set_wake_irq` since it's now handled by the i2c core. * Make the ACPI device PM system aware of the wake_irq. This is necessary so the device doesn't incorrectly get powered down when a wake_irq is enabled. I've tested this code with various combinations of having _PRW, ExclusiveAndWake and power resources all defined or not defined, but it would be great if others could test this out on their hardware. I'm sure this will surface some devices where the IRQs were not correctly marked as wake capable. Ideally the firmware can be fixed, but if not we can work around this in the kernel by providing a board specific `struct i2c_board_info` with the `I2C_CLIENT_WAKE` flag set. See `chromeos_laptop.c` for an example of matching DMI properties and setting the `I2C_CLIENT_WAKE` override. Thanks, Raul Changes in v2: - Added elants_i2c to series - Added raydium_ts_i2c to series - Fixed call site in mlxbf_gige_probe - Added ability to extract wake bit from Interrupt/IRQ resources - Look at wake_cabple bit for IRQ/Interrupt resources - I chose not to keep the legacy code around since systems without DT or ACPI should be rare. Raul E Rangel (13): HID: i2c-hid: Use PM subsystem to manage wake irq Input: elan_i2c - Use PM subsystem to manage wake irq Input: elants_i2c - Use PM subsystem to manage wake irq Input: raydium_ts_i2c - Use PM subsystem to manage wake irq gpiolib: acpi: Add wake_capable parameter to acpi_dev_gpio_irq_get_by ACPI: resources: Add wake_capable parameter to acpi_dev_irq_flags i2c: acpi: Use ACPI wake capability bit to set wake_irq ACPI: PM: Take wake IRQ into consideration when entering suspend-to-idle HID: i2c-hid: acpi: Stop setting wakeup_capable HID: i2c-hid: Don't set wake_capable and wake_irq Input: elan_i2c - Don't set wake_capable and wake_irq Input: elants_i2c - Don't set wake_capable and wake_irq Input: raydium_ts_i2c - Don't set wake_capable and wake_irq drivers/acpi/device_pm.c | 19 +++++++++- drivers/acpi/irq.c | 11 ++++-- drivers/acpi/resource.c | 24 ++++++++---- drivers/gpio/gpio-pca953x.c | 3 +- drivers/gpio/gpiolib-acpi.c | 11 +++++- drivers/gpio/gpiolib-acpi.h | 2 + drivers/hid/i2c-hid/i2c-hid-acpi.c | 5 --- drivers/hid/i2c-hid/i2c-hid-core.c | 24 ++---------- drivers/i2c/i2c-core-acpi.c | 37 ++++++++++++++----- drivers/i2c/i2c-core-base.c | 6 ++- drivers/i2c/i2c-core.h | 4 +- drivers/input/mouse/elan_i2c_core.c | 15 +------- drivers/input/touchscreen/elants_i2c.c | 13 +------ drivers/input/touchscreen/raydium_i2c_ts.c | 7 +--- .../mellanox/mlxbf_gige/mlxbf_gige_main.c | 3 +- drivers/pnp/pnpacpi/rsparser.c | 9 +++-- include/linux/acpi.h | 17 +++++++-- include/linux/ioport.h | 3 +- 18 files changed, 121 insertions(+), 92 deletions(-) -- 2.37.2.789.g6183377224-goog