From patchwork Thu Oct 5 20:54:05 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Maxime Ripard X-Patchwork-Id: 114999 Delivered-To: patch@linaro.org Received: by 10.140.22.163 with SMTP id 32csp1014678qgn; Thu, 5 Oct 2017 13:54:15 -0700 (PDT) X-Google-Smtp-Source: AOwi7QAwK06AmtSMtldzwXUgCpJR7hur0Zai/gaJegQVGdqXToElKSkBtnIE/s/AcEJQVbYO6fCc X-Received: by 10.84.240.196 with SMTP id l4mr23669504plt.399.1507236855740; Thu, 05 Oct 2017 13:54:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1507236855; cv=none; d=google.com; s=arc-20160816; b=vJr3cbozhiAVCO0hn/1GYE1ntzzvN7hvBC5xXM5KonBFROhbKnjyT/6/To2LmReTAG QxSMc+nAEoDQMa0T/5sWksS7xW/7EHm0DnKX10IkMXIKxQG1hCKBVb6ZLhXjtuBDIadJ MiLr7w6b7YW4N/ZPONJIsphTspL4qtR8+W7PtXfkP2dbrDF4ySlu8X1Nw9eyYWfWnT+1 EM7kJW7SSkjxfXmbpCJ/PVqf7L24PfZd5k+VBF99wzdHspLu7pEVJFCTo9fIzTjMzJDE VxvJmeBBT6WQTK9fZ5pmzeK8hn9HLXkf8V4bIDKHqaUE/BX5HWNQvYhcM8Gxht4brtmW ejKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=4F8M9nPWA7WkhLAEjyWeRZVetORvazdL+dj/ZSkT6Y8=; b=fMNQDSS2332Nm2HUn5wl6grv0CcDsYYn37+G8XrL6VIkNKqAI1QUFB8mTP5SXspu3x IC89xRSu4Mmn4brE4dre5TUXzSzhvmJLeMck4rg14Lv3Sg0VKIRVIVo8JBebOdl5cGHz G0sN8CUDwXrQ/ToDQ5dIScbB3Iy7htKE/jKQDso73xZsZAXVnq/RDXQeNjI2oDk+F+eU ONv3vCiPJXliDBV/bgIc6c15knitIG0mVO0l5stt2ny4xuEq61qo2XLAr5QMcL56D3YN Jlo2SVY7ubS+vjpPcT92bwx6ZkEjXkes8/R6WKbJVdewaDLqTSlOiOOhOtSidU3g3y80 uyhg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-gpio-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-gpio-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s8si13431386pgf.663.2017.10.05.13.54.15; Thu, 05 Oct 2017 13:54:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-gpio-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-gpio-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-gpio-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751654AbdJEUyO (ORCPT + 5 others); Thu, 5 Oct 2017 16:54:14 -0400 Received: from mail.free-electrons.com ([62.4.15.54]:32849 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751409AbdJEUyO (ORCPT ); Thu, 5 Oct 2017 16:54:14 -0400 Received: by mail.free-electrons.com (Postfix, from userid 110) id A678520971; Thu, 5 Oct 2017 22:54:11 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.free-electrons.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.0 Received: from localhost (unknown [91.126.32.14]) by mail.free-electrons.com (Postfix) with ESMTPSA id 761AF20914; Thu, 5 Oct 2017 22:54:11 +0200 (CEST) From: Maxime Ripard To: Chen-Yu Tsai , Maxime Ripard , linus.walleij@linaro.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org Subject: [PATCH 0/3] pinctrl: sunxi: Start to enforce the strict mode Date: Thu, 5 Oct 2017 22:54:05 +0200 Message-Id: X-Mailer: git-send-email 2.13.5 Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Hi, Here is an attempt to enable pinctrl's strict mode on our pinctrl drivers. Indeed, our controllers should have had that mode enabled since its introduction. However, there's a number of issues with old device trees that prevent from just enabling it for all the devices. There's basically two of them: - Most of our old DTs have a pinctrl node for GPIOs, which will result in an error when the driver is going to request the gpio because it would already be requested automatically by pinctrl. We cannot break those. - Some of these GPIOs also need to change their pin configuration to add a bias or change the current output, and there isn't a migration path. Let's just keep the old behaviour for the old SoCs, and enforce it on the new one, and enabled it by default so that the situation at least doesn't get worse. This has been tested on an A83t (strict on) and an H3 (strict off) board. Let me know what you think, Maxime Maxime Ripard (3): pinctrl: sunxi: Introduce the strict flag pinctrl: sunxi: Disable strict mode for old pinctrl drivers pinctrl: sunxi: Enforce the strict mode by default drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c | 1 + drivers/pinctrl/sunxi/pinctrl-sun5i.c | 1 + drivers/pinctrl/sunxi/pinctrl-sun6i-a31.c | 1 + drivers/pinctrl/sunxi/pinctrl-sun8i-a23.c | 1 + drivers/pinctrl/sunxi/pinctrl-sun8i-a33.c | 1 + drivers/pinctrl/sunxi/pinctrl-sun8i-h3.c | 3 ++- drivers/pinctrl/sunxi/pinctrl-sun9i-a80.c | 1 + drivers/pinctrl/sunxi/pinctrl-sunxi.c | 6 +++++- drivers/pinctrl/sunxi/pinctrl-sunxi.h | 1 + 9 files changed, 14 insertions(+), 2 deletions(-) base-commit: c27ad2958485126c3828e59d53013d3b45ec14f2 -- git-series 0.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Acked-by: Chen-Yu Tsai Acked-by: Chen-Yu Tsai