Received: by 2002:a05:7412:419a:b0:f3:1519:9f41 with SMTP id i26csp149277rdh; Wed, 22 Nov 2023 22:57:27 -0800 (PST) X-Google-Smtp-Source: AGHT+IG+t4b19DmwZDiM9sSWpx97vLFulQTSKgUH9QnbPZhNlz2pFW/8wYGbXjvCo//po74sa34f X-Received: by 2002:a9d:67c1:0:b0:6d7:e216:35bd with SMTP id c1-20020a9d67c1000000b006d7e21635bdmr5683382otn.11.1700722647031; Wed, 22 Nov 2023 22:57:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1700722646; cv=none; d=google.com; s=arc-20160816; b=JBWSc3exAq/+CktTyKPF/gni3eXzxC8y9QqnWvgXGl9eb+gcNgv7hg7hfmCoO4/zRg 0CjPbnxOhjhCDX4WHiCqaPOncY2Pp9LpXK4m15+dyy0VvWSX84AmEWkAU9TOaiAEsGXA osrM+XMPv5yTvTWxwDnyO/e2muT/o+xKrQ4jxEHDDK33DO5fyblR7ybQ1r4pZsYjP3xw vYCwKRq1E2B1svv6qGjaIGs5ZzWYeK1kiAYT/yUUfYb5FrviPzuAcCYL1nGflAO/sBmQ OjabYcn4MZ3lgKOB7zpqMsCdeE2/OQxpYQV+gYhjySXx8sJbVpcXhe1TbTndbbgJMXNo juow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=BsODPOSIN4yzP+0hqmAk4agbyOkIjH9Kys+jY9V1shc=; fh=Vs/EbCObreW9rnwDKNorsFEZvQy2LpgO3uqzi4vhobw=; b=wyDUg1MigPaHEwi7aVu5pG/G9N9uBqWtgtIGQY8/sZCjYppAvyFXs8finPZskKgouw m5om+xbfUh6Qu9gVUrp3Lh6p8wROiU3TYToKAV3SMfRiV2fQlg3VG6KBfYRUI/Ah1Uji VEPas70w2/HvIjeqT15fcJJzpmPwuy7n/qqlp0KGCQKfgZayQis06eu92ca/ZRFmTDrP IWvTIvvIOh5yTHmS6MCLxRY9xjVU5iValy7FEBWghZmrsDcT886ZfnH/IuIzBdW5SfDr C33hjYk4DNYW66zKP1E3jgOF6Cm8Yx+v2GdURysL/h7NjgXNE/mSrPQRm15xtH+WAx5I YVpA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from groat.vger.email (groat.vger.email. [23.128.96.35]) by mx.google.com with ESMTPS id u31-20020a63471f000000b005b967ddd984si744080pga.781.2023.11.22.22.57.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Nov 2023 22:57:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 229A2801D288; Wed, 22 Nov 2023 22:57:24 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231571AbjKWG44 (ORCPT + 99 others); Thu, 23 Nov 2023 01:56:56 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43902 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231127AbjKWG4z (ORCPT ); Thu, 23 Nov 2023 01:56:55 -0500 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA2C2CB; Wed, 22 Nov 2023 22:56:55 -0800 (PST) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id D8AAF8082; Thu, 23 Nov 2023 14:56:46 +0800 (CST) Received: from EXMBX171.cuchost.com (172.16.6.91) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 23 Nov 2023 14:56:46 +0800 Received: from [192.168.125.70] (183.27.97.46) by EXMBX171.cuchost.com (172.16.6.91) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 23 Nov 2023 14:56:45 +0800 Message-ID: Date: Thu, 23 Nov 2023 14:53:36 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v1 1/2] dt-bindings: phy: Add starfive,jh7110-dphy-tx Content-Language: en-US To: Rob Herring CC: , , , , , , , , , , , , References: <20231117130421.79261-1-shengyang.chen@starfivetech.com> <20231117130421.79261-2-shengyang.chen@starfivetech.com> <20231119160938.GA269430-robh@kernel.org> From: Shengyang Chen In-Reply-To: <20231119160938.GA269430-robh@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [183.27.97.46] X-ClientProxiedBy: EXCAS064.cuchost.com (172.16.6.24) To EXMBX171.cuchost.com (172.16.6.91) X-YovoleRuleAgent: yovoleflag X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Wed, 22 Nov 2023 22:57:24 -0800 (PST) Dear Rob, Thank you for your review and comment On 2023/11/20 0:09, Rob Herring wrote: > On Fri, Nov 17, 2023 at 09:04:20PM +0800, Shengyang Chen wrote: >> StarFive SoCs like the jh7110 use a MIPI D-PHY TX >> controller based on a M31 IP. Add a binding for it. >> >> Signed-off-by: Shengyang Chen >> --- >> .../bindings/phy/starfive,jh7110-dphy-tx.yaml | 74 +++++++++++++++++++ >> 1 file changed, 74 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-tx.yaml >> >> diff --git a/Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-tx.yaml b/Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-tx.yaml >> new file mode 100644 >> index 000000000000..850fe2e61d1d >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/phy/starfive,jh7110-dphy-tx.yaml >> @@ -0,0 +1,74 @@ >> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/phy/starfive,jh7110-dphy-tx.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: Starfive SoC MIPI D-PHY Tx Controller >> + >> +maintainers: >> + - Keith Zhao >> + - Shengyang Chen >> + >> +description: >> + The Starfive SoC uses the MIPI DSI D-PHY based on M31 IP to transfer >> + DSI data. >> + >> +properties: >> + compatible: >> + const: starfive,jh7110-dphy-tx >> + >> + reg: >> + maxItems: 1 >> + >> + clocks: >> + maxItems: 1 >> + >> + clock-names: >> + items: >> + - const: dphy_txesc > > Module name is redundant. Drop 'dphy_'. > OK, will drop "dphy_". >> + >> + resets: >> + items: >> + - description: DSITX_TXBYTEHS reset >> + - description: MIPITX_DPHY_SYS reset >> + - description: MIPITX_DPHY_TXBYTEHS reset >> + >> + reset-names: >> + items: >> + - const: dsi_txbytehs >> + - const: dphy_sys >> + - const: dphy_txbytehs > > Drop 'dphy_'. > OK, will drop "dphy_". > Is 'dsi_txbytehs' really a part of the DPHY block? Sounds like it is > part of the DSI block. If so, the reset belongs there. If the phy driver > needs it, then it needs to go find the DSI block and get its reset. > "dsi_txbytehs" is a reset of DSI block, it will be put back to DSI block and remove from DPHY block. >> + >> + power-domains: >> + maxItems: 1 >> + >> + "#phy-cells": >> + const: 0 >> + >> +required: >> + - compatible >> + - reg >> + - clocks >> + - clock-names >> + - resets >> + - reset-names >> + - power-domains >> + - "#phy-cells" >> + >> +additionalProperties: false >> + >> +examples: >> + - | >> + phy@295e0000 { >> + compatible = "starfive,jh7110-dphy-tx"; >> + reg = <0x295e0000 0x10000>; >> + clocks = <&voutcrg 14>; >> + clock-names = "dphy_txesc"; >> + resets = <&syscrg 7>, >> + <&syscrg 10>, >> + <&syscrg 11>; >> + reset-names = "dsi_txbytehs", "dphy_sys", "dphy_txbytehs"; >> + power-domains = <&aon_syscon 0>; >> + #phy-cells = <0>; >> + }; >> -- >> 2.17.1 >> thanks a lot. Best Regards, Shengyang