Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2950656imu; Wed, 7 Nov 2018 02:21:23 -0800 (PST) X-Google-Smtp-Source: AJdET5drVBkcImNZi0LP2Oj4K+uwb0QAo7B27YQ2TIeou8+jPd3Cfo0WCgGdYZEsSBe84g5M5XiT X-Received: by 2002:a17:902:5c4:: with SMTP id f62-v6mr1358889plf.18.1541586083159; Wed, 07 Nov 2018 02:21:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541586083; cv=none; d=google.com; s=arc-20160816; b=LtsH1M8zieQGeH1uiSQkMIGtLCA33nAFDy4nyCUAo25KrYkSJ7FEhDQ8iO/jhcdaLI aFXwxSSPmpVyw1Rtjo3Wdh5MJlT+hKAh7OkoRBb8DXROXNtciHkUSWzQtVyJRo0bezsd 0cfrBueRN6OHHFP8emBDp7/c1o/PlTnIcTzpPQFBPmEStv7IwHeGWDbuuqsL1+NZQqWr QQ0dkfoPI2vDM2BgPhS7mK3pveA+0y2oXjUAJKZTwhbaVR6s+fUAv/84EBu9V8krvSU7 e9qQwGBSkzPA44Sl7HFKW/rm3DIEfYkWmf854cYgwSv919hKLZTdKNTEpyZS7Ss9RA9m x+zA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=4bWK2SwWmO98rDA/Hm2d4En+vhGFZZlf7+F0uutA7j0=; b=GGSWU2T3N4mwlODB7ENjqSPYGXHFQGGm6/ak4PCXLxYOM87Xf+boHK3ivTtX4HkhJG +Ajlil6ExfAFq/vR14iMskBg2hYe+Wz5zR8W+JSQa4iAmK3ggOnQcUkU2rjlO0y8aGJO hhhdVhOfYFUqJzm9CL2+glOo3sUQJnTrUGWxlrBHQVKt8CsA/D3DcZ/ETcQTBK00fNSK vB6ZC2eMBfkIzQRAjynPcAJkfl+P26R3a1ZwGKwkBKHM/HIqry1a0z9qCrjLbdSxuZ2M Yl4tlyE5qwMK1JrMDTxEwhvD7hIoLDRm/is1ACX5nU6edB6+01Vf+0p9m/14s0v/hXZm utDQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QMbGtY2i; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f23-v6si155557pgl.207.2018.11.07.02.21.07; Wed, 07 Nov 2018 02:21:23 -0800 (PST) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=QMbGtY2i; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730749AbeKGTuB (ORCPT + 99 others); Wed, 7 Nov 2018 14:50:01 -0500 Received: from mail-wr1-f65.google.com ([209.85.221.65]:41754 "EHLO mail-wr1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726604AbeKGTuA (ORCPT ); Wed, 7 Nov 2018 14:50:00 -0500 Received: by mail-wr1-f65.google.com with SMTP id x12-v6so16753629wrw.8; Wed, 07 Nov 2018 02:20:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4bWK2SwWmO98rDA/Hm2d4En+vhGFZZlf7+F0uutA7j0=; b=QMbGtY2ilT7MT1QY48UEhkZLhX0ay0U9mjC9BNgMXPZnK81wxh+3x/BGV7g3g+eouV bMvmOBbITSUuJNOPI8SiEjMN5BSCQXojs0ip6N1xkScLPhE7JNfxDxFI56SP8GSfno+n 9Fg5LaOJrYAzhOeiLpWwjjSrmlSteZnTvuN6Ud/UMqQN9vTvAVXI1XwmMFAZB3hPTYHq XFGRQjIKaM84P7B7BtFlrMWzqrTqXqY7NYrqzswvxn+/S98k5LrISqMmMwWrVwZhjREO VjhAtvYgMnmLbmFI4/ijBL5cwhg2lZy2r1mbK8InxyKiE7fhfhUmONGK2sM/45gTUZD2 gJDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4bWK2SwWmO98rDA/Hm2d4En+vhGFZZlf7+F0uutA7j0=; b=MEWTvFjw2NH/UTvFPVUq6UW/bABUtCRQ2/qXSw6ugNpXc51Ai4kI5osKfu6DdnGpKw 57fs5kiV7XL+kcY6Tih/c9EuyV6eAntGiPn6smpJMRK6f+kIvEX0xjY2trpTMozF++AR FBg+Nvd/xlkZLlUiXqzkDQFkzDXhWC0CdmXUJ6qDIieXs6xnaXMFq4M3MTza5Vi2ffQr Kanx51PRHiKYSnrmm01uI9jUpD1pxchKVH2i07qT11TckCpZQC7Ha/NZFaEryiP8SeJh NG/ooBNwo3MCBvWgR3IEPS5yaELt+z06cz/ZjSQTTCAYJvpHDKGuYD4g6wqkappJETNC 4gPA== X-Gm-Message-State: AGRZ1gLXUQ33WxwacWqgHm8ve/3snX5305xeybXzA7dUv1SfK27JzlYY OV/0KS45WCaPBqtM2Eop+4fJYI5FrqG0rXgvdbK7kyuT X-Received: by 2002:adf:8281:: with SMTP id 1-v6mr1334288wrc.252.1541586016070; Wed, 07 Nov 2018 02:20:16 -0800 (PST) MIME-Version: 1.0 References: <20181026144344.27778-1-jagan@amarulasolutions.com> <20181026144344.27778-18-jagan@amarulasolutions.com> <3c4c8a08-8c1e-1ac6-2b53-81389d69c97b@samsung.com> In-Reply-To: From: Julian Calaby Date: Wed, 7 Nov 2018 21:20:03 +1100 Message-ID: Subject: Re: [linux-sunxi] Re: [PATCH v3 17/25] dt-bindings: panel: Add Bananapi S070WV20-CT16 ICN6211 MIPI-DSI to RGB bridge To: Jagan Teki Cc: a.hajda@samsung.com, Chen-Yu Tsai , Maxime Ripard , Icenowy Zheng , jernej.skrabec@siol.net, Vasily Khoruzhick , Rob Herring , Mark Rutland , Catalin Marinas , Will Deacon , David Airlie , dri-devel , Michael Turquette , sboyd@kernel.org, "open list:COMMON CLK FRAMEWORK" , Michael Nazzareno Trimarchi , "Mailing List, Arm" , devicetree , "linux-kernel@vger.kernel.org" , linux-sunxi@googlegroups.com 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 Hi Jagan, On Wed, Nov 7, 2018 at 5:13 AM Jagan Teki wrote: > > On Wed, Oct 31, 2018 at 2:46 PM Julian Calaby wrote: > > > > Hi Jagan, > > > > On Wed, Oct 31, 2018 at 7:58 PM Chen-Yu Tsai wrote: > > > > > > On Wed, Oct 31, 2018 at 4:53 PM Andrzej Hajda wrote: > > > > > > > > On 26.10.2018 16:43, Jagan Teki wrote: > > > > > Bananapi S070WV20-CT16 ICN6211 is 800x480, 4-lane MIPI-DSI to RGB > > > > > bridge panel, which is available on same PCB with 24-bit RGB interface. > > > > > > > > > > So, this patch adds DSI specific binding details on existing > > > > > dt-bindings file. > > > > > > > > > > Signed-off-by: Jagan Teki > > > > > --- > > > > > Changes for v3: > > > > > - Use existing binding doc and update dsi details > > > > > Changes for v2: > > > > > - none > > > > > > > > > > .../display/panel/bananapi,s070wv20-ct16.txt | 31 +++++++++++++++++-- > > > > > 1 file changed, 29 insertions(+), 2 deletions(-) > > > > > > > > > > diff --git a/Documentation/devicetree/bindings/display/panel/bananapi,s070wv20-ct16.txt b/Documentation/devicetree/bindings/display/panel/bananapi,s070wv20-ct16.txt > > > > > index 35bc0c839f49..b7855dc7c66f 100644 > > > > > --- a/Documentation/devicetree/bindings/display/panel/bananapi,s070wv20-ct16.txt > > > > > +++ b/Documentation/devicetree/bindings/display/panel/bananapi,s070wv20-ct16.txt > > > > > @@ -1,12 +1,39 @@ > > > > > Banana Pi 7" (S070WV20-CT16) TFT LCD Panel > > > > > > > > > > +S070WV20-CT16 is 7" 800x480 panel connected through a 24-bit RGB interface. > > > > > + > > > > > +Depending on the variant, the PCB attached to the panel module either > > > > > +supports DSI, or DSI + 24-bit RGB. DSI is converted to 24-bit RGB via > > > > > +an onboard ICN6211 MIPI DSI - RGB bridge chip, then fed to the panel > > > > > +itself > > > > > > > > As I understand this is display board, which contains 'pure' RGB panel > > > > S070WV20-CT16 and optionally ICN6211 DSI->RGB bridge. > > > > These are separate devices, just connected by vendor to simplify its > > > > assembly. Why don't you create then bridge driver for ICN6211 and RGB > > > > panel driver for S070WV20-CT16 - it looks more generic. > > > > Then you can describe both in dts and voila. > > > > Creating drivers for every combo of devices (panel + bridge), just > > > > because some vendor sells them together seems incorrect - we have > > > > devicetree for it. > > > > > > Rob suggested this, and also the opposite: using the same > > > "bananapi,s070wv20-ct16" > > > compatible string for both types of connections, and have the driver deal with > > > detecting the bus type. > > > > > > The thing about the bridge chip is that there's no available datasheet that > > > describes all the parts of the init sequence, in fact none at all. I managed > > > to work out some bits, but the others remain a mystery and must be hard-coded > > > to match the panel. That would work against having a generic bridge driver. > > > > To me it seems logical that we'd model it as another step in the graph > > between the DSI component and the panel. It's conceivable that some > > other manufacturer will probably buy these for their panels and having > > a somewhat generic driver seems vaguely future proof to me. > > > > As I see it, the weird init process belongs to the bridge chip and the > > timings belong to the panel and we shouldn't "confuse" them by giving > > them the same compatible. > > But the problem here is due to lack of information about the panel, > the init process command opcode data values seem to based on the panel > timings values. This look weird and ie reason for going into separate > panel driver with different compatible. I'd missed that particular wrinkle. In that case, it makes sense to produce a panel driver with the bridge chip's compatible. Thanks, -- Julian Calaby Email: julian.calaby@gmail.com Profile: http://www.google.com/profiles/julian.calaby/