From: Maud Spierings <maudspierings@gocontroll.com>
To: Fabio Estevam <festevam@gmail.com>, Tim Harvey <tharvey@gateworks.com>
Cc: Laurent.pinchart@ideasonboard.com, mchehab@kernel.org,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-media@vger.kernel.org, imx@lists.linux.dev
Subject: Re: Kernel Panic when trying to capture camera with ffmpeg on imx8mp
Date: Wed, 13 Aug 2025 13:31:34 +0200 [thread overview]
Message-ID: <8d4d8d75-fe89-4c6f-b8af-2f90d7e370e9@gocontroll.com> (raw)
In-Reply-To: <CAOMZO5C3o+UaLRaXfB+sfmgB801mNTLztE_cy-e5duKDAL-1Hg@mail.gmail.com>
On 8/13/25 13:23, Fabio Estevam wrote:
> Hi Maud,
>
> [Adding Tim]
>
> On Wed, Aug 13, 2025 at 8:12 AM Maud Spierings
> <maudspierings@gocontroll.com> wrote:
>
>> My devicetree setup is practically identical to the one in
>> freescale/imx8mp-venice-gw74xx-imx219.dtso (different i2c bus and
>> regulator gpio only)
>
> You'll need to configure the camera pipeline using media-ctl commands.
>
> Take a look at:
> https://trac.gateworks.com/wiki/venice/multimedia#MediaControllerPipeline
I have been messing around with that, but it still shouldn't panic right?
It seems to be happen in:
sd = media_entity_to_v4l2_subdev(pad->entity);
in mxc_isi_crossbar_xlate_streams()
Checking now if the pad variable is the issue
it seems media_pad_remote_pad_first() can return NULL which would cause
the issue there I think.
next prev parent reply other threads:[~2025-08-13 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 11:11 Kernel Panic when trying to capture camera with ffmpeg on imx8mp Maud Spierings
2025-08-13 11:23 ` Fabio Estevam
2025-08-13 11:31 ` Maud Spierings [this message]
2025-08-13 11:35 ` Laurent Pinchart
2025-08-13 11:41 ` Maud Spierings
2025-08-13 11:41 ` Laurent Pinchart
2025-08-13 11:45 ` Maud Spierings
2025-08-13 11:57 ` Laurent Pinchart
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=8d4d8d75-fe89-4c6f-b8af-2f90d7e370e9@gocontroll.com \
--to=maudspierings@gocontroll.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.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).