| Message ID | 20190315130825.9005-5-jagan@amarulasolutions.com |
|---|---|
| State | New |
| Headers |
Return-Path: <linux-amarula+bncBD7MFH7A7EEBB2OHV3SAKGQEHTC5QGI@amarulasolutions.com> X-Original-To: linux-amarula@patchwork.amarulasolutions.com Delivered-To: linux-amarula@patchwork.amarulasolutions.com Received: from mail-pg1-f198.google.com (mail-pg1-f198.google.com [209.85.215.198]) by ganimede.amarulasolutions.com (Postfix) with ESMTPS id D41693F033 for <linux-amarula@patchwork.amarulasolutions.com>; Fri, 15 Mar 2019 14:08:58 +0100 (CET) Received: by mail-pg1-f198.google.com with SMTP id d10sf9997748pgv.23 for <linux-amarula@patchwork.amarulasolutions.com>; Fri, 15 Mar 2019 06:08:58 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1552655337; cv=pass; d=google.com; s=arc-20160816; b=jAjqL0mCdZ+3dVbwCLgXsUn+b7GWtV0yoAheEjYLaTRtd2xmQd6h59xKi7KPbhRN+F pDcxQzwoi14zZLGRVTwLfYh0j3UA5/jbCdduWpjJGNCxvPX1sfqX4Prj9c8r6/LJ50F3 ujSaKmnpj3BhX0X0W08HwJzgjUanrmbk/81TcwChpIvuF3JweKZOOUyHLhHZxmjDygr4 LC3hoQXbwZpfWZh0axVHIiJZBFFPF6uC1ylDzlVJug4wcOjqwz5LKAGKdF8j/o+lFl3l mzCUxek+l06CEnr0HoGlYM9piuIwYqvAMfpbwANDM/1FAHTQbe5DChq7IhFjVWssDa2w HLRQ== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-archive:list-help:list-post:list-id :mailing-list:precedence:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:dkim-signature; bh=FYIh8v3RvcxNV8P2p1QhQXUXl6q29plTYDizbSVbWzw=; b=jh25QE7e0xmk2eLl9+afZHIv8YFn5vZTrOirnKRIqf2TEObwdtiUXVowCR6ebOWHPF QV/N0Qa3j3VkNcKLqq8ypUW738CFnfR+ygk20uFI9aVpictqoSeEJ8sjd3+zzepjjWZq 8a7tDFsBC2nPTh6bMy0Jlckg0PZ4bX4Yj0RHR3jqkBJv/PCeqld4EFh+EdIvx6C5PhcH 55KKgluMZsH2MMpBfOnhzLAMb3WsZooIWsuOzBCeOs739POlv2oRfLI3vXOlBtD3zwb7 zck69omiFfGBN/p5enEhz3NVAyLiWjQH0tDaz5Z0GWejeuQFbcUVJ24lZLW5T13dDmhc 5CIg== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=MBPaO0Zl; spf=pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=jagan@amarulasolutions.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amarulasolutions.com; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:x-original-sender:x-original-authentication-results :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-unsubscribe; bh=FYIh8v3RvcxNV8P2p1QhQXUXl6q29plTYDizbSVbWzw=; b=dN9mqyHkOfwXmsJx4vWwtxinG799hgZny4Nj3+PeKxYIJI6Rdm29SpHOzyjAn1tDGE ZLYxQAzlaqNLRT0yPin6zXztwOrOkXeUXjjvw7DzaRtVKIbdUU44/Bp+Ib7sBGYFlDBz 3B4gdPM3ib95i6VidmHJbiLrURqYyHGMnrGAw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:x-original-sender :x-original-authentication-results:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-unsubscribe; bh=FYIh8v3RvcxNV8P2p1QhQXUXl6q29plTYDizbSVbWzw=; b=AFDVWmfxYEfUAr3QDvugtXNlW63e3nbBmq/r2pMoZXGnP5sMBIsOixmd0lIuChnEX8 +kqQ0J61x3gQc1X9RlIM3MksZ5nfkDL3G05Z6b5xq3OUckh9g72HGtnEl4g8pMSDau9z QOVcozkoIm7w6XpGbLLWawdobHY5p9TDo/8zEy7I7zz/UmklV4O2fJwXHT4xM2bcdns7 r5KrPqHBOmwq919ofiGVC0wVjHZzQm/r87ToaZfLqkSMZbFwAAC1igPSMvIJUn1RD1tG VvZOYEfrcxmMqy46Uw2IFyTW8/fbBCwr/z4nRXkRyhnPJdJakOkenTyfJkvKau/t3hLn fqQA== X-Gm-Message-State: APjAAAXhhSw9cY2Vgegh0nAwT8sMUMvDhOlUD+0Fx8d9ZFrmqsVI+OZf KBoZILeGte/yzR9QPbk8hUBwc5Dn X-Google-Smtp-Source: APXvYqyeGAv+BIKVSUJ5iHbdZWOJYM1inKi4XyMco/wgMm33vaXdwXnK4n2mP2iYo/c5Bzy2oR0wFw== X-Received: by 2002:a63:c642:: with SMTP id x2mr1186974pgg.34.1552655337640; Fri, 15 Mar 2019 06:08:57 -0700 (PDT) X-BeenThere: linux-amarula@amarulasolutions.com Received: by 2002:a63:68c7:: with SMTP id d190ls3573078pgc.3.gmail; Fri, 15 Mar 2019 06:08:57 -0700 (PDT) X-Received: by 2002:a62:574d:: with SMTP id l74mr4047283pfb.9.1552655337195; Fri, 15 Mar 2019 06:08:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552655337; cv=none; d=google.com; s=arc-20160816; b=XOzOoLl2pbiELz4mLX1chZzyvRkr1X0O0QmBfh1UTufNT5+mfUmgWmy2ZYr6R1oHHC WAHDDTDw/BGHfeLYMosAnMuclhFNED2Ay+nxKCCtNqhTGC3k8+Rcok3BY/xt+/a6jALD V7Hr8+q2CghkqMpRpHLKMM6vcwX1GV5vheNBORwrFgwHdfSWmd1mNd2EgTA5ACRRh18Q l/zFebHuJNkreCptv/vtyr7ODysQdUFcOIbNg4olntdX/Gv9jaF9jdw5NUuIy7aMbYla SETlpFK8xitAG7+NLm/faxmCSF1xEdm39oEZRgXEGnUhhjV09Dykb0krRQAkbBmdXQMx /OKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:dkim-signature; bh=AAGhTSDHAoMycmwWhiYuqV20infnrcRGhVpZHstA2bg=; b=kX4zT5XqXvJJ9g9lCbYL2NReRnvcexa3MMV9gappGdb5z3vcd8mzZQ8UoA0W9NNuZf TmirLTtE8pzMH1F408Ks0DgwdPwRnzFFSdY+SRfkP431sUnEPcYUV1TCgozlYh4IrP8Y klZmPLegL/vnOaPtYYDzRH3I+P1UEfqCUB2O3zDYjxjJlHleWMm4hooZ80jM+zR8QnXh /UurAxakhpEKr0OkVvFKMAPKiP+rYJPuUFtGbuDO+Tt905yiCAyrBLxvlZ++tdyKs8By 452tvf/8Jx/IINr/znuGEQPG8EoOhSHdGCozEm/xf+floAI25nNZOcgFqJFlcxEG4Eqz vxVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=MBPaO0Zl; spf=pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=jagan@amarulasolutions.com Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id gn4sor2847291plb.64.2019.03.15.06.08.57 for <linux-amarula@amarulasolutions.com> (Google Transport Security); Fri, 15 Mar 2019 06:08:57 -0700 (PDT) Received-SPF: pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) client-ip=209.85.220.65; X-Received: by 2002:a17:902:234b:: with SMTP id n11mr4218595plg.89.1552655336942; Fri, 15 Mar 2019 06:08:56 -0700 (PDT) Received: from localhost.localdomain ([183.82.230.185]) by smtp.gmail.com with ESMTPSA id e2sm854008pfa.64.2019.03.15.06.08.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Mar 2019 06:08:56 -0700 (PDT) From: Jagan Teki <jagan@amarulasolutions.com> To: Andrzej Hajda <a.hajda@samsung.com>, Laurent Pinchart <Laurent.pinchart@ideasonboard.com>, Chen-Yu Tsai <wens@csie.org>, Maxime Ripard <maxime.ripard@bootlin.com>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com> Cc: Michael Trimarchi <michael@amarulasolutions.com>, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@googlegroups.com, linux-amarula@amarulasolutions.com, Jagan Teki <jagan@amarulasolutions.com> Subject: [PATCH 4/6] dt-bindings: display: bridge: Add ICN6211 MIPI-DSI to RGB convertor bridge Date: Fri, 15 Mar 2019 18:38:23 +0530 Message-Id: <20190315130825.9005-5-jagan@amarulasolutions.com> X-Mailer: git-send-email 2.18.0.321.gffc6fa0e3 In-Reply-To: <20190315130825.9005-1-jagan@amarulasolutions.com> References: <20190315130825.9005-1-jagan@amarulasolutions.com> MIME-Version: 1.0 X-Original-Sender: jagan@amarulasolutions.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@amarulasolutions.com header.s=google header.b=MBPaO0Zl; spf=pass (google.com: domain of jagan@amarulasolutions.com designates 209.85.220.65 as permitted sender) smtp.mailfrom=jagan@amarulasolutions.com Content-Type: text/plain; charset="UTF-8" Precedence: list Mailing-list: list linux-amarula@amarulasolutions.com; contact linux-amarula+owners@amarulasolutions.com List-ID: <linux-amarula.amarulasolutions.com> X-Spam-Checked-In-Group: linux-amarula@amarulasolutions.com X-Google-Group-Id: 476853432473 List-Post: <https://groups.google.com/a/amarulasolutions.com/group/linux-amarula/post>, <mailto:linux-amarula@amarulasolutions.com> List-Help: <https://support.google.com/a/amarulasolutions.com/bin/topic.py?topic=25838>, <mailto:linux-amarula+help@amarulasolutions.com> List-Archive: <https://groups.google.com/a/amarulasolutions.com/group/linux-amarula/> List-Unsubscribe: <mailto:googlegroups-manage+476853432473+unsubscribe@googlegroups.com>, <https://groups.google.com/a/amarulasolutions.com/group/linux-amarula/subscribe> |
| Series |
drm/bridge: Add ICN6211 MIPI-DSI/RGB bridge
|
|
Commit Message
Jagan Teki
March 15, 2019, 1:08 p.m. UTC
ICN6211 is MIPI-DSI/RGB converter bridge from chipone.
It has a flexible configuration of MIPI DSI signal input
and produce RGB565, RGB666, RGB888 output format.
Add dt-bingings for it.
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
.../display/bridge/chipone,icn6211.txt | 36 +++++++++++++++++++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt
Comments
On Fri, Mar 15, 2019 at 06:38:23PM +0530, Jagan Teki wrote: > ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > It has a flexible configuration of MIPI DSI signal input > and produce RGB565, RGB666, RGB888 output format. > > Add dt-bingings for it. > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> > --- > .../display/bridge/chipone,icn6211.txt | 36 +++++++++++++++++++ > 1 file changed, 36 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > diff --git a/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > new file mode 100644 > index 000000000000..7f13efd7ee7f > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > @@ -0,0 +1,36 @@ > +Chipone ICN6211 MIPI-DSI to RGB Convertor Bridge > + > +ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > +It has a flexible configuration of MIPI DSI signal input > +and produce RGB565, RGB666, RGB888 output format. > + > +Required properties for RGB: > +- compatible: must be "chipone,icn6211" and one of: > + * "bananapi,icn6211" Why is that compatible needed? > +- reg: the virtual channel number of a DSI peripheral > +- reset-gpios: a GPIO phandle for the reset pin > + > +The device node can contain following 'port' child nodes, > +according to the OF graph bindings defined in [1]: > + 0: DSI Input, not required, if the bridge is DSI controlled > + 1: RGB Output, mandatory Your example doesn't have that input port Maxime
On Fri, Mar 15, 2019 at 7:04 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > On Fri, Mar 15, 2019 at 06:38:23PM +0530, Jagan Teki wrote: > > ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > It has a flexible configuration of MIPI DSI signal input > > and produce RGB565, RGB666, RGB888 output format. > > > > Add dt-bingings for it. > > > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> > > --- > > .../display/bridge/chipone,icn6211.txt | 36 +++++++++++++++++++ > > 1 file changed, 36 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > new file mode 100644 > > index 000000000000..7f13efd7ee7f > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > @@ -0,0 +1,36 @@ > > +Chipone ICN6211 MIPI-DSI to RGB Convertor Bridge > > + > > +ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > +It has a flexible configuration of MIPI DSI signal input > > +and produce RGB565, RGB666, RGB888 output format. > > + > > +Required properties for RGB: > > +- compatible: must be "chipone,icn6211" and one of: > > + * "bananapi,icn6211" > > Why is that compatible needed? chipone,icn6211 - generic compatible bridge controller IC bananapi,icn6211 - compatible for icn6211 bridge using on bananapi panel I hope this would be proper bindings in terms of controller IC with associate device, anything wrong? Infact I used similar reference from Ilitek Bananapi panel from here Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.txt This is what I understood based on dt-binding, correct if I'm wrong. ilitek,ili9881c - generic ilitek,ili9881c compatable bananapi,lhr050h41 - compatible for bananapi panel associated with this ilitek IC > > > +- reg: the virtual channel number of a DSI peripheral > > +- reset-gpios: a GPIO phandle for the reset pin > > + > > +The device node can contain following 'port' child nodes, > > +according to the OF graph bindings defined in [1]: > > + 0: DSI Input, not required, if the bridge is DSI controlled > > + 1: RGB Output, mandatory > > Your example doesn't have that input port Yes, I intentionally did this by referring existing bridge binding. Documentation/devicetree/bindings/display/bridge/toshiba,tc35876*.txt Do we really need? since the input port can be part of panel binding.
On Tue, Mar 19, 2019 at 12:58 AM Jagan Teki <jagan@amarulasolutions.com> wrote: > > On Fri, Mar 15, 2019 at 7:04 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > > > On Fri, Mar 15, 2019 at 06:38:23PM +0530, Jagan Teki wrote: > > > ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > > It has a flexible configuration of MIPI DSI signal input > > > and produce RGB565, RGB666, RGB888 output format. > > > > > > Add dt-bingings for it. > > > > > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> > > > --- > > > .../display/bridge/chipone,icn6211.txt | 36 +++++++++++++++++++ > > > 1 file changed, 36 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > new file mode 100644 > > > index 000000000000..7f13efd7ee7f > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > @@ -0,0 +1,36 @@ > > > +Chipone ICN6211 MIPI-DSI to RGB Convertor Bridge > > > + > > > +ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > > +It has a flexible configuration of MIPI DSI signal input > > > +and produce RGB565, RGB666, RGB888 output format. > > > + > > > +Required properties for RGB: > > > +- compatible: must be "chipone,icn6211" and one of: > > > + * "bananapi,icn6211" > > > > Why is that compatible needed? > > chipone,icn6211 - generic compatible bridge controller IC > bananapi,icn6211 - compatible for icn6211 bridge using on bananapi panel > > I hope this would be proper bindings in terms of controller IC with > associate device, anything wrong? Infact I used similar reference from > Ilitek Bananapi panel from here > Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.txt > > This is what I understood based on dt-binding, correct if I'm wrong. > > ilitek,ili9881c - generic ilitek,ili9881c compatable > bananapi,lhr050h41 - compatible for bananapi panel associated with > this ilitek IC ili9881c is an LCD driver chip with a MIPI DSI interface. It directly drives the LCD panel, not outputting some RGB stuff. So it is a binding and driver for a panel, not a bridge in your case. > > > > > +- reg: the virtual channel number of a DSI peripheral > > > +- reset-gpios: a GPIO phandle for the reset pin > > > + > > > +The device node can contain following 'port' child nodes, > > > +according to the OF graph bindings defined in [1]: > > > + 0: DSI Input, not required, if the bridge is DSI controlled > > > + 1: RGB Output, mandatory > > > > Your example doesn't have that input port > > Yes, I intentionally did this by referring existing bridge binding. > Documentation/devicetree/bindings/display/bridge/toshiba,tc35876*.txt > > Do we really need? since the input port can be part of panel binding. How could the input port of _your_ _bridge_ be part of the panel binding? ChenYu
On Tue, Mar 19, 2019 at 8:29 AM Chen-Yu Tsai <wens@csie.org> wrote: > > On Tue, Mar 19, 2019 at 12:58 AM Jagan Teki <jagan@amarulasolutions.com> wrote: > > > > On Fri, Mar 15, 2019 at 7:04 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > > > > > On Fri, Mar 15, 2019 at 06:38:23PM +0530, Jagan Teki wrote: > > > > ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > > > It has a flexible configuration of MIPI DSI signal input > > > > and produce RGB565, RGB666, RGB888 output format. > > > > > > > > Add dt-bingings for it. > > > > > > > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> > > > > --- > > > > .../display/bridge/chipone,icn6211.txt | 36 +++++++++++++++++++ > > > > 1 file changed, 36 insertions(+) > > > > create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > > > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > > new file mode 100644 > > > > index 000000000000..7f13efd7ee7f > > > > --- /dev/null > > > > +++ b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > > @@ -0,0 +1,36 @@ > > > > +Chipone ICN6211 MIPI-DSI to RGB Convertor Bridge > > > > + > > > > +ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > > > +It has a flexible configuration of MIPI DSI signal input > > > > +and produce RGB565, RGB666, RGB888 output format. > > > > + > > > > +Required properties for RGB: > > > > +- compatible: must be "chipone,icn6211" and one of: > > > > + * "bananapi,icn6211" > > > > > > Why is that compatible needed? > > > > chipone,icn6211 - generic compatible bridge controller IC > > bananapi,icn6211 - compatible for icn6211 bridge using on bananapi panel > > > > I hope this would be proper bindings in terms of controller IC with > > associate device, anything wrong? Infact I used similar reference from > > Ilitek Bananapi panel from here > > Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.txt > > > > This is what I understood based on dt-binding, correct if I'm wrong. > > > > ilitek,ili9881c - generic ilitek,ili9881c compatable > > bananapi,lhr050h41 - compatible for bananapi panel associated with > > this ilitek IC > > ili9881c is an LCD driver chip with a MIPI DSI interface. It directly > drives the LCD panel, not outputting some RGB stuff. So it is a binding > and driver for a panel, not a bridge in your case. > > > > > > > > +- reg: the virtual channel number of a DSI peripheral > > > > +- reset-gpios: a GPIO phandle for the reset pin > > > > + > > > > +The device node can contain following 'port' child nodes, > > > > +according to the OF graph bindings defined in [1]: > > > > + 0: DSI Input, not required, if the bridge is DSI controlled > > > > + 1: RGB Output, mandatory > > > > > > Your example doesn't have that input port > > > > Yes, I intentionally did this by referring existing bridge binding. > > Documentation/devicetree/bindings/display/bridge/toshiba,tc35876*.txt > > > > Do we really need? since the input port can be part of panel binding. > > How could the input port of _your_ _bridge_ be part of the panel binding? Here the panel is from another vendor say bananapi, so the binding of that part could be already covered ie is what I mean. Since I mentioned I took the reference binding from another bridge. It has similar structure of binding / example. arch/arm/boot/dts/exynos5250-arndale.dts Bridge example binding: Documentation/devicetree/bindings/display/bridge/toshiba,tc358764.txt Panel example binding mentioned here Documentation/devicetree/bindings/display/panel/boe,hv070wsa-100.txt
On Mon, Mar 18, 2019 at 10:28:10PM +0530, Jagan Teki wrote: > On Fri, Mar 15, 2019 at 7:04 PM Maxime Ripard <maxime.ripard@bootlin.com> wrote: > > > > On Fri, Mar 15, 2019 at 06:38:23PM +0530, Jagan Teki wrote: > > > ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > > It has a flexible configuration of MIPI DSI signal input > > > and produce RGB565, RGB666, RGB888 output format. > > > > > > Add dt-bingings for it. > > > > > > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com> > > > --- > > > .../display/bridge/chipone,icn6211.txt | 36 +++++++++++++++++++ > > > 1 file changed, 36 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > new file mode 100644 > > > index 000000000000..7f13efd7ee7f > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt > > > @@ -0,0 +1,36 @@ > > > +Chipone ICN6211 MIPI-DSI to RGB Convertor Bridge > > > + > > > +ICN6211 is MIPI-DSI/RGB converter bridge from chipone. > > > +It has a flexible configuration of MIPI DSI signal input > > > +and produce RGB565, RGB666, RGB888 output format. > > > + > > > +Required properties for RGB: > > > +- compatible: must be "chipone,icn6211" and one of: > > > + * "bananapi,icn6211" > > > > Why is that compatible needed? > > chipone,icn6211 - generic compatible bridge controller IC > bananapi,icn6211 - compatible for icn6211 bridge using on bananapi panel > > I hope this would be proper bindings in terms of controller IC with > associate device, anything wrong? Infact I used similar reference from > Ilitek Bananapi panel from here > Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.txt > > This is what I understood based on dt-binding, correct if I'm wrong. The ILI9881c is an LCD controller, and it has some panel specific configuration. Does your bridge have board specific configuration? Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
diff --git a/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt new file mode 100644 index 000000000000..7f13efd7ee7f --- /dev/null +++ b/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.txt @@ -0,0 +1,36 @@ +Chipone ICN6211 MIPI-DSI to RGB Convertor Bridge + +ICN6211 is MIPI-DSI/RGB converter bridge from chipone. +It has a flexible configuration of MIPI DSI signal input +and produce RGB565, RGB666, RGB888 output format. + +Required properties for RGB: +- compatible: must be "chipone,icn6211" and one of: + * "bananapi,icn6211" +- reg: the virtual channel number of a DSI peripheral +- reset-gpios: a GPIO phandle for the reset pin + +The device node can contain following 'port' child nodes, +according to the OF graph bindings defined in [1]: + 0: DSI Input, not required, if the bridge is DSI controlled + 1: RGB Output, mandatory + +[1]: Documentation/devicetree/bindings/media/video-interfaces.txt + +Example: + + bridge@0 { + compatible = "bananapi,icn6211", "chipone,icn6211"; + reg = <0>; + reset-gpios = <&pio 3 6 GPIO_ACTIVE_HIGH>; /* LCD-RST: PD6 */ + #address-cells = <1>; + #size-cells = <0>; + + port@1 { + reg = <1>; + + bridge_out_ep: endpoint { + remote-endpoint = <&panel_ep>; + }; + }; + };