From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Saravana Kannan <saravanak@google.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: v5.15-rcX regression: video devices on i.MX6 are not created
Date: Mon, 04 Oct 2021 14:19:17 +0200 [thread overview]
Message-ID: <m3lf39nfsq.fsf@t19.piap.pl> (raw)
Hi Saravana et al.,
FYI the patch: 6b2117ad65f1bca9ece6d4b1ee784b42701a2d86
of: property: fw_devlink: Add support for "resets" and "pwms"
Allows better tracking of dependencies between devices.
drivers/of/property.c | 4 ++++
breaks v4l2 video devices on an i.MX6 CPU. The /dev/video* nodes are not
created, and the drivers (async subdevicess) are "waiting":
# cat /sys/kernel/debug/v4l2-async/pending_async_subdevices
imx-media:
[fwnode] dev=nil, node=/soc/ipu@2400000/port@0
[fwnode] dev=nil, node=/soc/ipu@2400000/port@1
[fwnode] dev=nil, node=/soc/ipu@2800000/port@0
[fwnode] dev=nil, node=/soc/ipu@2800000/port@1
imx6-mipi-csi2:
[fwnode] dev=0-0036, node=/soc/bus@2100000/i2c@21a0000/camera@36
ipu2_csi1_mux:
ipu1_csi0_mux:
[fwnode] dev=21dc000.mipi, node=/soc/bus@2100000/mipi@21dc000
Reverting the patch (or commenting the "resets" out) fixes the problem:
# cat /sys/kernel/debug/v4l2-async/pending_async_subdevices
ipu2_csi1:
ipu2_csi0:
ipu1_csi1:
ipu1_csi0:
imx-media:
imx6-mipi-csi2:
ipu2_csi1_mux:
ipu1_csi0_mux:
What now?
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next reply other threads:[~2021-10-04 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 12:19 Krzysztof Hałasa [this message]
2021-10-06 0:09 ` Saravana Kannan
2021-10-06 2:23 ` Fabio Estevam
2021-10-06 4:56 ` Krzysztof Hałasa
2021-10-06 22:14 ` Saravana Kannan
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=m3lf39nfsq.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.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
Powered by JetHome