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.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,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 A2D38C34021 for ; Mon, 17 Feb 2020 17:43:13 +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 35EDC20725 for ; Mon, 17 Feb 2020 17:43:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="TavjCbzb"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=cerno.tech header.i=@cerno.tech header.b="b0JTk3fp"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="1i5/8d8U" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 35EDC20725 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=cerno.tech 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-Type:Cc: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=unksTk8n+/qG6jj+uG6Pg25l67HNQ6v/c5nUG07nfSs=; b=TavjCbzbTqVOypNPxIIYl+8L0 v/dQZ4sfRKV1pxqrXrbaTlsfF4q+DqWMWW9FVwa4UhO8eWy1tXmj6OTI6XpEALiz18ClUZ0I6IoU9 ZINV0mGKCdszbuNLTKQkLG/X2PB7etm4Wh2dQxu1DHkPSEwWJXODbFxWs2Ng+nlhRUkIlM6Q8wSGh kR+h8IS8ZfhHrKahnscAXFX4MPgCC5P+4w9/d5A05nUipZXn1EXZd8Oe+g+q7Uq0Npuj+ElTxknni 3q8xQklyBcr/QbVDtwJh5MTTB7n4jj1DuL99Kvgtq6VqGG9bx4OQkAxHBOK2Zrw7Pr9ROpJwtdBmM AprZazjXA==; 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 1j3kQE-0002Bf-6M; Mon, 17 Feb 2020 17:43:06 +0000 Received: from new2-smtp.messagingengine.com ([66.111.4.224]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1j3kQ9-00023a-BA for linux-arm-kernel@lists.infradead.org; Mon, 17 Feb 2020 17:43:03 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 1AB224876; Mon, 17 Feb 2020 12:42:58 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 17 Feb 2020 12:42:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cerno.tech; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=LSh1lPCDqxLO7Bib4LTPMBWDfsX YnGwYBlDhYAcksF8=; b=b0JTk3fpnH2iEvcdnGSPGCzgWS4ca+cN7nDmuXFsV0S OWEG8L1FS5bSt1/CHbIkkdxHibHJxYdUO7LrBCLKNKlHy4it36RSWB949z4snssM v53A4n2KRwrX9EfFHyvAC5gcBqLJQ/B+nYuC71HgWY3dHQrr6QCbNg2RnX3kS+PP ONrQjLxRmBcJAeXzuQOtn8tK3rCvxi/t57k6oNBsgSTQvIiKgdfVexO8eMq5lPx+ m3tHPtkSbxlU+WmLc2CrnF893fgsHBLCfA5CeHNNuB/HmC+oD8y0SlxLmuLSAPpW qpoGETK0LWPyIBPUyK0CCT4fklQqdLXrBS0ziJPX7Sg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=LSh1lP CDqxLO7Bib4LTPMBWDfsXYnGwYBlDhYAcksF8=; b=1i5/8d8UeLz8dClE3oGsmn lFQr0W0jozQM1AAid1YGPD1CEsNlvn0Qn0e469lXKMFAUbiCznsko4L4EByFfmMG 79v3hlIoF13qUGbNSbaAN/Ii/Feiw67Esxb8tAtZB5XfEu+ODbde4dtwafketsmD ztJhHaOohxXo98uiFwDvjaqff1o6KOhYGRuJlcsBsVSa5kCl6kc6ieytjx3ZEofj SNvgh7HGN2jt/pMwx9IE0l+Ce2mAFfMfSmXvZKzi0N7sQgOaJeZAzTNolnZaz6RP NNJcUUSdsEG/j6BUqLYp/cK+hmnteBqlaiR6ZfAyeC5ET5rFgQlSGwXd10juoJ1w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrjeeigddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpeforgigihhm vgcutfhiphgrrhguuceomhgrgihimhgvsegtvghrnhhordhtvggthheqnecukfhppeeltd drkeelrdeikedrjeeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepmhgrgihimhgvsegtvghrnhhordhtvggthh X-ME-Proxy: Received: from localhost (lfbn-tou-1-1502-76.w90-89.abo.wanadoo.fr [90.89.68.76]) by mail.messagingengine.com (Postfix) with ESMTPA id B8A8B328005D; Mon, 17 Feb 2020 12:42:54 -0500 (EST) Date: Mon, 17 Feb 2020 18:42:53 +0100 From: Maxime Ripard To: Laurent Pinchart Subject: Re: [PATCH 1/2] dt-bindings: display: sun4i-tcon: Add LVDS Dual Link property Message-ID: <20200217174253.mj53us4bb7h2lyca@gilmour.lan> References: <20200214123244.109300-1-maxime@cerno.tech> <20200214131025.GI4831@pendragon.ideasonboard.com> <20200214154405.f5zuicm6uhhiczfs@gilmour.lan> <20200214154953.GJ4831@pendragon.ideasonboard.com> MIME-Version: 1.0 In-Reply-To: <20200214154953.GJ4831@pendragon.ideasonboard.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200217_094301_833552_145F80E4 X-CRM114-Status: GOOD ( 21.99 ) 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, David Airlie , Maarten Lankhorst , dri-devel@lists.freedesktop.org, Chen-Yu Tsai , Rob Herring , Sean Paul , Daniel Vetter , Frank Rowand , linux-arm-kernel@lists.infradead.org Content-Type: multipart/mixed; boundary="===============8630966084141635644==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============8630966084141635644== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qacjjsbo4tknjumh" Content-Disposition: inline --qacjjsbo4tknjumh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Feb 14, 2020 at 05:49:53PM +0200, Laurent Pinchart wrote: > On Fri, Feb 14, 2020 at 04:44:05PM +0100, Maxime Ripard wrote: > > On Fri, Feb 14, 2020 at 03:10:25PM +0200, Laurent Pinchart wrote: > > > On Fri, Feb 14, 2020 at 01:32:43PM +0100, Maxime Ripard wrote: > > > > SoCs that have multiple TCONs can use the two set of pins on the first TCON > > > > to drive a dual-link display. Add a property to enable the dual link. > > > > > > > > Signed-off-by: Maxime Ripard > > > > --- > > > > .../bindings/display/allwinner,sun4i-a10-tcon.yaml | 7 +++++++ > > > > 1 file changed, 7 insertions(+) > > > > > > > > diff --git a/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml b/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml > > > > index 86ad617d2327..aa6dd8409dbc 100644 > > > > --- a/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml > > > > +++ b/Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tcon.yaml > > > > @@ -105,6 +105,13 @@ properties: > > > > - const: edp > > > > - const: lvds > > > > > > > > + allwinner,lvds-dual-link: > > > > + type: boolean > > > > + description: | > > > > + On a SoC with two TCON with LVDS support, the first TCON can > > > > + operate over both pins sets to output in a dual-link setup. This > > > > + will be triggered by setting this property. > > > > > > Could you maybe provide an example of how this property is supposed to > > > be used ? I'm especially wondering what ports are used in that case and > > > how they're connected. > > > > It's pretty trivial to support, it's only a property to set on the > > encoder node itself. > > > > I'm not really sure what you meant by your question with the ports > > though :/ > > I assume that, in the single-link case, you have two TCON instances that > operate independently, each of them with one port that models an LVDS > connection to a panel. Indeed, > In the dual-link mode, how does that look like ? Does the TCON > instance that operate in dual-link mode have two ports in DT ? There > are two physical ports, so I think it makes sense to always have two > ports in DT. That's what we're doing for the LVDS encoders on R-Car > Gen3, in order to specify in DT which LVDS input of the dual-link > panel is connected to which LVDS output of the SoC. That allows > configuring the LVDS encoder to send the even and odd pixels on the > right port. As far as I can tell, you can't control that in our TCON. It just on more lanes, that's it. Also, we currently have multiple ports, to map another feature of the TCON, which is that it can drive directly a panel, or will send its output to the HDMI / TV encoders. Adding another port in that will break the current binding we have. Maxime --qacjjsbo4tknjumh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXkrQnQAKCRDj7w1vZxhR xYyzAP9aURz+zTYWHC5IhPxfSni9jc9Q1CStAZuL2lmltDlckwD/ev90hA7s+dfA ovuGwNHceNKd9m5Ieuk4gimi8XgkbgA= =33cs -----END PGP SIGNATURE----- --qacjjsbo4tknjumh-- --===============8630966084141635644== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============8630966084141635644==--