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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C01D4C433EF for ; Wed, 30 Mar 2022 05:14:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=BYBNmumQdfh0oj7Xy7EzwNjn3Mn89YS9onHqoh+l1K4=; b=G66TK/NeatHIGS FW5wD71MMW4L7nFlhXxf/sLr7DJCOa0Zx1iEgDRF7fv9WhddWOKvvf6uSf5tsni/jn5MKWQ+fNIec SBREJhxBsgUQJff0bBm/Il6qgyTo2p6GIfwn0qauJaBcZnIrq/LDCR36Z/eGGCqBx2NfvsWhEKjrF pgC5OzEFu9qdBlI1Y8U1/wE4ygO4V4BuQiICGSoFbtMs6WaJupW8uiLvnW5HDz5MGyrNLTyVBhwud IjTJ3DKmCj9MMxiEmXVWM5Zn/tBrEg238aonTlCrNQ2NQ1hcEplilEwtsjQy3GUAefosNYnCmbAhv gChhV2zSIS4Aal14SBsQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nZQdx-00EF1V-3b; Wed, 30 Mar 2022 05:13:17 +0000 Received: from mailgw02.mediatek.com ([216.200.240.185]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nZQdj-00EExE-MC; Wed, 30 Mar 2022 05:13:05 +0000 X-UUID: 714d1c6de51d44a0ab86329b4d530516-20220329 X-UUID: 714d1c6de51d44a0ab86329b4d530516-20220329 Received: from mtkcas68.mediatek.inc [(172.29.94.19)] by mailgw02.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLSv1.2 ECDHE-RSA-AES256-SHA384 256/256) with ESMTP id 1612614371; Tue, 29 Mar 2022 22:11:42 -0700 Received: from mtkexhb01.mediatek.inc (172.21.101.102) by MTKMBS62N1.mediatek.inc (172.29.193.41) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 29 Mar 2022 22:11:40 -0700 Received: from mtkcas10.mediatek.inc (172.21.101.39) by mtkexhb01.mediatek.inc (172.21.101.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 30 Mar 2022 13:11:38 +0800 Received: from mtksdccf07.mediatek.inc (172.21.84.99) by mtkcas10.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Wed, 30 Mar 2022 13:11:38 +0800 From: Miles Chen To: CC: , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v9 01/22] dt-bindings: mediatek, dpi: Add DP_INTF compatible Date: Wed, 30 Mar 2022 13:11:38 +0800 Message-ID: <20220330051138.19264-1-miles.chen@mediatek.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20220327223927.20848-2-granquet@baylibre.com> References: <20220327223927.20848-2-granquet@baylibre.com> MIME-Version: 1.0 X-MTK: N X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220329_221303_739453_09920A8F X-CRM114-Status: GOOD ( 13.05 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Guillaume, >DP_INTF is similar to DPI but does not have the exact same feature set >or register layouts. > >DP_INTF is the sink of the display pipeline that is connected to the >DisplayPort controller and encoder unit. It takes the same clocks as >DPI. > >Signed-off-by: Markus Schneider-Pargmann >Signed-off-by: Guillaume Ranquet >Reviewed-by: Rob Herring >--- > .../bindings/display/mediatek/mediatek,dpi.yaml | 11 ++++++----- > 1 file changed, 6 insertions(+), 5 deletions(-) > >diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml >index dd2896a40ff0..2dba80ad3b18 100644 >--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml >+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml >@@ -4,16 +4,16 @@ > $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > >-title: mediatek DPI Controller Device Tree Bindings >+title: mediatek DPI/DP_INTF Controller ^^^^^^^^ Would you mind changing this 'mediatek' to 'MediaTek'? > > maintainers: > - CK Hu > - Jitao shi > > description: | >- The Mediatek DPI function block is a sink of the display subsystem and > s/Mediatek/MediaTek/ Could you replace all 'Mediatek' with 'MediaTek' of this series, please? We have set up a chcker inside our organization to capture this case, hopefully we will see less 'Mediatek' in the future. >- provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel >- output bus. >+ The Mediatek DPI and DP_INTF function blocks are a sink of the display s/Mediatek/MediaTek/ thanks, Miles >+ subsystem and provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a >+ parallel output bus. > > properties: > compatible: >@@ -23,6 +23,7 @@ properties: > - mediatek,mt8173-dpi > - mediatek,mt8183-dpi > - mediatek,mt8192-dpi >+ - mediatek,mt8195-dpintf > > reg: > maxItems: 1 >@@ -54,7 +55,7 @@ properties: > $ref: /schemas/graph.yaml#/properties/port > description: > Output port node. This port should be connected to the input port of an >- attached HDMI or LVDS encoder chip. >+ attached HDMI, LVDS or DisplayPort encoder chip. > > required: > - compatible >-- >2.34.1 > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel