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=-13.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY, USER_AGENT_SANE_2 autolearn=unavailable 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 39D02C3567B for ; Mon, 24 Feb 2020 08:46:36 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 022DF20828 for ; Mon, 24 Feb 2020 08:46:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="EWdbmfct"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=mediatek.com header.i=@mediatek.com header.b="iiH3PAIE" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 022DF20828 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=mediatek.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Date:To:From:Subject:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Y/U8qv994NypwcisBTloVmx+u7ebMFWLAQUuk2L1KfM=; b=EWdbmfct7gRCXv UNmQv3anvZa21cefYQPmR73h8TpkY2mndGZr+BTMUMYTv5LSqeu5t6o981ieDVt7/4EqED+tOFBbO itZbF4aKVC7gG12h/Y3VAZdJeR8yEI6k1RwH8lb1My5yo4bjHKrowFlrNnhfnF3LIYfQnL+ls0Ou7 1BwwWJFZGLO0dfRrg+e5+14QYebkm+6ptIlddF0VTm9zH5jDFVVOLJl8JYTrpn048Xo8ydnqkinxL BcVaLxFbkMzdQF4QgqLXVeAwwE8hnSESmW2x1QgaGT42SC9bYZwLJB8MvIdR54KECLogg2jxelLoe NDtcxnQz3TD7FIeLEs3A==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1j69Nr-0003oP-KN; Mon, 24 Feb 2020 08:46:35 +0000 Received: from mailgw01.mediatek.com ([216.200.240.184]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1j69Nm-0003mF-Tu; Mon, 24 Feb 2020 08:46:34 +0000 X-UUID: aa9775777c5444fb95d54e4cc1a23bfe-20200224 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mediatek.com; s=dk; h=Content-Transfer-Encoding:MIME-Version:Content-Type:References:In-Reply-To:Date:CC:To:From:Subject:Message-ID; bh=ucwhUjhwtXJ7fomoy+TbQYpZVLRcyud+cUdXEQuJ3Mw=; b=iiH3PAIEkFzFwIci+IKErSH9RGG4s3HsUgyJ3C11MY4TDwR+IL482XiFT0x87OM742CNXyv0z9eyF6xYFm9moaLwe10IOxyqAauNKuJVjLqq9jxoHShr9PIOnTHWTDg7H1Cf06xQ6envjtcTDsyJpf4vHpLmYX2hq73y+GRAbqg=; X-UUID: aa9775777c5444fb95d54e4cc1a23bfe-20200224 Received: from mtkcas66.mediatek.inc [(172.29.193.44)] by mailgw01.mediatek.com (envelope-from ) (musrelay.mediatek.com ESMTP with TLS) with ESMTP id 163051272; Mon, 24 Feb 2020 00:46:25 -0800 Received: from MTKMBS07N2.mediatek.inc (172.21.101.141) by MTKMBS62N2.mediatek.inc (172.29.193.42) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 24 Feb 2020 00:47:25 -0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs07n2.mediatek.inc (172.21.101.141) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 24 Feb 2020 16:45:34 +0800 Received: from [172.21.77.4] (172.21.77.4) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Mon, 24 Feb 2020 16:46:39 +0800 Message-ID: <1582533982.12922.5.camel@mtksdaap41> Subject: Re: [PATCH v6 1/4] dt-bindings: display: mediatek: update dpi supported chips From: CK Hu To: Jitao Shi Date: Mon, 24 Feb 2020 16:46:22 +0800 In-Reply-To: <20200221112828.55837-2-jitao.shi@mediatek.com> References: <20200221112828.55837-1-jitao.shi@mediatek.com> <20200221112828.55837-2-jitao.shi@mediatek.com> X-Mailer: Evolution 3.10.4-0ubuntu2 MIME-Version: 1.0 X-MTK: N X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200224_004630_984340_14377D57 X-CRM114-Status: GOOD ( 14.45 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Mark Rutland , devicetree@vger.kernel.org, bibby.hsieh@mediatek.com, srv_heupstream@mediatek.com, David Airlie , huijuan.xie@mediatek.com, stonea168@163.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, cawa.cheng@mediatek.com, Rob Herring , linux-mediatek@lists.infradead.org, Daniel Vetter , Matthias Brugger , yingjoe.chen@mediatek.com, eddie.huang@mediatek.com, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi, Jitao: On Fri, 2020-02-21 at 19:28 +0800, Jitao Shi wrote: > Add decriptions about supported chips, including MT2701 & MT8173 & > mt8183 > > 1. Add more chips support. ex. MT2701 & MT8173 & MT8183 > 2. Add property "dpi_pin_mode_swap" and "pinctrl-names" gpio mode dpi mode and > gpio oupput-low to avoid leakage current. > 3. Add property "dpi_dual_edge" to config the dpi pin output mode dual edge or > single edge sample data. > > Signed-off-by: Jitao Shi > --- > .../bindings/display/mediatek/mediatek,dpi.txt | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.txt b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.txt > index b6a7e7397b8b..cd6a1469c8b7 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.txt > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.txt > @@ -7,6 +7,7 @@ output bus. > > Required properties: > - compatible: "mediatek,-dpi" > + the supported chips are mt2701 , mt8173 and mt8183. > - reg: Physical base address and length of the controller's registers > - interrupts: The interrupt signal from the function block. > - clocks: device clocks > @@ -16,6 +17,11 @@ Required properties: > Documentation/devicetree/bindings/graph.txt. This port should be connected > to the input port of an attached HDMI or LVDS encoder chip. > > +Optional properties: > +- dpi_pin_mode_swap: Swap the pin mode between dpi mode and gpio mode. > +- pinctrl-names: Contain "gpiomode" and "dpimode". > +- dpi_dual_edge: Control the RGB 24bit data on 12 pins or 24 pins. I've find that in [1], there are already a property of "pclk-sample" which like this, but it only have rising (1) or falling (0) status. Does that property describe the same thing with this property? If they are the same, I think you should add new state, dual (2), for "pclk-sample". [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/media/video-interfaces.txt?h=v5.6-rc3 Regards, CK > + > Example: > > dpi0: dpi@1401d000 { > @@ -26,6 +32,11 @@ dpi0: dpi@1401d000 { > <&mmsys CLK_MM_DPI_ENGINE>, > <&apmixedsys CLK_APMIXED_TVDPLL>; > clock-names = "pixel", "engine", "pll"; > + dpi_dual_edge; > + dpi_pin_mode_swap; > + pinctrl-names = "gpiomode", "dpimode"; > + pinctrl-0 = <&dpi_pin_gpio>; > + pinctrl-1 = <&dpi_pin_func>; > > port { > dpi0_out: endpoint { _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel