All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saravana Kannan <saravanak@google.com>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: Fabio Estevam <festevam@gmail.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, 6 Oct 2021 15:14:59 -0700	[thread overview]
Message-ID: <CAGETcx8qsJQNkEHYgqihqHuFu8sgC5DDsnG9yQ=_e_hiC43z-w@mail.gmail.com> (raw)
In-Reply-To: <m38rz6oinj.fsf@t19.piap.pl>

On Tue, Oct 5, 2021 at 9:56 PM Krzysztof Hałasa <khalasa@piap.pl> wrote:
>
> 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.

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

      reply	other threads:[~2021-10-06 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 12:19 v5.15-rcX regression: video devices on i.MX6 are not created 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
2021-10-06 22:14       ` Saravana Kannan [this message]

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='CAGETcx8qsJQNkEHYgqihqHuFu8sgC5DDsnG9yQ=_e_hiC43z-w@mail.gmail.com' \
    --to=saravanak@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=khalasa@piap.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.