[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250614141545.2860860-1-niklas.soderlund+renesas@ragnatech.se>
Date: Sat, 14 Jun 2025 16:15:42 +0200
From: Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
To: Mauro Carvalho Chehab <mchehab@...nel.org>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-media@...r.kernel.org,
linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Niklas Söderlund <niklas.soderlund+renesas@...natech.se>
Subject: [PATCH 0/3] media: rcar-vin: Generate FRAME_SYNC events
Hi,
This series extend the VIN interrupt handling to be able to generate
FRAME_SYNC events. Having these events in user-space is a great help to
know when a sensor starts to expose a new frame.
Patch 1/3 and 2/3 prepays the existing interrupt infrastructure to
support more then "frame captured" interrupts. While patch 3/3 enables
and checks for VSYNC detection and generates the new event.
The feature is tested on Gen2, Gen3 and Gen4 and all devices correctly
generate FRAME_SYNC events.
Niklas Söderlund (3):
media: rcar-vin: Fold interrupt helpers into only callers
media: rcar-vin: Check for correct capture interrupt event
media: rcar-vin: Generate FRAME_SYNC events
.../platform/renesas/rcar-vin/rcar-dma.c | 54 ++++++++++---------
.../platform/renesas/rcar-vin/rcar-v4l2.c | 2 +
2 files changed, 32 insertions(+), 24 deletions(-)
--
2.49.0
Powered by blists - more mailing lists