From: Philipp Zabel <p.zabel@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: 'bad remote port parent' warnings
Date: Thu, 22 Nov 2018 17:27:45 +0100 [thread overview]
Message-ID: <1542904065.16720.2.camel@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5DP8JEMfjXJ8Hihm684+3=pOoCo1Gz7kt-TnCB7h-8EvA@mail.gmail.com>
On Tue, 2018-11-20 at 10:10 -0200, Fabio Estevam wrote:
> Hi,
>
> On a imx6q-wandboard running linux-next 20181120 there the following warnings:
>
> [ 4.327794] video-mux 20e0000.iomuxc-gpr:ipu1_csi0_mux: bad remote
> port parent
> [ 4.336118] video-mux 20e0000.iomuxc-gpr:ipu2_csi1_mux: bad remote
> port parent
>
> Is there anything we should do to prevent this from happening?
There are empty endpoint nodes (without remote-endpoint property)
labeled ipu1_csi[01]_mux_from_parallel_sensor in the i.MX6 device trees
for board DT implementers' convenience. See commit 2539f517acbdc ("ARM:
dts: imx6qdl: Add video multiplexers, mipi_csi, and their connections").
We had a discussion about this issue in February when this caused a
probing error: https://patchwork.kernel.org/patch/10234469/
We could demote the warning to a debug message, make the wording a bit
less misleading (there is no bad remote port parent, there is just no
remote endpoint at all), or we could just accept the error message for
old DTBs and mark these empty endpoint nodes with the /omit-if-no-ref/
keyword to let dtc remove them if they are unused.
regards
Philipp
next prev parent reply other threads:[~2018-11-23 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 12:10 'bad remote port parent' warnings Fabio Estevam
2018-11-20 12:15 ` Sakari Ailus
2018-11-20 12:21 ` Fabio Estevam
2018-11-22 16:27 ` Philipp Zabel [this message]
2018-11-22 19:17 ` Fabio Estevam
2018-11-23 12:35 ` Sakari Ailus
2018-11-23 12:54 ` Fabio Estevam
2018-11-23 22:37 ` Steve Longerbeam
2018-11-24 15:20 ` Fabio Estevam
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=1542904065.16720.2.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=festevam@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=slongerbeam@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).