From nobody Sun Nov 24 12:01:26 2024 Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch [185.70.40.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 750EF1DB546 for ; Wed, 6 Nov 2024 10:08:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.70.40.137 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730887729; cv=none; b=FJPiCn1AYFocjTgAKRuJ39HTA9WYYENhcsQldSj/r32LMXFmiM8pZsEWC+FMSVZO/Eli2VRkMvgjw4FEXZLgKqEMbzC0zenk5UsoBOqLZZnIkjbe2jsfX8/rknU9NDlp04fVzdNIMLk2+VOmHJs1qignWoGU9A5WATcla0DcaO8= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730887729; c=relaxed/simple; bh=va/DILIUevm8NNWXKhwyztN+R+Y+3LeC7lUxWXKJVmQ=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=RLy+vIZLd7khgGlkcIfqV35Cxkr4GVh0C+Qc268y/VYBfHvtFZyGjJ/0T5B+twdLb5QZ5lsz/jhvyXWOuLw5v6Lo+3JInaDkb8tevknTKpVjSZcbR/EwVsc95Q8/TYCcAu2N9mCFvns7V20oTVxYVigJGdc9gJeCOOfvSt9nmlc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=protonmail.com; spf=pass smtp.mailfrom=protonmail.com; dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com header.b=V5Ysh5dT; arc=none smtp.client-ip=185.70.40.137 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=protonmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=protonmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com header.b="V5Ysh5dT" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1730887719; x=1731146919; bh=dEoDbeevWJIwX1JnG6y9+8lc/XLJscWHnsFUwOMj8fE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=V5Ysh5dThHm+t9+k4S/JuVHI0itg/nnhexwL4GlqVNQDnL6UXlYCHL1GDtmkS/oN+ +wc/222sJTeCYyKRQPrlBdRRVmoRqE/7yLziZ7u7Q7tTtCQIxMifYXSwi+ZAed31Am ATHm8EqSoBLeSyquyM/j4dHypxZzrF+ouZpsJGDOxlS3pJJE0LKlrwbBVihaJon/6R lFNl/MGRtaOFSWuQiiE4efPxzPdfnqML+Ikx0l8lqqlzeGxr8KjaaW9BBscwdD8zkP lp0skUKfxJLwV+FBXBc8vgw5g/BHl4+8qmKAC86/tqWfzv2qpZumc8kI4qhoq5I1Hd VjbRh0vpyhYtA== Date: Wed, 06 Nov 2024 10:08:33 +0000 To: Sean Wang , Linus Walleij , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Matthias Brugger , AngeloGioacchino Del Regno , Andy Teng From: Yassine Oudjana Cc: Yassine Oudjana , Yassine Oudjana , linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v7 1/7] dt-bindings: pinctrl: mediatek,mt6779-pinctrl: Pull pinctrl node changes from MT6795 document Message-ID: <20241106100741.173825-2-y.oudjana@protonmail.com> In-Reply-To: <20241106100741.173825-1-y.oudjana@protonmail.com> References: <20241106100741.173825-1-y.oudjana@protonmail.com> Feedback-ID: 6882736:user:proton X-Pm-Message-ID: 824e0214d7b2a6f87eb8c72b1622141a20f40769 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" mediatek,pinctrl-mt6795.yaml has different node name patterns which match bindings of other MediaTek pin controllers, ref for pinmux-node.yaml which has a description of the pinmux property, as well as some additional descriptions for some pin configuration properties. Pull those changes into mediatek,mt6779-pinctrl.yaml and adjust the example DTS to match in preparation to combine the MT6795 document into it. The only DT that currently gets affected by these changes is mt6797.dtsi. It is modified to match the new bindings in a following patch. Signed-off-by: Yassine Oudjana Reviewed-by: AngeloGioacchino Del Regno Reviewed-by: Rob Herring (Arm) --- .../pinctrl/mediatek,mt6779-pinctrl.yaml | 38 ++++++++++++++----- 1 file changed, 28 insertions(+), 10 deletions(-) diff --git a/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinc= trl.yaml b/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctr= l.yaml index 3bbc00df5548d..352a88d7b135e 100644 --- a/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml +++ b/Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml @@ -111,12 +111,12 @@ allOf: - "#interrupt-cells" =20 patternProperties: - '-[0-9]*$': + '-pins$': type: object additionalProperties: false =20 patternProperties: - '-pins*$': + '^pins': type: object description: A pinctrl node should contain at least one subnodes representing= the @@ -124,7 +124,9 @@ patternProperties: pins it needs, and how they should be configured, with regard to= muxer configuration, pullups, drive strength, input enable/disable and= input schmitt. - $ref: /schemas/pinctrl/pincfg-node.yaml + allOf: + - $ref: pinmux-node.yaml + - $ref: pincfg-node.yaml =20 properties: pinmux: @@ -135,9 +137,25 @@ patternProperties: =20 bias-disable: true =20 - bias-pull-up: true - - bias-pull-down: true + bias-pull-up: + oneOf: + - type: boolean + - enum: [100, 101, 102, 103] + description: Pull up PUPD/R0/R1 type define value. + description: | + For normal pull up type, it is not necessary to specify R1R0 + values; When pull up type is PUPD/R0/R1, adding R1R0 defines + will set different resistance values. + + bias-pull-down: + oneOf: + - type: boolean + - enum: [100, 101, 102, 103] + description: Pull down PUPD/R0/R1 type define value. + description: | + For normal pull down type, it is not necessary to specify R1= R0 + values; When pull down type is PUPD/R0/R1, adding R1R0 defin= es + will set different resistance values. =20 input-enable: true =20 @@ -221,8 +239,8 @@ examples: #interrupt-cells =3D <2>; interrupts =3D ; =20 - mmc0_pins_default: mmc0-0 { - cmd-dat-pins { + mmc0_pins_default: mmc0-pins { + pins-cmd-dat { pinmux =3D , , , @@ -235,11 +253,11 @@ examples: input-enable; mediatek,pull-up-adv =3D <1>; }; - clk-pins { + pins-clk { pinmux =3D ; mediatek,pull-down-adv =3D <2>; }; - rst-pins { + pins-rst { pinmux =3D ; mediatek,pull-up-adv =3D <0>; }; --=20 2.47.0