From: Antti Laakso <antti.laakso@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, "Yan,
Dongcheng" <dongcheng.yan@intel.com>,
Mehdi Djait <mehdi.djait@linux.intel.com>,
"Yu, Ong Hock" <ong.hock.yu@intel.com>,
"Ng, Khai Wen" <khai.wen.ng@intel.com>,
"Bajpai, Manik" <manik.bajpai@intel.com>,
Divyamani Tripathi <divyamani.tripathi@intel.com>,
"Sapre, Sarang" <sarang.sapre@intel.com>,
"Yao, Hao" <hao.yao@intel.com>
Subject: Re: [PATCH v2 0/5] IPU reset workaround changes
Date: Wed, 14 Oct 2026 16:05:15 +0300 [thread overview]
Message-ID: <as9-C50a3C69v_al@alaakso-desk> (raw)
In-Reply-To: <20261012114002.3970409-1-sakari.ailus@linux.intel.com>
Hi Sakari,
On Mon, Oct 12, 2026 at 02:39:57PM +0300, Sakari Ailus wrote:
> Hi folks,
>
> Maybe I should have labelled these as RFC instead... this set reworks based on
> what the ISYS is reset and how that affects UAPI.
>
> It seems there are some issues on IPU7; at times (around once in a few hundred
> cases) streaming with yavta results capturing a single frame only and an ISYS
> power reset is needed to recover from that. No reboot (or driver reload) is
> needed with these patches though.
>
> Similarly with these, an ISYS reset is avoided in regular streaming cases for
> IPU7.
>
> Comments are welcome (as always).
>
> since v1:
>
> - Fix error handling in start_streaming() in the 4th patch.
>
Reviewed-by: Antti Laakso <antti.laakso@linux.intel.com>
> Sakari Ailus (5):
> media: ipu6: Don't mark need_reset based on returned buffers
> media: ipu6: Tell about not being able to obtain frame descriptor
> media: ipu6: Prevent starting streaming if ISYS needs reset
> media: ipu6: Remove need_reset check from video device open
> media: ipu6: Return errors from stream stop and close
>
> drivers/media/pci/intel/ipu6/ipu6-isys-csi2.c | 6 +-
> .../media/pci/intel/ipu6/ipu6-isys-queue.c | 18 ++---
> .../media/pci/intel/ipu6/ipu6-isys-video.c | 74 +++++++++++--------
> .../media/pci/intel/ipu6/ipu6-isys-video.h | 4 +-
> 4 files changed, 55 insertions(+), 47 deletions(-)
>
>
> base-commit: d7e7bca7169873b46e857c025c10f3336c1258d8
> --
> 2.47.3
>
>
prev parent reply other threads:[~2026-10-14 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 11:39 [PATCH v2 0/5] IPU reset workaround changes Sakari Ailus
2026-10-12 11:39 ` [PATCH v2 1/5] media: ipu6: Don't mark need_reset based on returned buffers Sakari Ailus
2026-10-12 11:39 ` [PATCH v2 2/5] media: ipu6: Tell about not being able to obtain frame descriptor Sakari Ailus
2026-10-12 11:40 ` [PATCH v2 3/5] media: ipu6: Prevent starting streaming if ISYS needs reset Sakari Ailus
2026-10-12 11:40 ` [PATCH v2 4/5] media: ipu6: Remove need_reset check from video device open Sakari Ailus
2026-10-12 11:40 ` [PATCH v2 5/5] media: ipu6: Return errors from stream stop and close Sakari Ailus
2026-10-12 12:20 ` Antti Laakso
2026-10-14 13:05 ` Antti Laakso [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=as9-C50a3C69v_al@alaakso-desk \
--to=antti.laakso@linux.intel.com \
--cc=divyamani.tripathi@intel.com \
--cc=dongcheng.yan@intel.com \
--cc=hao.yao@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 \
--cc=sarang.sapre@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