From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,UNPARSEABLE_RELAY, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 78B34C43382 for ; Wed, 26 Sep 2018 02:38:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EDEE8208E4 for ; Wed, 26 Sep 2018 02:38:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EDEE8208E4 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mediatek.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726319AbeIZItD (ORCPT ); Wed, 26 Sep 2018 04:49:03 -0400 Received: from mailgw02.mediatek.com ([210.61.82.184]:44110 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726010AbeIZItC (ORCPT ); Wed, 26 Sep 2018 04:49:02 -0400 X-UUID: 1d73e25c5bca42209826baf8166672cb-20180926 Received: from mtkcas07.mediatek.inc [(172.21.101.84)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 342863482; Wed, 26 Sep 2018 10:38:20 +0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs02n1.mediatek.inc (172.21.101.77) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 26 Sep 2018 10:38:18 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Wed, 26 Sep 2018 10:38:18 +0800 Message-ID: <1537929498.32631.16.camel@mtkswgap22> Subject: Re: [Resend PATCH 5/5] arm: dts: mt7623: add display subsystem related device nodes From: Ryder Lee To: CK Hu CC: Matthias Brugger , Rob Herring , Sean Wang , Roy Luo , Weijie Gao , , , , , chunhui dai , Bibby Hsieh Date: Wed, 26 Sep 2018 10:38:18 +0800 In-Reply-To: <1537925879.20118.3.camel@mtksdaap41> References: <84011aa94dd7be9239b7a2f944dd30fc70568fbb.1536155449.git.ryder.lee@mediatek.com> <7105c341de3525761ad4067ca57c641c7097f773.1536155449.git.ryder.lee@mediatek.com> <1537925879.20118.3.camel@mtksdaap41> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2018-09-26 at 09:37 +0800, CK Hu wrote: > Hi, Ryder: > > On Wed, 2018-09-05 at 22:09 +0800, Ryder Lee wrote: > > Add display subsystem related device nodes for MT7623. > > > > Cc: CK Hu > > Signed-off-by: chunhui dai > > Signed-off-by: Bibby Hsieh > > Signed-off-by: Ryder Lee > > --- > > I forgot to sort nodes in my previous mail. Sorry for the inconvenience. > > > > This patch depends on the series: https://lkml.org/lkml/2018/9/5/223 > > > > @Matthias, > > I know you're working on broken MMSYS - just want to ask whether it's possible > > to let the patch to go to your tree (if others are okay with it), and send a > > fixup one for MT7623 MMSYS later? > > --- > > arch/arm/boot/dts/mt7623.dtsi | 177 ++++++++++++++++++++++++++ > > arch/arm/boot/dts/mt7623n-bananapi-bpi-r2.dts | 83 ++++++++++++ > > arch/arm/boot/dts/mt7623n-rfb-emmc.dts | 83 ++++++++++++ > > 3 files changed, 343 insertions(+) > > > > diff --git a/arch/arm/boot/dts/mt7623.dtsi b/arch/arm/boot/dts/mt7623.dtsi > > index d01bdee..fdf9078 100644 > > --- a/arch/arm/boot/dts/mt7623.dtsi > > +++ b/arch/arm/boot/dts/mt7623.dtsi > > @@ -23,6 +23,11 @@ > > #address-cells = <2>; > > #size-cells = <2>; > > > > + aliases { > > + rdma0 = &rdma0; > > + rdma1 = &rdma1; > > + }; > > + > > cpu_opp_table: opp-table { > > compatible = "operating-points-v2"; > > opp-shared; > > @@ -311,6 +316,25 @@ > > clock-names = "spi", "wrap"; > > }; > > > > + mipi_tx0: mipi-dphy@10010000 { > > + compatible = "mediatek,mt7623-mipi-tx", > > + "mediatek,mt2701-mipi-tx"; > > + reg = <0 0x10010000 0 0x90>; > > + clocks = <&clk26m>; > > + clock-output-names = "mipi_tx0_pll"; > > + #clock-cells = <0>; > > + #phy-cells = <0>; > > + }; > > + > > + cec: cec@10012000 { > > + compatible = "mediatek,mt7623-cec", > > + "mediatek,mt8173-cec"; > > + reg = <0 0x10012000 0 0xbc>; > > + interrupts = ; > > + clocks = <&infracfg CLK_INFRA_CEC>; > > + status = "disabled"; > > + }; > > + > > cir: cir@10013000 { > > compatible = "mediatek,mt7623-cir"; > > reg = <0 0x10013000 0 0x1000>; > > @@ -359,6 +383,18 @@ > > #clock-cells = <1>; > > }; > > > > + hdmi_phy: phy@10209100 { > > + compatible = "mediatek,mt7623-hdmi-phy", > > + "mediatek,mt2701-hdmi-phy"; > > + reg = <0 0x10209100 0 0x24>; > > + clocks = <&apmixedsys CLK_APMIXED_HDMI_REF>; > > + clock-names = "pll_ref"; > > + clock-output-names = "hdmitx_dig_cts"; > > + #clock-cells = <0>; > > + #phy-cells = <0>; > > + status = "disabled"; > > + }; > > + > > rng: rng@1020f000 { > > compatible = "mediatek,mt7623-rng"; > > reg = <0 0x1020f000 0 0x1000>; > > @@ -558,6 +594,16 @@ > > status = "disabled"; > > }; > > > > + hdmiddc0: i2c@11013000 { > > + compatible = "mediatek,mt7623-hdmi-ddc", > > + "mediatek,mt8173-hdmi-ddc"; > > + interrupts = ; > > + reg = <0 0x11013000 0 0x1C>; > > + clocks = <&pericfg CLK_PERI_I2C3>; > > + clock-names = "ddc-i2c"; > > + status = "disabled"; > > + }; > > + > > nor_flash: spi@11014000 { > > compatible = "mediatek,mt7623-nor", > > "mediatek,mt8173-nor"; > > @@ -732,6 +778,84 @@ > > #clock-cells = <1>; > > }; > > > > + display_components: dispsys@14000000 { > > + compatible = "mediatek,mt7623-mmsys", > > Checkpatch warning: > > WARNING: DT compatible string "mediatek,mt7623-mmsys" appears > un-documented -- check ./Documentation/devicetree/bindings/ > #101: FILE: arch/arm/boot/dts/mt7623.dtsi:782: > + compatible = "mediatek,mt7623-mmsys", > > > > + "mediatek,mt2701-mmsys"; > > + reg = <0 0x14000000 0 0x1000>; > > + power-domains = <&scpsys MT2701_POWER_DOMAIN_DISP>; > > + }; > > + > > + ovl@14007000 { > > + compatible = "mediatek,mt7623-disp-ovl", > > I think this is also un-documented, but I don't know why checkpatch does > not show any warning. > > Regards, > CK > > + "mediatek,mt2701-disp-ovl"; > > + reg = <0 0x14007000 0 0x1000>; > > + interrupts = ; > > + clocks = <&mmsys CLK_MM_DISP_OVL>; > > + iommus = <&iommu MT2701_M4U_PORT_DISP_OVL_0>; > > + mediatek,larb = <&larb0>; > > + }; > > + I fallback to use the MT2701's compatible string here and there, but I could add a new one for MT7623. BTW, I've had this question for a long time - should I add a new compatible for the very same IPs, or could we just use the old one in DTS? Ryder