Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp1107490rwb; Fri, 23 Sep 2022 08:16:33 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7hEUfkJJOzNzeZYYkY2flYLkLoKwMNZWLe3jOayb9gOkQeP6S7cU/d+/a3hqcgj7fk7SFs X-Received: by 2002:aa7:d3cd:0:b0:452:5457:6375 with SMTP id o13-20020aa7d3cd000000b0045254576375mr8952995edr.111.1663946193164; Fri, 23 Sep 2022 08:16:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663946193; cv=none; d=google.com; s=arc-20160816; b=x8mXA6QNLH95ggQvCQ/BqRzr4H1TAv1SH+5HKk/g6T6iW8jc96YoywEP+YQY2CiFi2 +89zyjElc8QZVkhCAQfXvJ/SFexIdX8u1SsYgVE3tczXYSRHAQgndMgFS22fPoZvnTNq Pyho5jBCkG1+tp+JA9JyXISVjutd5T2AFudP1GgF8QjfFmAI2agv/LXIYBLOVumUD0C9 Q3MJcpUUKLc5z5FtoOtv5jRJF7i2abR5xEPS028S52o1GvRc23P+7lwqQLHo/y7oRvXs Fkk5vcwkgytAfaCXTVYBAAU2ztBLKkZ8iQ9REGhC+tyZjnfoLSVswhp01u5GJyOMorSO lSEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:from; bh=hMWCxI5nIX9GbgK3zSTCnJil/VinYvsmbWO8QiL+7ME=; b=Uxhpokkt36ReR4WSBoaPgezSw7+IXL7l8vvBmgBUovZIrhEcpm2BtqHrDbx8UPHWI4 o/f/WBxF069vGQoz4Whm9VvB95B/HK0YrdgvXqGj8ex/TDc0JlvaMs6ks3bpnUxxptbj KZ1oMXb9UmamFeNPf/QSGShGUNpr3jVrv52R2mgOmwKmBfjKVKERqW7R0zKbq02xUkzd sekYK9zZ2aWsZndvCICDVUMV+vCyp9wJxoy4OqV1UFztAHRjo+BvVokpomDH2wm7upDY BEwZTkIR52gkTeuHw+C7AYrNkNOvk4uPVujiCGZ0ZA8frUR34uGZde0s8XAwq4Yc7F/j bDhg== ARC-Authentication-Results: i=1; mx.google.com; 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 sb6-20020a1709076d8600b0078200e81b92si9017673ejc.758.2022.09.23.08.16.06; Fri, 23 Sep 2022 08:16:33 -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; 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 S231622AbiIWOwU (ORCPT + 99 others); Fri, 23 Sep 2022 10:52:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48440 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231387AbiIWOwQ (ORCPT ); Fri, 23 Sep 2022 10:52:16 -0400 Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::223]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A4FCF12FF3A; Fri, 23 Sep 2022 07:52:14 -0700 (PDT) Received: (Authenticated sender: foss@0leil.net) by mail.gandi.net (Postfix) with ESMTPSA id C18C860005; Fri, 23 Sep 2022 14:52:08 +0000 (UTC) From: Quentin Schulz Cc: linus.walleij@linaro.org, brgl@bgdev.pl, heiko@sntech.de, jay.xu@rock-chips.com, linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, foss+kernel@0leil.net, Quentin Schulz , stable@vger.kernel.org Subject: [PATCH 2/2] gpio: rockchip: request GPIO mux to pinctrl when setting direction Date: Fri, 23 Sep 2022 16:51:41 +0200 Message-Id: <20220923145141.3463754-3-foss+kernel@0leil.net> X-Mailer: git-send-email 2.37.3 In-Reply-To: <20220923145141.3463754-1-foss+kernel@0leil.net> References: <20220923145141.3463754-1-foss+kernel@0leil.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net To: unlisted-recipients:; (no To-header on input) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Quentin Schulz Before the split of gpio and pinctrl sections in their own driver, rockchip_set_mux was called in pinmux_ops.gpio_set_direction for configuring a pin in its GPIO function. This is essential for cases where pinctrl is "bypassed" by gpio consumers otherwise the GPIO function is not configured for the pin and it does not work. Such was the case for the sysfs/libgpiod userspace GPIO handling. Let's call pinctrl_gpio_direction_input/output when setting the direction of a GPIO so that the pinctrl core requests from the rockchip pinctrl driver to put the pin in its GPIO function. Fixes: 9ce9a02039de ("pinctrl/rockchip: drop the gpio related codes") Fixes: 936ee2675eee ("gpio/rockchip: add driver for rockchip gpio") Cc: stable@vger.kernel.org Signed-off-by: Quentin Schulz --- drivers/gpio/gpio-rockchip.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c index bb50335239ac8..b83913e1ee49e 100644 --- a/drivers/gpio/gpio-rockchip.c +++ b/drivers/gpio/gpio-rockchip.c @@ -156,6 +156,12 @@ static int rockchip_gpio_set_direction(struct gpio_chip *chip, unsigned long flags; u32 data = input ? 0 : 1; + + if (input) + pinctrl_gpio_direction_input(bank->pin_base + offset); + else + pinctrl_gpio_direction_output(bank->pin_base + offset); + raw_spin_lock_irqsave(&bank->slock, flags); rockchip_gpio_writel_bit(bank, offset, data, bank->gpio_regs->port_ddr); raw_spin_unlock_irqrestore(&bank->slock, flags); -- 2.37.3