From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Fabio Estevam <festevam@gmail.com>
Cc: Saravana Kannan <saravanak@google.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: v5.15-rcX regression: video devices on i.MX6 are not created
Date: Wed, 06 Oct 2021 06:56:48 +0200 [thread overview]
Message-ID: <m38rz6oinj.fsf@t19.piap.pl> (raw)
In-Reply-To: <CAOMZO5DwcXUe5j97n4Q_RF9WRo2DYoToe7FLNbpDJhn_BxuH0w@mail.gmail.com> (Fabio Estevam's message of "Tue, 5 Oct 2021 23:23:38 -0300")
Hi Fabio, Saravana,
Fabio Estevam <festevam@gmail.com> writes:
>> > 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":
>
> Phillip has sent a fix for this issue:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2021-October/687868.html
This patch makes the /dev/video* devices to show up on my i.MX6-based
system again, so I consider the problem fixed. Thanks.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
next prev parent reply other threads:[~2021-10-06 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 12:19 Krzysztof Hałasa
2021-10-06 0:09 ` Saravana Kannan
2021-10-06 2:23 ` Fabio Estevam
2021-10-06 4:56 ` Krzysztof Hałasa [this message]
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=m38rz6oinj.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--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