All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Marek Vasut <marex@denx.de>
Cc: Robert Foss <robert.foss@linaro.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Jagan Teki <jagan@amarulasolutions.com>,
	dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH V3 05/13] drm: bridge: icn6211: Add DSI lane count DT property parsing
Date: Tue, 8 Mar 2022 14:49:21 +0100	[thread overview]
Message-ID: <20220308134921.zebs533xeazq46ts@houat> (raw)
In-Reply-To: <dd68f569-7fe3-dc00-b2f0-536b066ec37a@denx.de>

[-- Attachment #1: Type: text/plain, Size: 3554 bytes --]

On Tue, Mar 08, 2022 at 02:27:40PM +0100, Marek Vasut wrote:
> On 3/8/22 13:51, Maxime Ripard wrote:
> > On Tue, Mar 08, 2022 at 11:29:59AM +0100, Marek Vasut wrote:
> > > On 3/8/22 11:07, Jagan Teki wrote:
> > > > On Tue, Mar 8, 2022 at 3:19 PM Marek Vasut <marex@denx.de> wrote:
> > > > > 
> > > > > On 3/8/22 09:03, Jagan Teki wrote:
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > [...]
> > > > > 
> > > > > > > @@ -314,7 +321,9 @@ static const struct drm_bridge_funcs chipone_bridge_funcs = {
> > > > > > >     static int chipone_parse_dt(struct chipone *icn)
> > > > > > >     {
> > > > > > >            struct device *dev = icn->dev;
> > > > > > > +       struct device_node *endpoint;
> > > > > > >            struct drm_panel *panel;
> > > > > > > +       int dsi_lanes;
> > > > > > >            int ret;
> > > > > > > 
> > > > > > >            icn->vdd1 = devm_regulator_get_optional(dev, "vdd1");
> > > > > > > @@ -350,15 +359,42 @@ static int chipone_parse_dt(struct chipone *icn)
> > > > > > >                    return PTR_ERR(icn->enable_gpio);
> > > > > > >            }
> > > > > > > 
> > > > > > > +       endpoint = of_graph_get_endpoint_by_regs(dev->of_node, 0, 0);
> > > > > > > +       dsi_lanes = of_property_count_u32_elems(endpoint, "data-lanes");
> > > > > > > +       icn->host_node = of_graph_get_remote_port_parent(endpoint);
> > > > > > > +       of_node_put(endpoint);
> > > > > > > +
> > > > > > > +       if (!icn->host_node)
> > > > > > > +               return -ENODEV;
> > > > > > 
> > > > > > The non-ports-based OF graph returns a -19 example on the Allwinner
> > > > > > Display pipeline in R16 [1].
> > > > > > 
> > > > > > We need to have a helper to return host_node for non-ports as I have
> > > > > > done it for drm_of_find_bridge.
> > > > > > 
> > > > > > [1] https://patchwork.amarulasolutions.com/patch/1805/
> > > > > 
> > > > > The link points to a patch marked "DO NOT MERGE", maybe that patch is
> > > > > missing the DSI host port@0 OF graph link ? Both port@0 and port@1 are
> > > > > required, see:
> > > > > 
> > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/display/bridge/chipone,icn6211.yaml#n53
> > > > > 
> > > > > What is "non-ports-based OF graph" ?
> > > > > 
> > > > > I don't see drm_of_find_bridge() in linux-next , what is that ?
> > > > 
> > > > port@0 is optional as some of the DSI host OF-graph represent the
> > > > bridge or panel as child nodes instead of ports. (i think dt-binding
> > > > has to fix it to make port@0 optional)
> > > 
> > > The current upstream DT binding document says:
> > > 
> > >      required:
> > >        - port@0
> > >        - port@1
> > > 
> > > So port@0 is mandatory.
> > 
> > In the binding, sure, but fundamentally the DT excerpt Jagan provided is
> > correct. If the bridge supports DCS, there's no reason to use the OF
> > graph in the first place: the bridge node will be a child node of the
> > MIPI-DSI controller (and there's no obligation to use the OF-graph for a
> > MIPI-DSI controller).
> > 
> > I believe port@0 should be made optional (or downright removed if
> > MIPI-DCS in the only control bus).
> 
> That's out of scope of this series anyway, so Jagan can implement patches
> for that mode if needed.

Not really? You can't count on the port@0 being there generally
speaking, so you can't count on data-lanes being there either, which
exactly what you're doing in this patch.

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-03-08 13:49 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04  0:24 [PATCH V3 00/13] drm: bridge: icn6211: Fix hard-coded panel settings and add I2C support Marek Vasut
2022-03-04  0:24 ` [PATCH V3 01/13] dt-bindings: display: bridge: icn6211: Document DSI data-lanes property Marek Vasut
2022-03-04  0:24   ` Marek Vasut
2022-03-07 23:32   ` Rob Herring
2022-03-07 23:32     ` Rob Herring
2022-03-08 12:45   ` Maxime Ripard
2022-03-08 12:45     ` Maxime Ripard
2022-03-04  0:24 ` [PATCH V3 02/13] drm: bridge: icn6211: Fix register layout Marek Vasut
2022-03-04  0:24 ` [PATCH V3 03/13] drm: bridge: icn6211: Fix HFP_HSW_HBP_HI and HFP_MIN handling Marek Vasut
2022-03-04  0:24 ` [PATCH V3 04/13] drm: bridge: icn6211: Add HS/VS/DE polarity handling Marek Vasut
2022-03-08 12:46   ` Maxime Ripard
2022-03-04  0:25 ` [PATCH V3 05/13] drm: bridge: icn6211: Add DSI lane count DT property parsing Marek Vasut
2022-03-08  8:03   ` Jagan Teki
2022-03-08  9:49     ` Marek Vasut
2022-03-08 10:07       ` Jagan Teki
2022-03-08 10:29         ` Marek Vasut
2022-03-08 11:32           ` Jagan Teki
2022-03-08 12:51           ` Maxime Ripard
2022-03-08 13:27             ` Marek Vasut
2022-03-08 13:49               ` Maxime Ripard [this message]
2022-03-08 14:47                 ` Marek Vasut
2022-03-08 16:21                   ` Maxime Ripard
2022-03-08 21:41                     ` Marek Vasut
2022-03-10 10:53                       ` Maxime Ripard
2022-03-10 12:47                         ` Marek Vasut
2022-03-10 14:18                           ` Maxime Ripard
2022-03-11 10:36                             ` Marek Vasut
2022-03-11 16:29                               ` Maxime Ripard
2022-03-11 19:56                                 ` Marek Vasut
2022-03-11 20:35                                   ` Jagan Teki
2022-03-11 20:38                                     ` Jagan Teki
2022-03-11 21:11                                       ` Marek Vasut
2022-03-10 10:42             ` Laurent Pinchart
2022-03-10 10:57               ` Maxime Ripard
2022-03-10 11:16                 ` Laurent Pinchart
2022-03-10 14:23                   ` Maxime Ripard
2022-03-04  0:25 ` [PATCH V3 06/13] drm: bridge: icn6211: Add generic DSI-to-DPI PLL configuration Marek Vasut
2022-03-08  8:07   ` Jagan Teki
2022-03-08 10:11     ` Marek Vasut
2022-03-04  0:25 ` [PATCH V3 07/13] drm: bridge: icn6211: Use DSI burst mode without EoT and with LP command mode Marek Vasut
2022-03-04  0:25 ` [PATCH V3 08/13] drm: bridge: icn6211: Disable DPI color swap Marek Vasut
2022-03-04  0:25 ` [PATCH V3 09/13] drm: bridge: icn6211: Set SYS_CTRL_1 to value used in examples Marek Vasut
2022-03-04  0:25 ` [PATCH V3 10/13] drm: bridge: icn6211: Implement atomic_get_input_bus_fmts Marek Vasut
2022-03-04  0:25 ` [PATCH V3 11/13] drm: bridge: icn6211: Add I2C configuration support Marek Vasut
2022-03-04  0:25 ` [PATCH V3 12/13] drm: bridge: icn6211: Rework ICN6211_DSI to chipone_writeb() Marek Vasut
2022-03-04  0:25 ` [PATCH V3 13/13] drm: bridge: icn6211: Read and validate chip IDs before configuration Marek Vasut

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=20220308134921.zebs533xeazq46ts@houat \
    --to=maxime@cerno.tech \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=marex@denx.de \
    --cc=robert.foss@linaro.org \
    --cc=sam@ravnborg.org \
    --cc=tzimmermann@suse.de \
    /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: link
Be 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.