All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>, linux-media@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: [PATCH 0/4] media: videobuf2: Add a transfer error event
Date: Mon,  8 Nov 2021 17:02:16 +0100	[thread overview]
Message-ID: <20211108160220.767586-1-niklas.soderlund+renesas@ragnatech.se> (raw)

Hello,

This series adds a new V4L2 event, V4L2_EVENT_XFER_ERROR. This new event 
is intended to be used when a device in the capturing pipeline 
encounters an unrecoverable error and needs to inform the capturing 
application thru the video node about the error.

The fist use-case for this is also demonstrated in this series by the 
R-Car CSI-2 receiver that generates the new event when it detects an 
error on the bus.

Patch 1/4 is a bug fix for the R-Car VIN driver that was found while 
working on this series. This patch is good to be picked-up on it's own 
but is a requirement for later patches in this series so I have opted to 
include it here as the first patch. 

Patch 2/4 adds the new V4L2 event. While patch 3/4 and 4/4 makes use of 
it in the R-Car capture pipeline. Careful readers will note that the 
last to patches already have a patch history. This is because they have 
been part of an earlier attempt a while back to solve this issue in a 
different way, and during those discussions the need for this new event 
was found.

Niklas Söderlund (4):
  media: rcar-vin: Free buffers with error if hardware stop fails
  media: videobuf2: Add a transfer error event
  rcar-vin: Stop stream when subdevice signal transfer error
  rcar-csi2: Do not try to recover after transfer error

 .../userspace-api/media/v4l/vidioc-dqevent.rst  |  5 +++++
 .../media/videodev2.h.rst.exceptions            |  1 +
 drivers/media/platform/rcar-vin/rcar-csi2.c     | 17 +++++++++--------
 drivers/media/platform/rcar-vin/rcar-dma.c      | 10 ++++++++++
 drivers/media/platform/rcar-vin/rcar-v4l2.c     | 17 ++++++++++++++++-
 include/uapi/linux/videodev2.h                  |  1 +
 6 files changed, 42 insertions(+), 9 deletions(-)

-- 
2.33.1


             reply	other threads:[~2021-11-08 16:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 16:02 Niklas Söderlund [this message]
2021-11-08 16:02 ` [PATCH 1/4] media: rcar-vin: Free buffers with error if hardware stop fails Niklas Söderlund
2021-11-15 14:36   ` Hans Verkuil
2021-11-08 16:02 ` [PATCH 2/4] media: videobuf2: Add a transfer error event Niklas Söderlund
2022-03-02 15:40   ` Michael Rodin
2021-11-08 16:02 ` [PATCH 3/4] rcar-vin: Stop stream when subdevice signal transfer error Niklas Söderlund
2021-11-08 17:36   ` Hans Verkuil
2021-11-08 18:42     ` Niklas Söderlund
2021-11-15 14:26       ` Hans Verkuil
2022-03-02 16:48         ` Michael Rodin
2022-03-02 20:17           ` Niklas Söderlund
2022-03-06 20:01             ` Michael Rodin
2022-03-07 15:26               ` Niklas Söderlund
2022-03-09 19:27                 ` Michael Rodin
2022-05-19 18:09                   ` Michael Rodin
2021-11-08 16:02 ` [PATCH 4/4] rcar-csi2: Do not try to recover after " Niklas Söderlund

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=20211108160220.767586-1-niklas.soderlund+renesas@ragnatech.se \
    --to=niklas.soderlund+renesas@ragnatech.se \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.