Received: by 10.192.165.156 with SMTP id m28csp1119712imm; Wed, 11 Apr 2018 12:48:58 -0700 (PDT) X-Google-Smtp-Source: AIpwx48vWcdpNJBkIcjRtev5Jx0qtN1kx84TI1oYmgHbENCRjIpxftygeD8x9RuzT4c1MrkY+1Fx X-Received: by 2002:a17:902:6807:: with SMTP id h7-v6mr6495746plk.90.1523476138807; Wed, 11 Apr 2018 12:48:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523476138; cv=none; d=google.com; s=arc-20160816; b=XOKKGt4ii5z2ZR9JOans+YNQ2hH9w6G6nvKIHLsc/QmFgkhmdB4nC8SfMsHQW9uP8w 19zOdR8wBADK329mNYVyDSKDL2e/XdbrkwixOYSP6w6gL/pZ2Cypqc5RJ97Sgi2HvMAe /p8Bq1BQpAGwSdfxTqPBoQmot2HxpwntCAy0bua1uqpU0Z6b4mkdxv3QOC3xgLbht4Ad BXOXtBbip5feXzG/HmCoRO8OzfWF8MD0THGPaRSDmpT92pt+0qAFDxmgfjkxskvManZH RRHEDxzyfpVvVu4Jen3uztK3QzANBxr6JginipK+gqHRsnA1yzjCk1SzooDitQIvWBbt AMDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=X2tY1FGnqb3UoTg9TF5cIfBMlZ3EQswMCxMEZnGNduE=; b=s3nLFFwxplEhKpU9qJc5DIS/M6Eb0Squ6IDpv8SzL4pv96ohvPqTPpbh48RolBjkbm Kjiw+2vhzCxbl9Naq9Bf1Z+F0PapUNtIQHP9EWAkFnE9XoEZxNZOYkip458K6M2q5CaS 6D6gU4TKK1LCV7avkZKk+E9TaGTVL17HadkG1F/YWYR6rpZe7A3eivdLPwZH2m4ZYs+r yt//Y4yr0GMuAdoY8BA458c21odvvBnEssDymr4tCzw9KU0108yL76OB4fr23X5HYup6 R2q79bKoGDvvV7UrMUJNABkJdci+nWEKeVQ0a+qGrpFgLGHpeuC/SmEy3d7B6STOYoNs QTiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m15si1174535pgs.170.2018.04.11.12.48.21; Wed, 11 Apr 2018 12:48:58 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756700AbeDKTAW (ORCPT + 99 others); Wed, 11 Apr 2018 15:00:22 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:37716 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756686AbeDKTAU (ORCPT ); Wed, 11 Apr 2018 15:00:20 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id E9330D61; Wed, 11 Apr 2018 19:00:19 +0000 (UTC) From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Chen-Yu Tsai , Rob Herring , Maxime Ripard , Sasha Levin Subject: [PATCH 4.9 168/310] dt-bindings: display: sun4i: Add allwinner,tcon-channel property Date: Wed, 11 Apr 2018 20:35:07 +0200 Message-Id: <20180411183629.780754443@linuxfoundation.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180411183622.305902791@linuxfoundation.org> References: <20180411183622.305902791@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Maxime Ripard [ Upstream commit 22662f12768f971809b478386d9cc4947d00497a ] The Allwinner Timings Controller has two, mutually exclusive, channels. When the binding has been introduced, it was assumed that there would be only a single user per channel in the system. While this is likely for the channel 0 which only connects to LCD displays, it turns out that the channel 1 can be connected to multiple controllers in the SoC (HDMI and TV encoders for example). And while the simultaneous use of HDMI and TV outputs cannot be achieved, switching from one to the other at runtime definitely sounds plausible. Add an extra property, allwinner,tcon-channel, to specify for a given endpoint which TCON channel it is connected to, while falling back to the previous mechanism if that property is missing. Acked-by: Chen-Yu Tsai Acked-by: Rob Herring Signed-off-by: Maxime Ripard Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 11 ++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) --- a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt +++ b/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt @@ -47,10 +47,13 @@ Required properties: Documentation/devicetree/bindings/media/video-interfaces.txt. The first port should be the input endpoint, the second one the output - The output should have two endpoints. The first is the block - connected to the TCON channel 0 (usually a panel or a bridge), the - second the block connected to the TCON channel 1 (usually the TV - encoder) + The output may have multiple endpoints. The TCON has two channels, + usually with the first channel being used for the panels interfaces + (RGB, LVDS, etc.), and the second being used for the outputs that + require another controller (TV Encoder, HDMI, etc.). The endpoints + will take an extra property, allwinner,tcon-channel, to specify the + channel the endpoint is associated to. If that property is not + present, the endpoint number will be used as the channel number. On SoCs other than the A33, there is one more clock required: - 'tcon-ch1': The clock driving the TCON channel 1