mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Subject: Re: [PATCH v5 03/10] media: rcar-csi2: Move {enable|disable}_streams() calls
Date: Wed, 17 Jun 2026 12:33:42 +0300	[thread overview]
Message-ID: <6b409b1d-2b18-4d72-bdfb-18d2d0f536c6@ideasonboard.com> (raw)
In-Reply-To: <20260616140420.GA1662668@fsdn.se>

Hi,

On 16/06/2026 17:04, Niklas Söderlund wrote:

>>>> rcsi2_irq_thread() also calls rcsi2_stop(), followed by rcsi2_start().
>>>> This is to handle errors reported by the AFIFO_OF, ERRSOTHS and
>>>> ERRSOTSYNCHS interrupts. If the source isn't restarted, such an attempt
>>>> to recover from errors will likely fail. On the other hand, restarting
>>>> the source will likely not lead to great results either.
>>>
>>> Indeed. I think for single-stream use cases the behavior should still be
>>> the same, but for multi-stream use, any enabled stream will keep the
>>> csi2 enabled.
>>>
>>> This kind of error handling sounds a bit fragile. If a restart helps,
>>> don't we need to restart the whole pipeline, not just from csi2-rx
>>> upwards? Or is it guaranteed that the ISP/CS and VIN will continue working?
>>
>> My feeling is that these kind of errors would be best handled in
>> userspace.
> 
> I agree this should be handled in user-space. But since we have (or at
> least did not when this was added) no way to signal to user-space that
> an error have occurred and that action is needed this at least solved
> the error reported by the user.
> 
> If we think this is should be dropped and somehow signal user-space that
> action is needed that is OK for me. But then please remove all of it.
> 
>>
>>> Did this work earlier with the custom VC based routing?
>>
>> That I don't know.
> 
> It did. At least for the only way I had to create the error condition by
> "hot plugging" the CVBS input IIRC.
I think what I could try here is to call v4l2_subdev_disable_streams() 
from rcsi2_irq_thread(), disabling all currently enabled streams from 
the source, and then v4l2_subdev_enable_streams() them back. In theory 
that should do the same as the current code.

I also realized I have a bug here: enable streams does a 
"priv->stream_count += 1", regardless of how many streams the 
source_streams_mask mask contains... I need to check if this same 
pattern is present elsewhere.

  Tomi


  reply	other threads:[~2026-06-17  9:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 13:53 [PATCH v5 00/10] media: rcar: Streams support Tomi Valkeinen
2026-03-11 13:53 ` [PATCH v5 01/10] media: rcar-vin: Link VINs on Gen3 to a single channel on each CSI-2 Tomi Valkeinen
2026-04-04 12:09   ` Niklas Söderlund
2026-03-11 13:53 ` [PATCH v5 02/10] media: rcar-isp: Move {enable|disable}_streams() calls Tomi Valkeinen
2026-03-18 20:44   ` Laurent Pinchart
2026-03-11 13:53 ` [PATCH v5 03/10] media: rcar-csi2: " Tomi Valkeinen
2026-03-18 20:54   ` Laurent Pinchart
2026-04-04 12:19     ` Niklas Söderlund
2026-06-16 12:35       ` Laurent Pinchart
2026-06-16 11:20     ` Tomi Valkeinen
2026-06-16 12:34       ` Laurent Pinchart
2026-06-16 14:04         ` Niklas Söderlund
2026-06-17  9:33           ` Tomi Valkeinen [this message]
2026-03-11 13:53 ` [PATCH v5 04/10] media: rcar-csi2: Switch to Streams API Tomi Valkeinen
2026-03-18 21:04   ` Laurent Pinchart
2026-06-16 11:22     ` Tomi Valkeinen
2026-06-16 12:27       ` Laurent Pinchart
2026-06-16 13:26         ` Tomi Valkeinen
2026-06-16 13:41           ` Laurent Pinchart
2026-03-11 13:53 ` [PATCH v5 05/10] media: rcar-isp: " Tomi Valkeinen
2026-03-18 21:12   ` Laurent Pinchart
2026-03-11 13:53 ` [PATCH v5 06/10] media: rcar-csi2: Add .get_frame_desc op Tomi Valkeinen
2026-03-18 21:16   ` Laurent Pinchart
2026-06-16 11:30     ` Tomi Valkeinen
2026-06-16 12:30       ` Laurent Pinchart
2026-06-16 13:12         ` Tomi Valkeinen
2026-06-16 13:21           ` Laurent Pinchart
2026-03-11 13:53 ` [PATCH v5 07/10] media: rcar-isp: Call get_frame_desc to find out VC & DT Tomi Valkeinen
2026-03-11 13:53 ` [PATCH v5 08/10] media: rcar-csi2: Call get_frame_desc to find out VC & DT (Gen3) Tomi Valkeinen
2026-03-11 13:53 ` [PATCH v5 09/10] media: rcar-csi2: Add full streams support Tomi Valkeinen
2026-03-11 13:53 ` [PATCH v5 10/10] media: rcar-isp: " Tomi Valkeinen
2026-03-11 17:38 ` [PATCH v5 00/10] media: rcar: Streams support Niklas Söderlund
2026-03-11 18:03   ` Tomi Valkeinen
2026-03-18 20:33 ` 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=6b409b1d-2b18-4d72-bdfb-18d2d0f536c6@ideasonboard.com \
    --to=tomi.valkeinen@ideasonboard.com \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --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

all inboxes | Powered by JetHome®