From: Rob Herring <robh@kernel.org>
To: Vinay Simha B N <simhavcs@gmail.com>
Cc: "open list:DRM DRIVER FOR MSM ADRENO GPU"
<freedreno@lists.freedesktop.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: graph connection to node is not bidirectional kernel-5.6.0-rc6
Date: Thu, 19 Mar 2020 09:46:36 -0600 [thread overview]
Message-ID: <CAL_JsqLz-0myc-PSSaCQWDFXQx+=X9nBSXWsJaGCVqTFn0d5kw@mail.gmail.com> (raw)
In-Reply-To: <CAGWqDJ7AccvoxjKfQJ3GytJ-+u56Bk3rEn0sSYv-zCuBe1brAg@mail.gmail.com>
On Thu, Mar 19, 2020 at 1:31 AM Vinay Simha B N <simhavcs@gmail.com> wrote:
>
> hi,
>
> I am getting the endpoint' is not bidirectional(d2l_in, dsi0_out)
> warning in compilation, built boot image works on qcom apq8016-ifc6309
> board with the dsi->bridge->lvds panel.
> Because of this warning i cannot create a .yaml documentation examples.
> Please suggest.
>
> tc_bridge: bridge@f {
^^^^^^^^
> arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi:253.28-255.9: Warning
> (graph_endpoint): /soc/i2c@78b8000/bridge@39/ports/port@0/endpoint:
^^^^^^^^^
Looks like you have 2 different bridges.
Rob
next prev parent reply other threads:[~2020-03-19 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 7:31 graph connection to node is not bidirectional kernel-5.6.0-rc6 Vinay Simha B N
2020-03-19 15:46 ` Rob Herring [this message]
2020-03-19 15:56 ` Vinay Simha B N
2020-03-19 17:06 ` Rob Herring
2020-03-19 17:16 ` Vinay Simha B N
2020-03-20 4:32 ` Vinay Simha B N
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='CAL_JsqLz-0myc-PSSaCQWDFXQx+=X9nBSXWsJaGCVqTFn0d5kw@mail.gmail.com' \
--to=robh@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simhavcs@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).