From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: David CARLIER <devnexen@gmail.com>
Cc: Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
dan.scally@ideasonboard.com, nayden.kanchev@arm.com,
mchehab@kernel.org, hverkuil+cisco@kernel.org,
linusw@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: mali-c55: Require an enabled link to start a video node
Date: Tue, 10 Nov 2026 10:00:18 +0100 [thread overview]
Message-ID: <avLYoCrMB_L3gTPT@zed> (raw)
In-Reply-To: <CA+XhMqwfK+zoXb2_9XBUnjd9cLY_D0WwykbSccQR6kKqriZezA@mail.gmail.com>
Hi David
On Tue, Nov 10, 2026 at 08:32:00AM +0000, David CARLIER wrote:
> Fair point, sorry for the shortcuts.
>
> > What does it mean "rather than through the graph" ?
> > enable_streams() is propagated by drivers along the pipeline by design
>
> Badly worded, sorry. I only meant that start_streaming() takes the
> resizer from cap_dev->rsz rather than from the remote end of an enabled
> link, so it enables it even with the link disabled.
>
> > Is this a typo ? From FR we can't go to the DS resizer.
>
> Not for data, no. I meant the media_pipeline_populate() walk: from the
Ah ok
> ISP source video pad it follows the immutable link into the DS resizer
> sink pad and, through the internal route, its source pad. A
> MUST_CONNECT on that pad would then fail FR only streaming with the DS
> link disabled.
This means (and reading Documentation/admin-guide/media/mali-c55.rst I
think it was intended) that if you link-enable the DS-pipe you will have to
start streaming on the DS capture node, otherwise streaming will never
start due to mali_c55_pipeline_ready() returning false ?
I wish I had a system with a DS pipe to test with.
What I'm after here: I'm trying to figure out if your change
introduces any requirement on how pipe have to be handled and if this
has any implication on how libcamera works on mali.
A use case is continous capture from DS while only taking seldom
pictures from FR. In this case I have to link both pipes, start both
of them and feed buffers continuously to DS and only sporadically to
FR. The key here is the requirement to call STREAMON on both capture
nodes if they're linked.
In other words, if you want to use both pipes you need to link both of them
and call STREAMON on both capture devices, even if in a session you will be
capturing from one of them.
I think it's fine and matches the documentation in mali-c55.rst and
the libcamera pipeline handler.
>
> Thanks for the reviews.
> Cheers.
prev parent reply other threads:[~2026-11-10 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 23:15 David Carlier
2026-11-09 9:26 ` Linus Walleij
2026-11-10 8:26 ` Jacopo Mondi
2026-11-09 15:52 ` Jacopo Mondi
[not found] ` <CA+XhMqyKNd2maRXmmpL=aOMB-z4X3JgCD5ofiHpMubtFHuS_0g@mail.gmail.com>
2026-11-10 8:25 ` Jacopo Mondi
[not found] ` <CA+XhMqwfK+zoXb2_9XBUnjd9cLY_D0WwykbSccQR6kKqriZezA@mail.gmail.com>
2026-11-10 9:00 ` Jacopo Mondi [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=avLYoCrMB_L3gTPT@zed \
--to=jacopo.mondi@ideasonboard.com \
--cc=dan.scally@ideasonboard.com \
--cc=devnexen@gmail.com \
--cc=hverkuil+cisco@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nayden.kanchev@arm.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
all inboxes | Powered by JetHome®