linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gaël PORTAY" <gael.portay@collabora.com>
To: Steve Longerbeam <slongerbeam@gmail.com>
Cc: linux-media@vger.kernel.org, Peter Seiderer <ps.report@gmx.net>
Subject: Re: [PATCH v4 0/3] media: imx: Stop stream before disabling IDMA channels
Date: Tue, 22 Jan 2019 09:45:49 -0500	[thread overview]
Message-ID: <20190122144549.zznkilfwnf2gv2on@archlinux.localdomain> (raw)
In-Reply-To: <20190121233552.20001-1-slongerbeam@gmail.com>

Steve,

On Mon, Jan 21, 2019 at 03:35:49PM -0800, Steve Longerbeam wrote:
> Repeatedly sending a stream off immediately followed by stream on can
> eventually cause a complete system hard lockup on the SabreAuto when
> streaming from the ADV7180:
> 
> while true; do v4l2-ctl  -d4 --stream-mmap --stream-count=3; done
> 
> Eventually this either causes the system lockup or EOF timeouts at all
> subsequent stream on, until a system reset.
> 
> The lockup occurs when disabling the IDMA channels at stream off. Stopping
> the video data stream entering the IDMA channel before disabling the
> channel itself appears to be a reliable fix for the hard lockup.
> 
> In the CSI subdevice, this can be done by disabling the CSI before
> disabling the CSI IDMA channel, instead of after. In the IC-PRPENVVF
> subdevice, this can be done by stopping upstream before disabling the
> PRPENC/VF IDMA channel.
> 
> History:
> v4:
> - Disabling SMFC will have no effect if both CSI's are streaming. So
>   go back to disabling CSI before channel as in v2, but split up
>   csi_idmac_stop such that ipu_csi_disable can still be called within
>   csi_stop.
> 
> v3:
> - Switch to disabling the SMFC before the channel, instead of the CSI
>   before the channel.
> 
> v2:
> - Whitespace fixes
> - Add Fixes: and Cc: stable@vger.kernel.org
> - No functional changes.
> 
> 
> Steve Longerbeam (3):
>   media: imx: csi: Disable CSI immediately after last EOF
>   media: imx: csi: Stop upstream before disabling IDMA channel
>   media: imx: prpencvf: Stop upstream before disabling IDMA channel
> 
>  drivers/staging/media/imx/imx-ic-prpencvf.c | 26 ++++++++-----
>  drivers/staging/media/imx/imx-media-csi.c   | 42 +++++++++++++--------
>  2 files changed, 44 insertions(+), 24 deletions(-)
> 
> -- 
> 2.17.1
> 

The system is still up and running this morning after a whole night long
of tests.

You have my Tested-by.

Thanks,
Gael

      parent reply	other threads:[~2019-01-22 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 23:35 [PATCH v4 0/3] media: imx: Stop stream before disabling IDMA channels Steve Longerbeam
2019-01-21 23:35 ` [PATCH v4 1/3] media: imx: csi: Disable CSI immediately after last EOF Steve Longerbeam
2019-01-21 23:35 ` [PATCH v4 2/3] media: imx: csi: Stop upstream before disabling IDMA channel Steve Longerbeam
2019-01-21 23:35 ` [PATCH v4 3/3] media: imx: prpencvf: " Steve Longerbeam
2019-01-22  7:34 ` [PATCH v4 0/3] media: imx: Stop stream before disabling IDMA channels Hans Verkuil
2019-01-27 22:41   ` Steve Longerbeam
2019-01-22 14:45 ` Gaël PORTAY [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=20190122144549.zznkilfwnf2gv2on@archlinux.localdomain \
    --to=gael.portay@collabora.com \
    --cc=linux-media@vger.kernel.org \
    --cc=ps.report@gmx.net \
    --cc=slongerbeam@gmail.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).