From nobody Thu Apr 2 13:16:42 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D583BC07E9D for ; Sat, 24 Sep 2022 08:06:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233729AbiIXIGJ (ORCPT ); Sat, 24 Sep 2022 04:06:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54334 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233613AbiIXIF2 (ORCPT ); Sat, 24 Sep 2022 04:05:28 -0400 Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1CBBF1871 for ; Sat, 24 Sep 2022 01:05:20 -0700 (PDT) Received: by mail-lj1-x233.google.com with SMTP id l12so2292164ljg.9 for ; Sat, 24 Sep 2022 01:05:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date; bh=V4HqYpo8tMEHEMR+IQ/EL+5/qaemZaDGSORGW1L0emg=; b=uh7Jvk4SCQQqWNT3MQ5m9zPWGWr7RlXPOTB1uKtRy3l/HZXbK07TAn9qRZHFUUHVU8 Q1LFvs48x+rZj8yiaUgZSq66Czp1RCeaj9b3N2z+r61KI5QN56vKOzJJANOvW4udshyQ Iv4y7x27c3rH7OzSsAJ0L9f6eAm1P9Fy4nBV/X3N135KITvTsF6HEhZTPnrfjtnX5yqr nOYlN7VRByAu/UGZ0lOyoCJHiWsTdvYWTZe4D+eodiKZyJ7vG0EomYE8jcR9wel49TO9 ycK0VGwHTWI1cBxebyEEoqo3wI/ZA3WzGlYEXv/Le9Gzl/a/QiPgN4PSoiy4dwyuA+yn MsBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date; bh=V4HqYpo8tMEHEMR+IQ/EL+5/qaemZaDGSORGW1L0emg=; b=RIIXfxTXc8V76VGTKM0S+CxRHMNzPOJQtq+Zy3L1vZIc0BRJOiRfDmbZtyqydSGqjb L595l/JeYh18r/frZvqFZIQgsUCoMYvIJ7Py7zxlmnnkdL45MADjBVYj/V9duk98UbSt hGGeFw/UPwcKyARiYaGAXjRTrXfzzlqzBRzDGGz/ZR8OwYuO2TxO7MbssaZzCzzyxuSj uXBoY9EaJ7a5dL1AYBnu9yRAoPRd2P20skKgwv670A8L13rldivcZlU7KpJCyHPhZU+9 vPwsFjnC6SCDfmME/oc7EHucexX3SSgOH82DFYvpkvNMIpy08LZyUyWlvnebOeXHW/ca KCpw== X-Gm-Message-State: ACrzQf3oHb2eAImrZ6spooBrKG6TNjNFj4iYx5PH+o14kaahcDWatyTE ancTTrVXklVWsD6zgCpt6is7wQ== X-Google-Smtp-Source: AMsMyM6ksJBlNqkBRNd8kafnhHTh6uTiurBiBB6JP/8s0cUerO/BthhvSnTyCZV/jymh/ZTDdVo4Xg== X-Received: by 2002:a05:651c:221a:b0:26c:6fe2:c146 with SMTP id y26-20020a05651c221a00b0026c6fe2c146mr4118969ljq.284.1664006718976; Sat, 24 Sep 2022 01:05:18 -0700 (PDT) Received: from krzk-bin.. (78-11-189-27.static.ip.netia.com.pl. [78.11.189.27]) by smtp.gmail.com with ESMTPSA id y2-20020a2e5442000000b0026c41574790sm1696668ljd.30.2022.09.24.01.05.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 24 Sep 2022 01:05:18 -0700 (PDT) From: Krzysztof Kozlowski To: Andy Gross , Bjorn Andersson , Konrad Dybcio , Linus Walleij , Rob Herring , Krzysztof Kozlowski , Sricharan R , Stephan Gerhold , Shawn Guo , Vinod Koul , krishna Lanka , Sivaprakash Murugesan , linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Krzysztof Kozlowski Subject: [PATCH 09/32] dt-bindings: pinctrl: qcom,ipq6018: fix matching pin config Date: Sat, 24 Sep 2022 10:04:36 +0200 Message-Id: <20220924080459.13084-10-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220924080459.13084-1-krzysztof.kozlowski@linaro.org> References: <20220924080459.13084-1-krzysztof.kozlowski@linaro.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" The TLMM pin controller follows generic pin-controller bindings, so should have subnodes with '-state' and '-pins'. Otherwise the subnodes (level one and two) are not properly matched. This method also unifies the bindings with other Qualcomm TLMM and LPASS pinctrl bindings. Signed-off-by: Krzysztof Kozlowski --- .../bindings/pinctrl/qcom,ipq6018-pinctrl.yaml | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl= .yaml b/Documentation/devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl.yaml index 9c6958a9cfe4..e7f3106ccd39 100644 --- a/Documentation/devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl.yaml +++ b/Documentation/devicetree/bindings/pinctrl/qcom,ipq6018-pinctrl.yaml @@ -42,10 +42,17 @@ properties: gpio-ranges: maxItems: 1 =20 -#PIN CONFIGURATION NODES patternProperties: - '-pinmux$': - type: object + "-state$": + oneOf: + - $ref: "#/$defs/qcom-ipq6018-tlmm-state" + - patternProperties: + "-pins$": + $ref: "#/$defs/qcom-ipq6018-tlmm-state" + additionalProperties: false + +$defs: + qcom-ipq6018-tlmm-state: description: Pinctrl node's client devices use subnodes for desired pin configura= tion. Client device subnodes use below standard properties. @@ -146,7 +153,7 @@ examples: #gpio-cells =3D <2>; gpio-ranges =3D <&tlmm 0 0 80>; =20 - serial3-pinmux { + serial3-state { pins =3D "gpio44", "gpio45"; function =3D "blsp2_uart"; drive-strength =3D <8>; --=20 2.34.1