Message ID | 20221129023401.278780-1-bero@baylibre.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp84846wrr; Mon, 28 Nov 2022 18:37:02 -0800 (PST) X-Google-Smtp-Source: AA0mqf6bIrXyKAKM3MQYeoldbpZKKihRKLDH94VDjgqULNoNMKbdnbEq1OtLdr8V7tkB2KHMVRjE X-Received: by 2002:a17:906:6847:b0:7bf:a827:35c with SMTP id a7-20020a170906684700b007bfa827035cmr7396459ejs.711.1669689422084; Mon, 28 Nov 2022 18:37:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669689422; cv=none; d=google.com; s=arc-20160816; b=bWurVNFsqqEqxnYqr/lV40mCoSsIUF5w57XJLQMBLvn4CrHTDoMDbjVqgmaei+8o2z j8wDnOKcQ0DtSOQTqS2py9HnTbxzXzfE2tyGtARqNKzbsSdAiLoI8mBMPw1OikirFL5k XJorvpivhtB6OJT4IQW7T9+N8erTHjs0KjmDOS5x8cmFFt8lOCJFCAYMoP0K69X8RZAs 2HZeSM3dbfOi1ZNhZLf6RbJBhChfJzang0ZoxNXxH1gZRsiC0t8Sdq8X9Q5U1EXrfdSF C5TY6hmrvw5bOHF4L7JmWPx3QpAUN+cr92oQHmcHylodFpGuH+qsU4x5FKPulueGEXAy rdBQ== 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=p2wIPJTHkD+bylj39gTMFm3DTXuPW9bL6vkGIzsV8aw=; b=I4912qIguaEC2p7HTIOvsTLjI4PvtTEInmtDcCwi7oD4DmBNei7TniRRN/PLXGw3JC J7V5UBNeS8+LhH9nQydtn6QMlKvNrWbmAb62mf8DluGCYqbRtnnRGQBOLlt/ykbfHKyF m/24QGoBa7LwzFPk/FU09okK9zVLHghYaEoIpNigil7KEIHQLcmiiItPN1Cm4w/cC9QT m2BYS8JJH3p5yEGud0t/+Hfb9FK3vlC4qKcg0KqScyxawrvJYsyZ0UxQkLJfqYAh+kwJ S+aCSNoAvM88FUEx8Y/8ZbMLUgkwvyNgDapmmDuNazA7knTuqa4nxs9lxfQQBe5dzCDg t4JQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=kZurQYlw; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hq29-20020a1709073f1d00b007ae29da29b3si12934766ejc.731.2022.11.28.18.36.38; Mon, 28 Nov 2022 18:37:02 -0800 (PST) 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=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=kZurQYlw; 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 S235190AbiK2CeI (ORCPT <rfc822;gah0developer@gmail.com> + 99 others); Mon, 28 Nov 2022 21:34:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37776 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234872AbiK2CeG (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 28 Nov 2022 21:34:06 -0500 Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DA2BE29CB5 for <linux-kernel@vger.kernel.org>; Mon, 28 Nov 2022 18:34:04 -0800 (PST) Received: by mail-ed1-x535.google.com with SMTP id m19so16736625edj.8 for <linux-kernel@vger.kernel.org>; Mon, 28 Nov 2022 18:34:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=p2wIPJTHkD+bylj39gTMFm3DTXuPW9bL6vkGIzsV8aw=; b=kZurQYlwJIRzTT+7zqhkAVIxZypR4Ym0x21fe9bnwCAsqwvJR3TgpGxd88mHYJPm60 LX3Zp6nshIqrm/lDU+Va90uCJdbBfnFx54Pa1g98o7iTTEH/uIS7obpjSO+yHcX+15q7 jtfPifPzJKnKO6y1bWCOOeVy05p0Lu1/MRZ6+n6HSI3Ak1OSE5/P1MbgdRr8cP+b92QP coG/3EtVGGfQ9NRoOUWInj0l71Yrm5wOABzV725Ia6FZQZjeAeNlVjIZjteS9eAogSyA 11LA1BueA/e0g3FQ6uoXH7ehNiaD42FNk/FB1CO/tGlEeiyz1+fbvFgyOSSvvpuW+F6U sPNQ== 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:message-id :reply-to; bh=p2wIPJTHkD+bylj39gTMFm3DTXuPW9bL6vkGIzsV8aw=; b=GQQFF8ElPibABcGvtJEgavo+Op7YUQJ4NrrfafgK4tqRRi138lpuscbKigCgF9Qm2Z ww3oyldjSsDAU6r32O6pJt0CPzu/pM0XfM3ewOsy97IwKrWjrkIvnr+DjFL8PyCN/dQ9 kBE9DGE8MPLmFMfAyQdKOp1N275YX1w0734nTvEA63w3VXbjiaeZP+Hui+5ODgMbS7cT nPZYu4zpjZDenrOAZ1TbLnY5OjoDqdkmG3Q693epDMP9ZOTRH8P2cZSPy2ak6ZtpN6km VjSOYL0pCQn1ubzyHGVowCvE1mqgeVNu3dmQz5filaOKZy2K5/Wk3dGFa5lMuz/choxV XIaQ== X-Gm-Message-State: ANoB5pmGQAs342MXyY6TRGa+Sao/EcTsUsaFPxph5rjwtyOVUNW3wB4n ZqMz2AcIfYJ6HrVCXxAOeickpg== X-Received: by 2002:a05:6402:4008:b0:458:dd63:e339 with SMTP id d8-20020a056402400800b00458dd63e339mr31534833eda.81.1669689243478; Mon, 28 Nov 2022 18:34:03 -0800 (PST) Received: from c64.fritz.box ([81.221.122.240]) by smtp.gmail.com with ESMTPSA id a4-20020aa7d744000000b004615f7495e0sm5733817eds.8.2022.11.28.18.34.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 28 Nov 2022 18:34:03 -0800 (PST) From: =?utf-8?q?Bernhard_Rosenkr=C3=A4nzer?= <bero@baylibre.com> To: devicetree@vger.kernel.org Cc: linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com, krzysztof.kozlowski@linaro.org, matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com, khilman@baylibre.com, linux-gpio@vger.kernel.org, linus.walleij@linaro.org Subject: [PATCH v3 0/7] Remove the pins-are-numbered DT property Date: Tue, 29 Nov 2022 03:33:54 +0100 Message-Id: <20221129023401.278780-1-bero@baylibre.com> X-Mailer: git-send-email 2.38.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1750796255674534571?= X-GMAIL-MSGID: =?utf-8?q?1750796255674534571?= |
Series |
Remove the pins-are-numbered DT property
|
|
Message
Bernhard Rosenkränzer
Nov. 29, 2022, 2:33 a.m. UTC
During the review of my MT8365 support patchset (https://lore.kernel.org/linux-mediatek/20221117210356.3178578-1-bero@baylibre.com/), the issue of the "pins-are-numbered" DeviceTree property has come up. This property is unique to Mediatek MT65xx and STM32 pinctrls, and doesn't seem to serve any purpose (both the Mediatek and STM32 drivers simply refuse to deal with a device unless pins-are-numbered is set to true). There is no other use of this property in the kernel or in other projects using DeviceTrees (checked u-boot and FreeBSD -- in both of those, the flag is present in Mediatek and STM devicetrees, but not used anywhere). There is also no known use in userspace (in fact, a userland application relying on the property would be broken because it would get true on any Mediatek or STM chipset and false on all others, even though other chipsets use numbered pins). This patchset removes all uses of pins-are-numbered and marks the property as deprecated. v3: - No functional changes; add recent Reviewed-Bys and Acked-Bys, add linux-gpio to Cc v2: - Deprecate the property instead of removing it completely from schemas - squash some related commits Bernhard Rosenkränzer (7): pinctrl: mediatek: common: Remove check for pins-are-numbered pinctrl: stm32: Remove check for pins-are-numbered dt-bindings: pinctrl: mediatek,mt65xx: Deprecate pins-are-numbered dt-bindings: pinctrl: st,stm32: Deprecate pins-are-numbered arm64: dts: mediatek: Remove pins-are-numbered property ARM: dts: mediatek: Remove pins-are-numbered property ARM: dts: stm32: Remove the pins-are-numbered property .../bindings/pinctrl/mediatek,mt65xx-pinctrl.yaml | 5 ++--- .../devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml | 7 +++---- arch/arm/boot/dts/mt2701.dtsi | 1 - arch/arm/boot/dts/mt7623.dtsi | 1 - arch/arm/boot/dts/mt8135.dtsi | 1 - arch/arm/boot/dts/stm32f4-pinctrl.dtsi | 1 - arch/arm/boot/dts/stm32f7-pinctrl.dtsi | 1 - arch/arm/boot/dts/stm32h743.dtsi | 1 - arch/arm/boot/dts/stm32mp131.dtsi | 1 - arch/arm/boot/dts/stm32mp151.dtsi | 2 -- arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 1 - arch/arm64/boot/dts/mediatek/mt8167.dtsi | 1 - arch/arm64/boot/dts/mediatek/mt8173-elm.dtsi | 1 - arch/arm64/boot/dts/mediatek/mt8173.dtsi | 1 - arch/arm64/boot/dts/mediatek/mt8516.dtsi | 1 - drivers/pinctrl/mediatek/pinctrl-mtk-common.c | 6 ------ drivers/pinctrl/stm32/pinctrl-stm32.c | 5 ----- 17 files changed, 5 insertions(+), 32 deletions(-)
Comments
Hi Bero, long time no see! On Tue, Nov 29, 2022 at 3:34 AM Bernhard Rosenkränzer <bero@baylibre.com> wrote: > During the review of my MT8365 support patchset > (https://lore.kernel.org/linux-mediatek/20221117210356.3178578-1-bero@baylibre.com/), > the issue of the "pins-are-numbered" DeviceTree property has come up. (...) > This patchset removes all uses of pins-are-numbered and marks the > property as deprecated. I don't remember any more why this property was introduced, but I am happy to see it go. > Bernhard Rosenkränzer (7): > pinctrl: mediatek: common: Remove check for pins-are-numbered > pinctrl: stm32: Remove check for pins-are-numbered > dt-bindings: pinctrl: mediatek,mt65xx: Deprecate pins-are-numbered > dt-bindings: pinctrl: st,stm32: Deprecate pins-are-numbered I applied patches 1-4 to the pin control tree for v6.2, please funnel the rest through mediatek/stm32 and SoC trees! Yours, Linus Walleij
On Sat, Dec 3, 2022 at 10:22 AM Linus Walleij <linus.walleij@linaro.org> wrote: > > Hi Bero, > > long time no see! Hi Linus, indeed, I've been doing mostly userland stuff lately, and my latest kernel patch was x86 (got to keep all of my hardware working ;) ). Now that I've changed jobs, I'm expecting to be more active on the kernel side (though still doing a lot of userland). > > This patchset removes all uses of pins-are-numbered and marks the > > property as deprecated. > > I don't remember any more why this property was introduced, but > I am happy to see it go. I couldn't find why it was introduced either (and git blame wasn't much help). I'm assuming there was some other mode in vendor trees that never made it into mainline (but the flag for switching between the modes did). > I applied patches 1-4 to the pin control tree for v6.2, > please funnel the rest through mediatek/stm32 and > SoC trees! Thanks! Remaining patches reposted and currently waiting. ttyl bero