linux-kernel - Re: v5.15-rcX regression: video devices on i.MX6 are not created

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGETcx8qsJQNkEHYgqihqHuFu8sgC5DDsnG9yQ=_e_hiC43z-w@mail.gmail.com>
Date:   Wed, 6 Oct 2021 15:14:59 -0700
From:   Saravana Kannan <saravanak@...gle.com>
To:     Krzysztof Hałasa <khalasa@...p.pl>
Cc:     Fabio Estevam <festevam@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Frank Rowand <frowand.list@...il.com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-media <linux-media@...r.kernel.org>
Subject: Re: v5.15-rcX regression: video devices on i.MX6 are not created

On Tue, Oct 5, 2021 at 9:56 PM Krzysztof Hałasa <khalasa@...p.pl> wrote:
>
> Hi Fabio, Saravana,
>
> Fabio Estevam <festevam@...il.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.

Ah, I helped Phillip come up with that fix. I didn't realize this was
the same issue. Glad that I have one less issue to debug :)

-Saravana