Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2628435rwb; Thu, 17 Nov 2022 13:40:33 -0800 (PST) X-Google-Smtp-Source: AA0mqf7NGHG8gGV3YzWOKBg71N5w0n7MNUxweI643c2eVj+vFisCL2NSIUreEor3e0PcZ43SmwcU X-Received: by 2002:a17:906:860b:b0:7ad:f8e2:ff0a with SMTP id o11-20020a170906860b00b007adf8e2ff0amr3675199ejx.275.1668721233550; Thu, 17 Nov 2022 13:40:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668721233; cv=none; d=google.com; s=arc-20160816; b=KuwDjm9JJFapKAaO8Cv683C7l2qSRK5jmv++qbh8lHVFT8muRDA9JENtLbWbj3sufd ByPenim9c2sA6mARlG1iXjNXhOIN39GTSQrskowZu8PWTD6hO0S63YXr3BdECFmByozT irMlVvSnHc0ld+G00JkoIennTgITrGTzbE1hRzzTa3Osv9qsl/u1G8BCvtd4+xmfJYM2 OXH8MZ8NhfQ7vGbb0PdeMFW+qI/Pno6OmQ6NSqzWxAhc0S3h5An79m4R9fBf2VFjAapu uOMgP/HJiSdCRKkHMNX4cF+Q3dlA2gJM5FIvJuv3w5lHdIwbmxIZOVWuYt9fNksZcfvV 0wXQ== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=cOZMxW37BY8Yd9fEGMThaSEaaYa1HlPqz2FtFLwUuYk=; b=Skxi1sSl2BCC9N32TXkx+zDjhhT1YqHbD6KfqOlcP8fq+y/b1wSpUuGmB6eg4w+EgX LY56mDM8l38ZBHKZn7EkOQCtk8bgYPj9VCdozbXAUaDjQQR8uyp7sR+Kv07UrJbzvoXB n+QimWtB3e+n8BwTbpROb0RoyGK1KpH//TSYY7G5nq6YKEXG5/lXLGGrQUd1+L6QVv6W kfYJQ0dlKs4s5gmSvztHBvRefmUq8cIjm/yPlDT8musVF7rIk3QAM1YpK7+8DytEO7+V 81iRFybKNZaVoQ+9bRAN/kIGFVZ20jfAqIbf2WVsmBJMp6HaR2ftA0dgQjhgHDhgrDRf rQgw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=kR8n8904; 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 dz13-20020a0564021d4d00b00467238595easi1921005edb.369.2022.11.17.13.40.10; Thu, 17 Nov 2022 13:40:33 -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=kR8n8904; 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 S240773AbiKQVF3 (ORCPT + 92 others); Thu, 17 Nov 2022 16:05:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50292 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240490AbiKQVEy (ORCPT ); Thu, 17 Nov 2022 16:04:54 -0500 Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1778E8E2A2 for ; Thu, 17 Nov 2022 13:04:12 -0800 (PST) Received: by mail-ej1-x62a.google.com with SMTP id bj12so8131174ejb.13 for ; Thu, 17 Nov 2022 13:04:12 -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:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=cOZMxW37BY8Yd9fEGMThaSEaaYa1HlPqz2FtFLwUuYk=; b=kR8n89044TBqJ54l4lMHOxRV7EqoXki+eLerysd/jNKPYGrAgxT799qR28Qvy/LCJX in49v01xRAuavqdSJSNE+XvSNP9EjMvNp4AM++hjjJD5029gwjysKmNLLwPmk2gbblOt Bcz4U54Rv+ENpz/1P74mPIQ1ZwCj8reBpQwVGykfGJ64rXJ0az+imp5MWD+EukriXf2f xD6ikXLo/tzc+bODI2IFP+DDOXZnuq0i8gR+Pup1MdF3McRAG/9SYACWT3BSzGPsfxuO HohqWTodc3G+LuF6Q0LMJfM8QLl0NCQmXDVFI6YirVVTX0IMKc/KkHe2VvvCyKD/8TWm T3bQ== 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:message-id:reply-to; bh=cOZMxW37BY8Yd9fEGMThaSEaaYa1HlPqz2FtFLwUuYk=; b=apGjo9WQGTCj3pdYZs+1iQ8eKqL1eaaAMwhhsMt5tMf3sMpgc6sgWqrlWC7hc6Cudp nHiKP5NIihDFMrzCO+dmQmDlEYmZ2BT54mMV80HAwo6KU433d7skvCMEEEuXwuCMBcjt 2i0dXFaGX1OMzvi8OwN75DgKOvaN/FFZlSKT+94uPETgaMVDY3Kw7HF18lVnAh9B1xPn 8yKCIQPkWohLRAZzKe/Te3xZxMeMlqqb8nWJIVn58eIi5mFUmqV+IArAtiPKAJy+IVcd TLQ6mIkX2KsbhwVD5PXKNxsaF9Fo30khSxqnGZoUngGufchOivQTZjuTKHVsqnnhEr9n /kdg== X-Gm-Message-State: ANoB5pnBMLvPje4BcWmhDAzwnQh+WsUPhHi8GkmS5t7e8A8Tu1GSRi6U M/tTqyWjsuPX5xTgrDvrgMWMJBLMdhXKi2Zx X-Received: by 2002:a17:906:ef1:b0:78d:260d:a6e4 with SMTP id x17-20020a1709060ef100b0078d260da6e4mr3532130eji.93.1668719047430; Thu, 17 Nov 2022 13:04:07 -0800 (PST) Received: from c64.fritz.box ([2a01:2a8:8108:8301:7643:bec8:f62b:b074]) by smtp.gmail.com with ESMTPSA id p15-20020aa7cc8f000000b00461c6e8453dsm970807edt.23.2022.11.17.13.04.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 17 Nov 2022 13:04:06 -0800 (PST) From: =?UTF-8?q?Bernhard=20Rosenkr=C3=A4nzer?= To: linux-mediatek@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com, angelogiocchino.delregno@collabora.com Subject: [PATCH v3 4/7] dt-bindings: pinctrl: add bindings for Mediatek MT8365 SoC Date: Thu, 17 Nov 2022 22:03:53 +0100 Message-Id: <20221117210356.3178578-5-bero@baylibre.com> X-Mailer: git-send-email 2.38.1 In-Reply-To: <20221117210356.3178578-1-bero@baylibre.com> References: <20221117210356.3178578-1-bero@baylibre.com> 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: X-Mailing-List: linux-kernel@vger.kernel.org Add devicetree bindings for Mediatek MT8365 pinctrl driver. Signed-off-by: Bernhard Rosenkränzer --- .../pinctrl/mediatek,mt8365-pinctrl.yaml | 202 ++++++++++++++++++ 1 file changed, 202 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml diff --git a/Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml new file mode 100644 index 0000000000000..7758644da302a --- /dev/null +++ b/Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml @@ -0,0 +1,202 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/pinctrl/mediatek,mt8365-pinctrl.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Mediatek MT8365 Pin Controller + +maintainers: + - Zhiyong Tao + - Bernhard Rosenkränzer + +description: |+ + The MediaTek's MT8365 Pin controller is used to control SoC pins. + +properties: + compatible: + const: mediatek,mt8365-pinctrl + + reg: + maxItems: 1 + + mediatek,pctl-regmap: + $ref: /schemas/types.yaml#/definitions/phandle-array + items: + maxItems: 1 + minItems: 1 + maxItems: 2 + description: | + Should be phandles of the syscfg node. + + pins-are-numbered: + $ref: /schemas/types.yaml#/definitions/flag + description: | + Specify the subnodes are using numbered pinmux to specify pins. + + gpio-controller: true + + "#gpio-cells": + const: 2 + description: | + Number of cells in GPIO specifier. Since the generic GPIO + binding is used, the amount of cells must be specified as 2. See the below + mentioned gpio binding representation for description of particular cells. + + interrupt-controller: true + + interrupts: + maxItems: 1 + + "#interrupt-cells": + const: 2 + +required: + - compatible + - reg + - gpio-controller + - "#gpio-cells" + +allOf: + - $ref: pinctrl.yaml# + +patternProperties: + '-pins$': + type: object + additionalProperties: false + patternProperties: + 'pins': + type: object + additionalProperties: false + description: | + A pinctrl node should contain at least one subnode representing the + pinctrl groups available on the machine. Each subnode will list the + 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" + + properties: + pinmux: + description: + integer array, represents gpio pin number and mux setting. + Supported pin number and mux varies for different SoCs, and are + defined as macros in -pinfunc.h directly. + + bias-disable: true + + bias-pull-up: + description: | + Besides generic pinconfig options, it can be used as the pull up + settings for 2 pull resistors, R0 and R1. User can configure those + special pins. + + bias-pull-down: true + + input-enable: true + + input-disable: true + + output-low: true + + output-high: true + + input-schmitt-enable: true + + input-schmitt-disable: true + + mediatek,drive-strength-adv: + description: | + Describe the specific driving setup property. + For I2C pins, the existing generic driving setup can only support + 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they + can support 0.125/0.25/0.5/1mA adjustment. If we enable specific + driving setup, the existing generic setup will be disabled. + The specific driving setup is controlled by E1E0EN. + When E1=0/E0=0, the strength is 0.125mA. + When E1=0/E0=1, the strength is 0.25mA. + When E1=1/E0=0, the strength is 0.5mA. + When E1=1/E0=1, the strength is 1mA. + EN is used to enable or disable the specific driving setup. + Valid arguments are described as below: + 0: (E1, E0, EN) = (0, 0, 0) + 1: (E1, E0, EN) = (0, 0, 1) + 2: (E1, E0, EN) = (0, 1, 0) + 3: (E1, E0, EN) = (0, 1, 1) + 4: (E1, E0, EN) = (1, 0, 0) + 5: (E1, E0, EN) = (1, 0, 1) + 6: (E1, E0, EN) = (1, 1, 0) + 7: (E1, E0, EN) = (1, 1, 1) + So the valid arguments are from 0 to 7. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [0, 1, 2, 3, 4, 5, 6, 7] + + mediatek,pull-up-adv: + description: | + Pull up setings for 2 pull resistors, R0 and R1. User can + configure those special pins. Valid arguments are described as below: + 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. + 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. + 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. + 3: (R1, R0) = (1, 1) which means R1 enabled and R0 enabled. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [0, 1, 2, 3] + + mediatek,pull-down-adv: + description: | + Pull down settings for 2 pull resistors, R0 and R1. User can + configure those special pins. Valid arguments are described as below: + 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. + 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. + 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. + 3: (R1, R0) = (1, 1) which means R1 enabled and R0 enabled. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [0, 1, 2, 3] + + mediatek,tdsel: + description: | + An integer describing the steps for output level shifter duty + cycle when asserted (high pulse width adjustment). Valid arguments + are from 0 to 15. + $ref: /schemas/types.yaml#/definitions/uint32 + + mediatek,rdsel: + description: | + An integer describing the steps for input level shifter duty cycle + when asserted (high pulse width adjustment). Valid arguments are + from 0 to 63. + $ref: /schemas/types.yaml#/definitions/uint32 + + required: + - pinmux + +additionalProperties: false + +examples: + - | + #include + #include + soc { + #address-cells = <2>; + #size-cells = <2>; + + pio: pinctrl@1000b000 { + compatible = "mediatek,mt8365-pinctrl"; + reg = <0 0x1000b000 0 0x1000>; + mediatek,pctl-regmap = <&syscfg_pctl>; + pins-are-numbered; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + interrupts = ; + pio-pins { + pins { + pinmux = , ; + mediatek,pull-up-adv = <3>; + mediatek,drive-strength-adv = <00>; + bias-pull-up; + }; + }; + }; + }; -- 2.38.1