Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1216890rwb; Thu, 8 Dec 2022 08:02:42 -0800 (PST) X-Google-Smtp-Source: AA0mqf4qE0KQ5/rRbVLu0PdlkJq2gYLyLHyuTaRIz46z3jr6HVyml9AVt0pnw7c98OMeaADfCAct X-Received: by 2002:aa7:c44c:0:b0:46b:3549:f7ef with SMTP id n12-20020aa7c44c000000b0046b3549f7efmr41680858edr.225.1670515362260; Thu, 08 Dec 2022 08:02:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670515362; cv=none; d=google.com; s=arc-20160816; b=sUl9RTKgKh0HMxs+jQaQTK80MYBbpxsNh7vD8BziLmBeco5tja+Z1D4NMnhnn/CAgk 8wTLTf8IgiMamuOu9xbmim+X702+c+WffEkmcUPC/YiA4GVbh9prGA1+qFm0/V+FHE3y t/8xX8i/0FpAggtpvzrmmTGBrd2Nbuo/vm4b4gwwZAVG5DDCT/Gr3X+NGCbRcEeNMdD9 kYcDRhHcaTq8AriXq0CrkVAU5W+NQwat1uKaMDJcIcz/d7n+kEN+QDF+M4LiXhffAEKA c+ZlhY5jWmNuoVeqrPhUjgMQBW+KSSTYeKL+j6IVB/hjMl7UemUuiTnzJ1PI84zoKGi7 NSpw== 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=XmyXJeXOh9aIrCgjS6ftss8a4dPzBjoQogZkMKVqyWc=; b=tbXQyOOYOCx6tMP5AQCm/IOqUACi2nqhSGJJaQ3NY5/xKTx45ZwDUhFvxTN8nUoyys fXU4vi31ZDwNtP2rpoZU7r1l9l5vhvahviIDVTAD32cYi0bw+Xei9b1CiUs6iqQs/Vzi 8AWu+jUu+6xTJ3AcitOAe+MwKTM0WbrZ3UPyw+ioLIAQyc2Lvy+PnX7YUMyKWQcyQB+h xh/yRR4hrzH+9aRRzBtljT17UMhbmtvAPGEWufzht9RcBW53irPEJ47K4/SOhx+rlEl7 0bPC22DpdYes6wWuA+3fktCxFFchjGx7T2KQgbj5NTQ2cKL8zKcjFeKoAqaGkUPRUJNM F8WA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=hqrjX4Jf; 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 s11-20020a170906a18b00b007adef1fc90fsi14930729ejy.304.2022.12.08.08.02.24; Thu, 08 Dec 2022 08:02:42 -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=hqrjX4Jf; 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 S231131AbiLHPcH (ORCPT + 72 others); Thu, 8 Dec 2022 10:32:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230384AbiLHPax (ORCPT ); Thu, 8 Dec 2022 10:30:53 -0500 Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A65138C443 for ; Thu, 8 Dec 2022 07:30:47 -0800 (PST) Received: by mail-wr1-x444.google.com with SMTP id bx10so2067538wrb.0 for ; Thu, 08 Dec 2022 07:30:47 -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=XmyXJeXOh9aIrCgjS6ftss8a4dPzBjoQogZkMKVqyWc=; b=hqrjX4JfWZoBrCAot0Pdqad0u+00X9VWJckZrhwVPufe+2y50mIxI6lywOceVZThj+ EMVQMeHYlXsdRurNXflgvx/2yY/K0z67n/5UmTyMsKnlyfPr20WuF0IBCL3kgVJMpSXM 4CspMocxDypnIzhQd3iUG6tyDySfWRuLsUrfalMhn3UR8FE+oOgwMcZG4n1JsbYdb6Tf hTR7MdGKQ1F19TSfBYlovRbvzqRATKkQ02qOpJPT3uV62wSxH7K0NHVm3Cd/z9HonmEA EyFBusJ/cT7pELthYlgxfBlvK7rOWgU3wIRdT9uKSPGqSwmb2mr1NKd9DsphUBjV4cIU pHgg== 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=XmyXJeXOh9aIrCgjS6ftss8a4dPzBjoQogZkMKVqyWc=; b=e4yTr5uqbYd/k6zYLGP+uCcyKawQO9BI+/VWwYkjJCUMO+icliz/QuYUQDfM9kHI/N V5SrCK4TX6MaJdCTj+Z3tBFTfyGWLvL/27YAw5kauMW6EcmByQ/ugE2ORPj5cxkkXS01 QHr5m/9ZkkuvXcCfsIaLjccDCFvu/7jYc/jnEeus4j9CTma6pZfYlLRvazEmncI2s/6T 7pnz83gUkbfQzK6l7K9uhWb722WZQXCms6faRJ8nsIEsAMdNA0vwRMzrru55Fs0zk8gk baGoSawdwWMoTMbzv49/F3NuBUyyhT23+0XvlaY2PrjWAULORBB54sLo9sa7//LQDI0M 0Jsg== X-Gm-Message-State: ANoB5pmVI5Wm0sPk7Ap0FzgvMRHniDVJSwETx07upkRqplRgxOMlreL9 hXGLKvyGc3/pIIKbofjjegOGGQ== X-Received: by 2002:a05:6000:11cf:b0:242:2e74:7930 with SMTP id i15-20020a05600011cf00b002422e747930mr1762192wrx.10.1670513445960; Thu, 08 Dec 2022 07:30:45 -0800 (PST) Received: from predatorhelios.baylibre (laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr. [90.63.244.31]) by smtp.gmail.com with ESMTPSA id h10-20020a5d504a000000b002366553eca7sm10673239wrt.83.2022.12.08.07.30.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 08 Dec 2022 07:30:45 -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, angelogioacchino.delregno@collabora.com, khilman@baylibre.com Subject: [PATCH v4 4/7] dt-bindings: pinctrl: add bindings for Mediatek MT8365 SoC Date: Thu, 8 Dec 2022 16:30:37 +0100 Message-Id: <20221208153041.3965378-5-bero@baylibre.com> X-Mailer: git-send-email 2.38.1 In-Reply-To: <20221208153041.3965378-1-bero@baylibre.com> References: <20221208153041.3965378-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=unavailable 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 | 197 ++++++++++++++++++ 1 file changed, 197 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..9560e1d2898d0 --- /dev/null +++ b/Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml @@ -0,0 +1,197 @@ +# 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. + + 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 + +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>; + 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; + }; + }; + }; + }; + +required: + - compatible + - reg + - gpio-controller + - "#gpio-cells" + +allOf: + - $ref: pinctrl.yaml# -- 2.38.1