Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp591454iog; Thu, 30 Jun 2022 06:39:41 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sWQkjecFatQOPqQLO34HdvMTDVG80C96Jzzo8KghwRlcbH0BfwWQHe9lZssAodxE+slE7L X-Received: by 2002:a05:6402:1c09:b0:435:6562:e70d with SMTP id ck9-20020a0564021c0900b004356562e70dmr11460189edb.203.1656596381091; Thu, 30 Jun 2022 06:39:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656596381; cv=none; d=google.com; s=arc-20160816; b=hmHGcXXGlTrRTThdUgwRnG5yAUSFvfdY3LwjQtqyh0d2Go9YYZqPn8sp64tOn6rOF1 4H3l1kvhR+xX9yx5farzkwZpKnRoKPBnJ9aVtTMk4QR6NTzEQb12KWWGtlEwJGtPpphm cJmxtIn8UQvYfrL9eOEs9vB9RU/sJHi2wBHle+7lvNRnTuD7MG4YlfGnGEIIHhcYVzog p0AWmqYfGrPEhLwi6ftJYYT6TnOQtclSQ2PJ/qxo+fuMUs9OXlqtQhVlbKfUJVn4tScI VQ4Ug5ER75CyupJqPCvCzguMkYaHtmHNFvg7JV4khMgbhmoXjm5AVpnvOEUGFDOIBVRC hdMA== 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=mqT3VAD11E9Jb9u7Ydy2F8EEDfqA9QbzAVg9N22YokM=; b=BxgHWijdQC0BQeonVIufDhny1XEUCz7LkpuVznUzFtORs3GDZ/hDGnJwXg5nw2tQhj sC0YDmUtz0NKpcYacqfluHLVYDLZNsW8ArTPFiUmPKQbCNkd3UQRx/909elwf8gnbxxs mkVdJIEGWasN07U2u2M/mgotzZbyLwycsE8NQcJ4dMKZ8ut/BVFQ6E6K/TLvehK/4dzM 735+tsi72rTCvv17TLvl1IbEqEIEv38FrKkshkzaTBtMSdaBZv4y7NXxAegkv6ZoRUpJ WAgezschY8w8IZvkXFc/huHLb/fRjRQi0QuXeqsh6jtu//YaPqMsdpDZh9YaQFXn2+Xd XoGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@collabora.com header.s=mail header.b=P2utmyG7; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hu9-20020a170907a08900b006ff492dc350si25031102ejc.378.2022.06.30.06.39.15; Thu, 30 Jun 2022 06:39:41 -0700 (PDT) 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=@collabora.com header.s=mail header.b=P2utmyG7; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235257AbiF3NPw (ORCPT + 99 others); Thu, 30 Jun 2022 09:15:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52278 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230305AbiF3NPv (ORCPT ); Thu, 30 Jun 2022 09:15:51 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3EA66D65; Thu, 30 Jun 2022 06:15:50 -0700 (PDT) Received: from IcarusMOD.eternityproject.eu (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id 30561660193B; Thu, 30 Jun 2022 14:15:48 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1656594948; bh=mXj0tGABrhs2twtkLJTs6KED1Ej73CKEqHJRlvIRmkQ=; h=From:To:Cc:Subject:Date:From; b=P2utmyG7OaeInNeQPLF5I3L8zASXrtlmlz7Gh2pENo0iUGqD7Xaq2wm9JhWybtmT/ UZhvCidCb3wDIkGJYdceOMgAy8JHx1gz7DdS7jqeSjouAtWXh+3w54VOIM662NefbW 7ctAinBcUWFp5X0q2I8Tw4EQSTniH7JsfTX3lTsZQdhjUE2Vo2QavgS0Djb5tQzgQA SHf97WvIaPfx63+EI7EUr/0AKioAkrD6ZDdtq7GQ9f3Bl6JFOoZTOvJWk64RpSlQy1 3Fq7/r2ngpYhEUOios4dWrsm6NVQf6bZ/rxPn4jidC6xnplF/Kyb+tmlLWDQus41qi 4Un286oT62mQw== From: AngeloGioacchino Del Regno To: linus.walleij@linaro.org Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com, sean.wang@mediatek.com, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, nfraprado@collabora.com, AngeloGioacchino Del Regno Subject: [PATCH] dt-bindings: pinctrl: mt8195: Add and use drive-strength-microamp Date: Thu, 30 Jun 2022 15:15:43 +0200 Message-Id: <20220630131543.225554-1-angelogioacchino.delregno@collabora.com> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE 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 As was already done for MT8192 in commit b52e695324bb ("dt-bindings: pinctrl: mt8192: Add drive-strength-microamp"), replace the custom mediatek,drive-strength-adv property with the standardized pinconf 'drive-strength-microamp' one. Similarly to the mt8192 counterpart, there's no user of property 'mediatek,drive-strength-adv', hence removing it is safe. Fixes: 69c3d58dc187 ("dt-bindings: pinctrl: mt8195: Add mediatek,drive-strength-adv property") Signed-off-by: AngeloGioacchino Del Regno --- .../bindings/pinctrl/pinctrl-mt8195.yaml | 27 ++----------------- 1 file changed, 2 insertions(+), 25 deletions(-) diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml index b0fea44403e7..85e96a5e1708 100644 --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8195.yaml @@ -100,31 +100,8 @@ patternProperties: drive-strength: enum: [2, 4, 6, 8, 10, 12, 14, 16] - 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] + drive-strength-microamp: + enum: [125, 250, 500, 1000] bias-pull-down: oneOf: -- 2.35.1