From: Marek Vasut <marex@denx.de> To: Jagan Teki <jagan@amarulasolutions.com>, Rob Herring <robh+dt@kernel.org>, Andrzej Hajda <a.hajda@samsung.com>, Neil Armstrong <narmstrong@baylibre.com>, Laurent Pinchart <Laurent.pinchart@ideasonboard.com>, Jonas Karlman <jonas@kwiboo.se>, Jernej Skrabec <jernej.skrabec@siol.net>, Sam Ravnborg <sam@ravnborg.org> Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-amarula@amarulasolutions.com Subject: Re: [PATCH v3 1/2] dt-bindings: display: bridge: Add bindings for SN65DSI83/84/85 Date: Fri, 5 Mar 2021 22:43:40 +0100 [thread overview] Message-ID: <be0fdd57-507d-0f9b-89db-65891531908c@denx.de> (raw) In-Reply-To: <20210214174453.104616-1-jagan@amarulasolutions.com> On 2/14/21 6:44 PM, Jagan Teki wrote: > SN65DSI83/84/85 devices are MIPI DSI to LVDS based bridge > controller IC's from Texas Instruments. > > SN65DSI83 - Single Channel DSI to Single-link LVDS bridge > SN65DSI84 - Single Channel DSI to Dual-link LVDS bridge > SN65DSI85 - Dual Channel DSI to Dual-link LVDS bridge [...] > +description: | > + SN65DSI83/84/85 devices are MIPI DSI to LVDS based bridge controller > + IC's from Texas Instruments. > + > + SN65DSI83 - Single Channel DSI to Single-link LVDS bridge > + SN65DSI84 - Single Channel DSI to Dual-link LVDS bridge > + SN65DSI85 - Dual Channel DSI to Dual-link LVDS bridge [...] > +properties: > + compatible: > + enum: > + - ti,sn65dsi83 > + - ti,sn65dsi84 DSI85 seems missing ? > + reg: > + const: 0x2c I have the DSI83 device at 0x2d, so this cannot be const 0x2c ? > + enable-gpios: > + maxItems: 1 > + description: GPIO specifier for bridge enable pin (active high). The bridge can work without this GPIO, so its optional. [...] Also, Doug reported that vcc and vcore regulators should likely be listed, see feedback on: [PATCH 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 bindings
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de> To: Jagan Teki <jagan@amarulasolutions.com>, Rob Herring <robh+dt@kernel.org>, Andrzej Hajda <a.hajda@samsung.com>, Neil Armstrong <narmstrong@baylibre.com>, Laurent Pinchart <Laurent.pinchart@ideasonboard.com>, Jonas Karlman <jonas@kwiboo.se>, Jernej Skrabec <jernej.skrabec@siol.net>, Sam Ravnborg <sam@ravnborg.org> Cc: devicetree@vger.kernel.org, linux-amarula@amarulasolutions.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org Subject: Re: [PATCH v3 1/2] dt-bindings: display: bridge: Add bindings for SN65DSI83/84/85 Date: Fri, 5 Mar 2021 22:43:40 +0100 [thread overview] Message-ID: <be0fdd57-507d-0f9b-89db-65891531908c@denx.de> (raw) In-Reply-To: <20210214174453.104616-1-jagan@amarulasolutions.com> On 2/14/21 6:44 PM, Jagan Teki wrote: > SN65DSI83/84/85 devices are MIPI DSI to LVDS based bridge > controller IC's from Texas Instruments. > > SN65DSI83 - Single Channel DSI to Single-link LVDS bridge > SN65DSI84 - Single Channel DSI to Dual-link LVDS bridge > SN65DSI85 - Dual Channel DSI to Dual-link LVDS bridge [...] > +description: | > + SN65DSI83/84/85 devices are MIPI DSI to LVDS based bridge controller > + IC's from Texas Instruments. > + > + SN65DSI83 - Single Channel DSI to Single-link LVDS bridge > + SN65DSI84 - Single Channel DSI to Dual-link LVDS bridge > + SN65DSI85 - Dual Channel DSI to Dual-link LVDS bridge [...] > +properties: > + compatible: > + enum: > + - ti,sn65dsi83 > + - ti,sn65dsi84 DSI85 seems missing ? > + reg: > + const: 0x2c I have the DSI83 device at 0x2d, so this cannot be const 0x2c ? > + enable-gpios: > + maxItems: 1 > + description: GPIO specifier for bridge enable pin (active high). The bridge can work without this GPIO, so its optional. [...] Also, Doug reported that vcc and vcore regulators should likely be listed, see feedback on: [PATCH 1/2] dt-bindings: drm/bridge: ti-sn65dsi83: Add TI SN65DSI83 bindings _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-03-05 21:44 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-14 17:44 [PATCH v3 1/2] dt-bindings: display: bridge: Add bindings for SN65DSI83/84/85 Jagan Teki 2021-02-14 17:44 ` Jagan Teki 2021-02-14 17:44 ` [PATCH v3 2/2] drm: bridge: Add TI SN65DSI83/84/85 DSI to LVDS bridge Jagan Teki 2021-02-14 17:44 ` Jagan Teki 2021-02-14 18:43 ` kernel test robot 2021-02-14 18:43 ` kernel test robot 2021-03-05 21:51 ` Marek Vasut 2021-03-05 21:51 ` Marek Vasut 2021-03-24 13:21 ` Claudius Heine 2021-03-24 13:21 ` Claudius Heine 2021-02-15 9:02 ` [PATCH v3 1/2] dt-bindings: display: bridge: Add bindings for SN65DSI83/84/85 Neil Armstrong 2021-02-15 9:02 ` Neil Armstrong 2021-02-15 11:25 ` Jagan Teki 2021-02-15 11:25 ` Jagan Teki 2021-02-15 16:49 ` Neil Armstrong 2021-02-15 16:49 ` Neil Armstrong 2021-03-05 21:36 ` Rob Herring 2021-03-05 21:36 ` Rob Herring 2021-03-05 21:43 ` Marek Vasut [this message] 2021-03-05 21:43 ` Marek Vasut 2021-03-24 13:56 ` Claudius Heine 2021-03-24 13:56 ` Claudius Heine 2021-04-07 10:04 ` ch 2021-04-07 10:04 ` ch 2021-04-08 14:45 ` Jagan Teki 2021-04-08 14:45 ` Jagan Teki 2021-04-21 22:34 ` Marek Vasut 2021-04-21 22:34 ` Marek Vasut 2021-04-22 8:10 ` Jagan Teki 2021-04-22 8:10 ` Jagan Teki
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=be0fdd57-507d-0f9b-89db-65891531908c@denx.de \ --to=marex@denx.de \ --cc=Laurent.pinchart@ideasonboard.com \ --cc=a.hajda@samsung.com \ --cc=devicetree@vger.kernel.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=jagan@amarulasolutions.com \ --cc=jernej.skrabec@siol.net \ --cc=jonas@kwiboo.se \ --cc=linux-amarula@amarulasolutions.com \ --cc=linux-kernel@vger.kernel.org \ --cc=narmstrong@baylibre.com \ --cc=robh+dt@kernel.org \ --cc=sam@ravnborg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.