From patchwork Tue Nov 24 17:47:19 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Doug Anderson X-Patchwork-Id: 332541 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-18.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER, INCLUDES_PATCH, MAILING_LIST_MULTI, SPF_HELO_NONE, SPF_PASS, URIBL_BLOCKED, USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5DBEDC2D0E4 for ; Tue, 24 Nov 2020 17:48:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 043972087C for ; Tue, 24 Nov 2020 17:48:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="PuNaFOUD" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2403909AbgKXRrs (ORCPT ); Tue, 24 Nov 2020 12:47:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403958AbgKXRrq (ORCPT ); Tue, 24 Nov 2020 12:47:46 -0500 Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DCAA2C0613D6 for ; Tue, 24 Nov 2020 09:47:44 -0800 (PST) Received: by mail-pf1-x441.google.com with SMTP id q10so19239969pfn.0 for ; Tue, 24 Nov 2020 09:47:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=8ckt5NlFQBUj9ad7Wcfnzxmq4bS87/8gcDcZUE4/+ro=; b=PuNaFOUDQZ0VIxY0XaAbtfd5SDpQK9q04/AaC1rPeDrPSW0yP8HpXqIEpt1foMV/oZ acqddNjTYpYjz8E1ABr/T1xxKkisF8YQMgh7Do4VcCJ9MqRQzxvpQjKt984jxMK2N1Ik TkgrOAosOxTyzdpiK/sbdu5uZrvWO5Tv20GoQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=8ckt5NlFQBUj9ad7Wcfnzxmq4bS87/8gcDcZUE4/+ro=; b=BwJZpXoOq8CVUJsepHOq5zPCVbTXHD5/sI7Gcn4FBForvhTY6xwKgfdle17GtuoJcy +FNxrn7ovKV4n/R+yqjR+Xw8Dmppm0xuyVIPyxbcAAG7Y0Uq5SAjBIWxUarjUKZcTfQR PNAxRRDqfnmzEFnmItWqMnbdXW9wzQlR6R2EF7kXIOPBYsl1JcCF2iD1E67jT7IlF3eQ 1dKwvjnNxDAXeofj9BBLXPSS7QbKQm4hszxkLk50BscC2jQFvFolN72iwVEiQjrcrA8Q OnP+H1uR7MyLs4zVzfYQ6SAeU4Bzgw/akDpl2F2Lz2TgZxMhrZaGpSKlJuLmrzVyHx1q BBsQ== X-Gm-Message-State: AOAM531lH9HfFHZYk8AwpGiZYeFQCxtpQGUgGkFXsJ9YATucR25gfrem /oxLofWBO9lhgblfkvOQY64M8w== X-Google-Smtp-Source: ABdhPJwoLRiT+KykvFRT+U8sBkabFveCDhERGqz1LJCJk2ftAle9VsTy6P52AxNwRMydIWiUKQQz0A== X-Received: by 2002:a63:34c:: with SMTP id 73mr4524428pgd.172.1606240064368; Tue, 24 Nov 2020 09:47:44 -0800 (PST) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:42b0:34ff:fe3d:58e6]) by smtp.gmail.com with ESMTPSA id i4sm13480459pgg.67.2020.11.24.09.47.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Nov 2020 09:47:43 -0800 (PST) From: Douglas Anderson To: Marc Zyngier , Thomas Gleixner , Jason Cooper , Linus Walleij Cc: linux-gpio@vger.kernel.org, Neeraj Upadhyay , Stephen Boyd , Bjorn Andersson , Srinivas Ramana , linux-arm-msm@vger.kernel.org, Maulik Shah , Rajendra Nayak , Douglas Anderson , Andy Gross , Archana Sathyakumar , Lina Iyer , linux-kernel@vger.kernel.org Subject: [PATCH v2 1/3] irqchip: qcom-pdc: Fix phantom irq when changing between rising/falling Date: Tue, 24 Nov 2020 09:47:19 -0800 Message-Id: <20201124094636.v2.1.I2702919afc253e2a451bebc3b701b462b2d22344@changeid> X-Mailer: git-send-email 2.29.2.454.gaff20da3a2-goog MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org We have a problem if we use gpio-keys and configure wakeups such that we only want one edge to wake us up. AKA: wakeup-event-action = ; wakeup-source; Specifically we end up with a phantom interrupt that blocks suspend if the line was already high and we want wakeups on rising edges (AKA we want the GPIO to go low and then high again before we wake up). The opposite is also problematic. Specifically, here's what's happening today: 1. Normally, gpio-keys configures to look for both edges. Due to the current workaround introduced in commit c3c0c2e18d94 ("pinctrl: qcom: Handle broken/missing PDC dual edge IRQs on sc7180"), if the line was high we'd configure for falling edges. 2. At suspend time, we change to look for rising edges. 3. After qcom_pdc_gic_set_type() runs, we get a phantom interrupt. We can solve this by just clearing the phantom interrupt. NOTE: it is possible that this could cause problems for a client with very specific needs, but there's not much we can do with this hardware. As an example, let's say the interrupt signal is currently high and the client is looking for falling edges. The client now changes to look for rising edges. The client could possibly expect that if the line has a short pulse low (and back high) that it would always be detected. Specifically no matter when the pulse happened, it should either have tripped the (old) falling edge trigger or the (new) rising edge trigger. We will simply not trip it. We could narrow down the race a bit by polling our parent before changing types, but no matter what we do there will still be a period of time where we can't tell the difference between a real transition (or more than one transition) and the phantom. Fixes: f55c73aef890 ("irqchip/pdc: Add PDC interrupt controller for QCOM SoCs") Signed-off-by: Douglas Anderson Reviewed-by: Maulik Shah Tested-by: Maulik Shah --- There are no dependencies between this patch and patch #2/#3. It can go in by itself. Patches are only grouped together in one series because they address similar issues. Changes in v2: - 0 => false - If irq_chip_set_type_parent() fails don't bother clearing. - Add Fixes tag. drivers/irqchip/qcom-pdc.c | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/drivers/irqchip/qcom-pdc.c b/drivers/irqchip/qcom-pdc.c index bd39e9de6ecf..f91e7d5aea25 100644 --- a/drivers/irqchip/qcom-pdc.c +++ b/drivers/irqchip/qcom-pdc.c @@ -159,6 +159,8 @@ static int qcom_pdc_gic_set_type(struct irq_data *d, unsigned int type) { int pin_out = d->hwirq; enum pdc_irq_config_bits pdc_type; + enum pdc_irq_config_bits old_pdc_type; + int ret; if (pin_out == GPIO_NO_WAKE_IRQ) return 0; @@ -187,9 +189,26 @@ static int qcom_pdc_gic_set_type(struct irq_data *d, unsigned int type) return -EINVAL; } + old_pdc_type = pdc_reg_read(IRQ_i_CFG, pin_out); pdc_reg_write(IRQ_i_CFG, pin_out, pdc_type); - return irq_chip_set_type_parent(d, type); + ret = irq_chip_set_type_parent(d, type); + if (ret) + return ret; + + /* + * When we change types the PDC can give a phantom interrupt. + * Clear it. Specifically the phantom shows up if a line is already + * high and we change to rising or if a line is already low and we + * change to falling but let's be consistent and clear it always. + * + * Doing this works because we have IRQCHIP_SET_TYPE_MASKED so the + * interrupt will be cleared before the rest of the system sees it. + */ + if (old_pdc_type != pdc_type) + irq_chip_set_parent_state(d, IRQCHIP_STATE_PENDING, false); + + return 0; } static struct irq_chip qcom_pdc_gic_chip = { From patchwork Tue Nov 24 17:47:20 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Doug Anderson X-Patchwork-Id: 331616 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-18.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER, INCLUDES_PATCH, MAILING_LIST_MULTI, SPF_HELO_NONE, SPF_PASS, URIBL_BLOCKED, USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95AFAC63798 for ; Tue, 24 Nov 2020 17:48:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3C8DD20857 for ; Tue, 24 Nov 2020 17:48:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="kJmaRcUE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404029AbgKXRrs (ORCPT ); Tue, 24 Nov 2020 12:47:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45840 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404018AbgKXRrq (ORCPT ); Tue, 24 Nov 2020 12:47:46 -0500 Received: from mail-pf1-x442.google.com (mail-pf1-x442.google.com [IPv6:2607:f8b0:4864:20::442]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 75F37C061A4E for ; Tue, 24 Nov 2020 09:47:46 -0800 (PST) Received: by mail-pf1-x442.google.com with SMTP id w187so4720063pfd.5 for ; Tue, 24 Nov 2020 09:47:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=D8tPSsYL1qfIVkcuPbhvLnnL5asoR8hb7TjnZUtF55c=; b=kJmaRcUEMsT8jHB+Gq+d+M86v0kV4uA4QNxg8wP6Jx4fx/QkRJQBLTaks0GEYrYCXH vMWeozBudkIku9CEGq5ASZ7QqrQA2aOei7tAlFtUC5fMz/HbFem+v/Do2dk7APjseMl4 Pc0x5reiISDWy5FqKPzJyWP/UofkJSPYekMu8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=D8tPSsYL1qfIVkcuPbhvLnnL5asoR8hb7TjnZUtF55c=; b=ZyT/fOANUs2xgBa9I0T5f7B2amm4Jn3lWTDmAWk5KVvRKKwxJpb8S3S+aRio64lm9F 7MPOuHJHcYpx6yP1SYmv4Svn8Fvm+TBa6RdHzdhTvRHcrNkrK9EN4/Ut0OHe21tBVrsp vYFRzle6hK7K8N8vdJBOhBzLygBHopaaMOmeHN2Cvamkj7uO/H8GOaaEqx/K/lX1PQrF UuSgUTFXUtjRaHF9pd+umO/2IDd7OuDuRbfYWp03Qgn2oV2o/wJmJIHBwGKrTvxEnQgo 1yMGfFwde7r1tJd/PWmq+3Kbq58vhmegwtWModpKIaLiCpbSAQgB/ypc5Vg9A6yOYdtU tnSQ== X-Gm-Message-State: AOAM531EfWAVfkuFxgQQ83uH83Zj+CprbY+DVXJVk6Fa+xOyeyOpKm0i RlHbp03iJeEx9oVFpLFvVIzVCLULnPp39A== X-Google-Smtp-Source: ABdhPJyBJULUMYEWPTxjWku02vD3DrDQD/ZbLXbaawto/H1pM+se8SKoCpExYCi52Od/6GCPMajYtg== X-Received: by 2002:a63:6341:: with SMTP id x62mr4527970pgb.93.1606240066021; Tue, 24 Nov 2020 09:47:46 -0800 (PST) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:42b0:34ff:fe3d:58e6]) by smtp.gmail.com with ESMTPSA id i4sm13480459pgg.67.2020.11.24.09.47.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Nov 2020 09:47:45 -0800 (PST) From: Douglas Anderson To: Marc Zyngier , Thomas Gleixner , Jason Cooper , Linus Walleij Cc: linux-gpio@vger.kernel.org, Neeraj Upadhyay , Stephen Boyd , Bjorn Andersson , Srinivas Ramana , linux-arm-msm@vger.kernel.org, Maulik Shah , Rajendra Nayak , Douglas Anderson , Andy Gross , linux-kernel@vger.kernel.org Subject: [PATCH v2 2/3] pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0 Date: Tue, 24 Nov 2020 09:47:20 -0800 Message-Id: <20201124094636.v2.2.I3ad184e3423d8e479bc3e86f5b393abb1704a1d1@changeid> X-Mailer: git-send-email 2.29.2.454.gaff20da3a2-goog In-Reply-To: <20201124094636.v2.1.I2702919afc253e2a451bebc3b701b462b2d22344@changeid> References: <20201124094636.v2.1.I2702919afc253e2a451bebc3b701b462b2d22344@changeid> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org There's currently a comment in the code saying function 0 is GPIO. Instead of hardcoding it, let's add a member where an SoC can specify it. No known SoCs use a number other than 0, but this just makes the code clearer. NOTE: no SoC code needs to be updated since we can rely on zero-initialization. Signed-off-by: Douglas Anderson --- (no changes since v1) drivers/pinctrl/qcom/pinctrl-msm.c | 4 ++-- drivers/pinctrl/qcom/pinctrl-msm.h | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c index 77a25bdf0da7..588df91274e2 100644 --- a/drivers/pinctrl/qcom/pinctrl-msm.c +++ b/drivers/pinctrl/qcom/pinctrl-msm.c @@ -210,8 +210,8 @@ static int msm_pinmux_request_gpio(struct pinctrl_dev *pctldev, if (!g->nfuncs) return 0; - /* For now assume function 0 is GPIO because it always is */ - return msm_pinmux_set_mux(pctldev, g->funcs[0], offset); + return msm_pinmux_set_mux(pctldev, + g->funcs[pctrl->soc->gpio_func], offset); } static const struct pinmux_ops msm_pinmux_ops = { diff --git a/drivers/pinctrl/qcom/pinctrl-msm.h b/drivers/pinctrl/qcom/pinctrl-msm.h index 333f99243c43..e31a5167c91e 100644 --- a/drivers/pinctrl/qcom/pinctrl-msm.h +++ b/drivers/pinctrl/qcom/pinctrl-msm.h @@ -118,6 +118,7 @@ struct msm_gpio_wakeirq_map { * @wakeirq_dual_edge_errata: If true then GPIOs using the wakeirq_map need * to be aware that their parent can't handle dual * edge interrupts. + * @gpio_func: Which function number is GPIO (usually 0). */ struct msm_pinctrl_soc_data { const struct pinctrl_pin_desc *pins; @@ -134,6 +135,7 @@ struct msm_pinctrl_soc_data { const struct msm_gpio_wakeirq_map *wakeirq_map; unsigned int nwakeirq_map; bool wakeirq_dual_edge_errata; + unsigned int gpio_func; }; extern const struct dev_pm_ops msm_pinctrl_dev_pm_ops; From patchwork Tue Nov 24 17:47:21 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Doug Anderson X-Patchwork-Id: 331615 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-18.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER, INCLUDES_PATCH, MAILING_LIST_MULTI, SPF_HELO_NONE, SPF_PASS, URIBL_BLOCKED, USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94B41C64E90 for ; Tue, 24 Nov 2020 17:48:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 40E30208B8 for ; Tue, 24 Nov 2020 17:48:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="J497ZQM2" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404025AbgKXRr5 (ORCPT ); Tue, 24 Nov 2020 12:47:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45838 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404024AbgKXRrs (ORCPT ); Tue, 24 Nov 2020 12:47:48 -0500 Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8D739C0617A6 for ; Tue, 24 Nov 2020 09:47:48 -0800 (PST) Received: by mail-pl1-x62b.google.com with SMTP id r2so3410498pls.3 for ; Tue, 24 Nov 2020 09:47:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=saz+0bKElsOnmCho3b8WqT2d2aqkaPOJ04CTSMvxSiQ=; b=J497ZQM21awjc/d3Je1Z+cTU2RDVLMOrOXNcbCwCcDusgcjVW4OJOiyLWuMCfXIADp 3nidOxrJfY4mdlzHlHSY1vBdZy+VXSU7jaEYOEcGz6wf00GSNxEjFT4o/CYTCx/kvk2r kcsW7/tGabyxwq0NKUe2DA6TB76ctXOcUV7Qw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=saz+0bKElsOnmCho3b8WqT2d2aqkaPOJ04CTSMvxSiQ=; b=OP8tpiibb9Y6oC8747uyPZqsgLfYJVE5hHeJncSEMAoQSjj5tCknDrbFCPRT25jG3z HHjflOT5mQf6vWx2qRnMTN1CQHBXlXMl6YD2/7S0ODc6UgjlogiOLW7XkK1slFP8ukX+ 6wO/gksdIhQvugVK8jwsnBLH4EH/cqki26l81XcI8MsfoNFpFKBvscldrnRk9lfD4rN4 PptoYAvUJGyPRkJizW/ZM0Z7oDmWOaPy5ntpbC75XtKZyGuRju0AUlGrHh39+QxqkXaN pUREmSeOGQgpLEYiOnEwcCRzil+0dRuA/ThBhPGU3ZN5s41bO7488MvKb9WiFvxQ6fEM e6rw== X-Gm-Message-State: AOAM533dxBVB9vTxYRrQqo8VDzM/X4+r8nW9tu2EzdXicLKlC83wp8Dq zT2tswutcJe69jdszkDyxgySfQ== X-Google-Smtp-Source: ABdhPJyy8Xl1OyzeDoaFsJLm4lyr0jnIk8/IpyAQ1f7P1StPM39d2hzBEY24dDhyT3PQo74Mw0cpWg== X-Received: by 2002:a17:902:bd91:b029:d9:f06:7375 with SMTP id q17-20020a170902bd91b02900d90f067375mr4923567pls.12.1606240067967; Tue, 24 Nov 2020 09:47:47 -0800 (PST) Received: from tictac2.mtv.corp.google.com ([2620:15c:202:1:42b0:34ff:fe3d:58e6]) by smtp.gmail.com with ESMTPSA id i4sm13480459pgg.67.2020.11.24.09.47.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Nov 2020 09:47:47 -0800 (PST) From: Douglas Anderson To: Marc Zyngier , Thomas Gleixner , Jason Cooper , Linus Walleij Cc: linux-gpio@vger.kernel.org, Neeraj Upadhyay , Stephen Boyd , Bjorn Andersson , Srinivas Ramana , linux-arm-msm@vger.kernel.org, Maulik Shah , Rajendra Nayak , Douglas Anderson , Andy Gross , linux-kernel@vger.kernel.org Subject: [PATCH v2 3/3] pinctrl: qcom: Clear possible pending irq when remuxing GPIOs Date: Tue, 24 Nov 2020 09:47:21 -0800 Message-Id: <20201124094636.v2.3.I771b6594b2a4d5b7fe7e12a991a6640f46386e8d@changeid> X-Mailer: git-send-email 2.29.2.454.gaff20da3a2-goog In-Reply-To: <20201124094636.v2.1.I2702919afc253e2a451bebc3b701b462b2d22344@changeid> References: <20201124094636.v2.1.I2702919afc253e2a451bebc3b701b462b2d22344@changeid> MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Conceptually, we can envision the input on Qualcomm SoCs to pass through a bunch of blocks between coming into the chip and becoming a GPIO interrupt. From guessing and running a handful of tests, I believe that we can represent the state of the world with a drawing that looks something like this: +-----------------+ +-----------------+ +-----------------+ | INPUT | --> | PINMUX | | IS_INPUT | +-----------------+ | | --> | | | output bogus (?)| | output bogus (?)| | if not muxed | | if input disab. | +-----------------+ +-----------------+ | +---------------------------------------------------+--> to PDC | V +-----------------+ +-----------------+ +-----------------+ | INTR RAW ENABLE | | DETECTION LOGIC | | STATUS REGISTER | | | | | | | | output bogus (?)| --> | maybe handles | | latches inputs | | if disabled | | polarity diffs | --> | that are high | +-----------------+ | | | | | maybe debounces | | write 1 to clr | | level irqs | +-----------------+ +-----------------+ | | +---------------------------------------------------+ | V +-----------------+ | ENABLE | | | +-----------------+ | nothing passes | --> | SUMMARY IRQ | | through if | +-----------------+ | disabled | +-----------------+ The above might not be 100% exact, but for the purpose of this discussion, the point is that there are a whole bunch of gates and transformations on the input before it gets to the circuitry that generates interrupts. As you might guess, if you reconfigure one of the gates in the above diagram while the system is configured to detect interrupts things get a little wacky. Specifically it appears that if you gate the input at any step it can cause various glitches in the later steps because they are still paying attention to their input but their input isn't really sane anymore. I did some poking and I found that I could generate bogus interrupts in the system both when muxing away from GPIO mode and also when muxing back to GPIO mode. When configured to use the PDC path for generating interrupts I found that if the external input on the GPIO was low that I'd get what looked like a rising edge when unmuxing and a falling edge when muxing. When configured away from the PDC path I got slightly different glitch interrupts when changing muxing. These glitches when remuxing matter in reality, not just in theory. To be concrete, let's take the special "wakeup_irq" in qcom_geni_serial.c as an example. In sc7180-trogdor.dtsi we configure the uart3 to have two pinctrl states, sleep and default, and mux between the two during runtime PM and system suspend (see geni_se_resources_{on,off}() for more details). The difference between the sleep and default state is that the RX pin is muxed to a GPIO during sleep and muxed to the UART otherwise. When we switch between these two states we can generate the glitches talked about above because we're configured to look for edges but the transition from the gated input (which is bogus) to the real input can look like an edge. Historically the UART case above was handled by the fact that the "enable" function in the MSM GPIO driver did an "unmask and clear". This relied on the fact that the system happens to have the interrupt disabled until suspend time and that it would enable it after the pinmux change happened, thus clearing the interrupt. The historical solution, however, had a few problems. The first problem (that nobody seemed to have tripped) is that we can still get bogus interrupts if we remux when the interrupt isn't disabled during the muxing and re-enabled after. The second problem is that it violates how I believe that the interrupt enable path is supposed to work. In Linux, if a driver does disable_irq() and later does enable_irq() on its interrupt, I believe it's expecting these properties: * If an interrupt was pending when the driver disabled then it will still be pending after the driver re-enables. * If an edge-triggered interrupt comes in while an interrupt is disabled it should assert when the interrupt is re-enabled. If you think that the above sounds a lot like the disable_irq() and enable_irq() are supposed to be masking/unmasking the interrupt instead of disabling/enabling it then you've made an astute observation. Specifically when talking about interrupts, "mask" usually means to stop posting interrupts but keep tracking them and "disable" means to fully shut off interrupt detection. It's unfortunate that this is so confusing, but presumably this is all the way it is for historical reasons. Perhaps more confusing than the above is that, even though clients of IRQs themselves don't have a way to request mask/unmask vs. disable/enable calls, IRQ chips themselves can implement both. ...and yet more confusing is that if an IRQ chip implements disable/enable then they will be called when a client driver calls disable_irq() / enable_irq(). It does feel like some of the above could be cleared up. However, without any other core interrupt changes it should be clear that when an IRQ chip gets a request to "disable" an IRQ that it has to treat it like a mask of that IRQ. In any case, after that long interlude you can see that the "unmask and clear" can break things. Maulik tried to fix it so that we no longer did "unmask and clear" in commit 71266d9d3936 ("pinctrl: qcom: Move clearing pending IRQ to .irq_request_resources callback"), but it didn't work for two reasons: * It only tried to address the problem for interrupts that had parents (like the PDC). * It regressed the problem that the original clearing was trying to solve. I think we can safely assume that if someone muxes a pin to be something other than a GPIO and then muxes it back that we can clear any interrupts that were pending on it without violating any assumptions that client drivers are making. Presumably the client drivers are intentionally remuxing the pin away from a dedicated purpose to be a plain GPIO so they don't care what the pin state was before the mux switch and they don't expect to see the pin change level during this switch. Let's move the clearing of the IRQ to the pin muxing routine so that we'll clear a pending IRQ if we're muxing from some non-GPIO mode to a GPIO mode. Fixes: 71266d9d3936 ("pinctrl: qcom: Move clearing pending IRQ to .irq_request_resources callback") Signed-off-by: Douglas Anderson --- This patch depends on #2 in the series, but not #1. #1 can land on its own and then #2/#3 can land together even without #1. The only reason patch #1 and #2/#3 are together in one series is because they address similar issues. IMPORTANT NOTE: Maulik has requested to wait for his Ack on patch #3 before landing [1]. As per above, this need not stop patch #1 from landing. I have done most of this patch testing on the Chrome OS 5.4 kernel tree (with many backports) but have sanity checked it on mainline. [1] https://lore.kernel.org/r/603c691f-3614-d87b-075a-0889e9ffc453@codeaurora.org Changes in v2: - 0 => false - If skip_wake_irqs, don't need to clear normal intr. - Add comment about glitches in both output and input. drivers/pinctrl/qcom/pinctrl-msm.c | 114 +++++++++++++++++++---------- 1 file changed, 74 insertions(+), 40 deletions(-) diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c index 588df91274e2..89e9579d076d 100644 --- a/drivers/pinctrl/qcom/pinctrl-msm.c +++ b/drivers/pinctrl/qcom/pinctrl-msm.c @@ -166,14 +166,44 @@ static int msm_get_function_groups(struct pinctrl_dev *pctldev, return 0; } +static void msm_pinctrl_clear_pending_irq(struct msm_pinctrl *pctrl, + unsigned int group, + unsigned int irq) +{ + struct irq_data *d = irq_get_irq_data(irq); + const struct msm_pingroup *g; + unsigned long flags; + u32 val; + + if (!d) + return; + + if (d->parent_data && test_bit(d->hwirq, pctrl->skip_wake_irqs)) { + irq_chip_set_parent_state(d, IRQCHIP_STATE_PENDING, false); + return; + } + + g = &pctrl->soc->groups[group]; + + raw_spin_lock_irqsave(&pctrl->lock, flags); + val = msm_readl_intr_status(pctrl, g); + val &= ~BIT(g->intr_status_bit); + msm_writel_intr_status(val, pctrl, g); + raw_spin_unlock_irqrestore(&pctrl->lock, flags); +} + static int msm_pinmux_set_mux(struct pinctrl_dev *pctldev, unsigned function, unsigned group) { struct msm_pinctrl *pctrl = pinctrl_dev_get_drvdata(pctldev); + struct gpio_chip *gc = &pctrl->chip; + unsigned int irq = irq_find_mapping(gc->irq.domain, group); const struct msm_pingroup *g; unsigned long flags; u32 val, mask; + u32 oldval; + u32 old_i; int i; g = &pctrl->soc->groups[group]; @@ -187,15 +217,26 @@ static int msm_pinmux_set_mux(struct pinctrl_dev *pctldev, if (WARN_ON(i == g->nfuncs)) return -EINVAL; - raw_spin_lock_irqsave(&pctrl->lock, flags); + disable_irq(irq); - val = msm_readl_ctl(pctrl, g); + raw_spin_lock_irqsave(&pctrl->lock, flags); + oldval = val = msm_readl_ctl(pctrl, g); val &= ~mask; val |= i << g->mux_bit; msm_writel_ctl(val, pctrl, g); - raw_spin_unlock_irqrestore(&pctrl->lock, flags); + /* + * Clear IRQs if switching to/from GPIO mode since muxing to/from + * the GPIO path can cause phantom edges. + */ + old_i = (oldval & mask) >> g->mux_bit; + if (old_i != i && + (i == pctrl->soc->gpio_func || old_i == pctrl->soc->gpio_func)) + msm_pinctrl_clear_pending_irq(pctrl, group, irq); + + enable_irq(irq); + return 0; } @@ -456,32 +497,49 @@ static const struct pinconf_ops msm_pinconf_ops = { static int msm_gpio_direction_input(struct gpio_chip *chip, unsigned offset) { const struct msm_pingroup *g; + unsigned int irq = irq_find_mapping(chip->irq.domain, offset); struct msm_pinctrl *pctrl = gpiochip_get_data(chip); unsigned long flags; + u32 oldval; u32 val; g = &pctrl->soc->groups[offset]; + disable_irq(irq); + raw_spin_lock_irqsave(&pctrl->lock, flags); - val = msm_readl_ctl(pctrl, g); + oldval = val = msm_readl_ctl(pctrl, g); val &= ~BIT(g->oe_bit); msm_writel_ctl(val, pctrl, g); raw_spin_unlock_irqrestore(&pctrl->lock, flags); + /* + * Clear IRQs if switching to/from input mode since that can use + * a phantom edge. + */ + if (oldval != val) + msm_pinctrl_clear_pending_irq(pctrl, offset, irq); + + enable_irq(irq); + return 0; } static int msm_gpio_direction_output(struct gpio_chip *chip, unsigned offset, int value) { const struct msm_pingroup *g; + unsigned int irq = irq_find_mapping(chip->irq.domain, offset); struct msm_pinctrl *pctrl = gpiochip_get_data(chip); unsigned long flags; + u32 oldval; u32 val; g = &pctrl->soc->groups[offset]; + disable_irq(irq); + raw_spin_lock_irqsave(&pctrl->lock, flags); val = msm_readl_io(pctrl, g); @@ -491,12 +549,21 @@ static int msm_gpio_direction_output(struct gpio_chip *chip, unsigned offset, in val &= ~BIT(g->out_bit); msm_writel_io(val, pctrl, g); - val = msm_readl_ctl(pctrl, g); + oldval = msm_readl_ctl(pctrl, g); val |= BIT(g->oe_bit); msm_writel_ctl(val, pctrl, g); raw_spin_unlock_irqrestore(&pctrl->lock, flags); + /* + * Clear IRQs if switching to/from input mode since that can use + * a phantom edge. + */ + if (oldval != val) + msm_pinctrl_clear_pending_irq(pctrl, offset, irq); + + enable_irq(irq); + return 0; } @@ -774,7 +841,7 @@ static void msm_gpio_irq_mask(struct irq_data *d) raw_spin_unlock_irqrestore(&pctrl->lock, flags); } -static void msm_gpio_irq_clear_unmask(struct irq_data *d, bool status_clear) +static void msm_gpio_irq_unmask(struct irq_data *d) { struct gpio_chip *gc = irq_data_get_irq_chip_data(d); struct msm_pinctrl *pctrl = gpiochip_get_data(gc); @@ -792,17 +859,6 @@ static void msm_gpio_irq_clear_unmask(struct irq_data *d, bool status_clear) raw_spin_lock_irqsave(&pctrl->lock, flags); - if (status_clear) { - /* - * clear the interrupt status bit before unmask to avoid - * any erroneous interrupts that would have got latched - * when the interrupt is not in use. - */ - val = msm_readl_intr_status(pctrl, g); - val &= ~BIT(g->intr_status_bit); - msm_writel_intr_status(val, pctrl, g); - } - val = msm_readl_intr_cfg(pctrl, g); val |= BIT(g->intr_raw_status_bit); val |= BIT(g->intr_enable_bit); @@ -815,14 +871,10 @@ static void msm_gpio_irq_clear_unmask(struct irq_data *d, bool status_clear) static void msm_gpio_irq_enable(struct irq_data *d) { - struct gpio_chip *gc = irq_data_get_irq_chip_data(d); - struct msm_pinctrl *pctrl = gpiochip_get_data(gc); - if (d->parent_data) irq_chip_enable_parent(d); - if (!test_bit(d->hwirq, pctrl->skip_wake_irqs)) - msm_gpio_irq_clear_unmask(d, true); + msm_gpio_irq_unmask(d); } static void msm_gpio_irq_disable(struct irq_data *d) @@ -837,11 +889,6 @@ static void msm_gpio_irq_disable(struct irq_data *d) msm_gpio_irq_mask(d); } -static void msm_gpio_irq_unmask(struct irq_data *d) -{ - msm_gpio_irq_clear_unmask(d, false); -} - /** * msm_gpio_update_dual_edge_parent() - Prime next edge for IRQs handled by parent. * @d: The irq dta. @@ -1097,19 +1144,6 @@ static int msm_gpio_irq_reqres(struct irq_data *d) ret = -EINVAL; goto out; } - - /* - * Clear the interrupt that may be pending before we enable - * the line. - * This is especially a problem with the GPIOs routed to the - * PDC. These GPIOs are direct-connect interrupts to the GIC. - * Disabling the interrupt line at the PDC does not prevent - * the interrupt from being latched at the GIC. The state at - * GIC needs to be cleared before enabling. - */ - if (d->parent_data && test_bit(d->hwirq, pctrl->skip_wake_irqs)) - irq_chip_set_parent_state(d, IRQCHIP_STATE_PENDING, 0); - return 0; out: module_put(gc->owner);