Linux Media Controller development
 help / color / mirror / Atom feed
From: Nicola Fiorillo <nicfio@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, dongcheng.yan@intel.com,
	mehdi.djait@linux.intel.com, ong.hock.yu@intel.com,
	khai.wen.ng@intel.com, antti.laakso@linux.intel.com,
	manik.bajpai@intel.com, divyamani.tripathi@intel.com,
	nicfio@gmail.com
Subject: Re: [PATCH v3 09/21] media: ipu6: Start streaming once all streams have started, stop when not
Date: Wed, 23 Sep 2026 16:54:21 +0200	[thread overview]
Message-ID: <179017526193.315162.9897874972042062382@gmail.com> (raw)
In-Reply-To: <20260922120538.896684-10-sakari.ailus@linux.intel.com>

Hi Sakari,

On Tue, Sep 22, 2026 at 03:05:26PM +0300, Sakari Ailus wrote:
> +static int ipu6_isys_csi2_streaming_change(struct ipu6_isys_subdev *asd,
> +					   struct v4l2_subdev_state *state,
> +					   u32 pad, u8 *vc, bool enable)

Thanks for picking up the return value and the inner loop key; both
read correctly to me in v3.

One question on the loop, again from reading only:

> +		struct media_pad *video_pad =
> +			media_pad_remote_pad_first(&asd->sd.entity.pads[route->source_pad]);
> +		struct ipu6_isys_video *av =
> +			container_of_const(video_pad, struct ipu6_isys_video,
> +					   pad);
> +
> +		streams_enabled++;
> +		if (av->streaming || (enable && pad == route->source_pad))

The CSI-2 source pad to video node links are created with no flags in
isys_csi2_create_media_links(), so they are neither immutable nor
enabled by default, and media_pad_remote_pad_first() returns NULL for a
pad whose link is disabled. With two active routes on the same virtual
channel, say one per source pad, and only one of the two video node
links enabled, streaming on the enabled node reaches the other route
here, and av->streaming is read through a pointer derived from NULL.

That does not need anything unusual: it is the multi-stream setup this
series prepares for, with one of the two outputs simply not in use.
Even without the oops, that route could never start streaming, so it
would hold back the first one forever.

Unless something earlier already rejects such a configuration and I
have missed it, skipping those routes would seem to cover both:

		if (!video_pad)
			continue;

Thanks,

--
Nicola Fiorillo

  reply	other threads:[~2026-09-23 14:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 12:05 [PATCH v3 00/21] IPU6 multi-stream and metadata support preparation Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 01/21] media: ipu6: Fix releasing resources at failing streamon Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 02/21] media: ipu6: Move streaming control to CSI-2 receiver driver Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 03/21] media: ipu6: Stream number on CSI-2 receiver source pads is always 0 Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 04/21] media: ipu6: Rename misnamed out_free_watermark label in video init Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 05/21] media: ipu6: Always request a capture ack Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 06/21] media: ipu6: Clean up link frequency calculation Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 07/21] media: ipu6: Get watermark configuration directly from ipdata Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 08/21] media: ipu6: Collect IPU streams into CSI-2 receiver sub-device context Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 09/21] media: ipu6: Start streaming once all streams have started, stop when not Sakari Ailus
2026-09-23 14:54   ` Nicola Fiorillo [this message]
2026-09-24 10:20     ` Sakari Ailus
2026-09-26 18:25   ` [PATCH v4 1/1] " Sakari Ailus
2026-09-27  5:03     ` Nicola Fiorillo
2026-09-22 12:05 ` [PATCH v3 10/21] media: ipu6: Add lockdep checks for CSI-2 streaming enable and disable Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 11/21] media: ipu6: Remove nr_queues and nr_streaming fields in ipu6_isys_stream Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 12/21] media: ipu6: Collect enabled stream IDs Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 13/21] media: ipu6: Avoid accessing av->streams before streaming Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 14/21] media: ipu6: Rework watermark calculation Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 15/21] media: ipu6: Rework watermark setting Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 16/21] media: ipu6: Bridge the gap between streams in V4L2 and IPU6 firmware Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 17/21] media: ipu6: Drop {get,put}_streams_opened() Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 18/21] media: ipu6: Serialise access to stream pointers by isys stream_lock Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 19/21] media: ipu6: Move firmware init/cleanup to RPM callbacks Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 20/21] media: ipu6: Don't track power status, rely on runtime PM Sakari Ailus
2026-09-22 12:05 ` [PATCH v3 21/21] media: ipu6: Support upstream sub-devices without get_frame_desc() Sakari Ailus
2026-09-23 12:04 ` [PATCH v3 00/21] IPU6 multi-stream and metadata support preparation Antti Laakso

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=179017526193.315162.9897874972042062382@gmail.com \
    --to=nicfio@gmail.com \
    --cc=antti.laakso@linux.intel.com \
    --cc=divyamani.tripathi@intel.com \
    --cc=dongcheng.yan@intel.com \
    --cc=khai.wen.ng@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=manik.bajpai@intel.com \
    --cc=mehdi.djait@linux.intel.com \
    --cc=ong.hock.yu@intel.com \
    --cc=sakari.ailus@linux.intel.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