From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Scally <dan.scally@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
jacopo.mondi@ideasonboard.com, biju.das.jz@bp.renesas.com
Subject: Re: [PATCH v2 0/3] Add Input Video Control Block driver for RZ/V2H
Date: Tue, 24 Jun 2025 14:52:18 +0200 [thread overview]
Message-ID: <145fbca0-bb55-4809-9c13-cbfa50e5b1ec@kernel.org> (raw)
In-Reply-To: <20250624-ivc-v2-0-e4ecdddb0a96@ideasonboard.com>
On 24/06/2025 14:35, Daniel Scally wrote:
> Hello all
>
> This series adds a driver for the Input Video Control Block in the
> RZ/V2H SoC. The IVC block transmits input image data from memory to
> the ISP core (on this SoC, a Mali-C55 ISP). The driver registers an
> output video device for userspace to queue image buffers to. One
> noteworthy feature is that - because it is not a part of the main ISP
> drive - the IVC driver also registers a subdevice, which connects to
> the media device created by the ISP driver through the usual v4l2
> async framework. This requires delaying the registration of the video
> device until the .registered() callback of the subdevice, so that the
> struct v4l2_dev pointer the subdevice connected to can be set to the
> video device.
>
> To facilitate communication between the ISP driver and the IVC driver
> we use the new media jobs framework that was posted recently [1]. The
> series is also based on top of the latest version of the Mali-C55
> driver [2] and some updates to rzg2l-cru [3].
>
> Note that this is not quite ready to merge, as there's an outstanding
> bug that sometimes causes the driver to hang. The device should fire
> two interrupts per frame; once on completion of data transmission and
> once on expiration of the blanking period. The second interrupt seems
> sometimes not to arrive, and at the moment the problem is worked
> around with a timeout in rzv2h_ivc_send_next_buffer(). We're working
> on that issue, but because the driver lends helpful context to the
> media jobs and mali-c55 series (and is probably otherwise ready for
> comment too) I wanted to post it.
>
> Thanks
> Dan
>
> [1] https://lore.kernel.org/linux-media/20250624-media-jobs-v2-0-8e649b069a96@ideasonboard.com/T/#t
> [2] https://lore.kernel.org/linux-media/20250624-c55-v10-0-54f3d4196990@ideasonboard.com/T/#t
> [3] https://lore.kernel.org/linux-media/20250623-rzg2l-cru-v5-0-1663a8c6719a@ideasonboard.com/T/#t
>
> ---
> Daniel Scally (3):
> dt-bindings: media: Add bindings for the RZ/V2H IVC block
> media: platform: Add Renesas Input Video Control block driver
> MAINTAINERS: Add entry for rzv2h-ivc driver
>
> .../bindings/media/renesas,rzv2h-ivc.yaml | 103 ++++
> MAINTAINERS | 7 +
> drivers/media/platform/renesas/Kconfig | 2 +
> drivers/media/platform/renesas/Makefile | 1 +
> drivers/media/platform/renesas/rzv2h-ivc/Kconfig | 15 +
> drivers/media/platform/renesas/rzv2h-ivc/Makefile | 5 +
> .../platform/renesas/rzv2h-ivc/rzv2h-ivc-dev.c | 237 +++++++
> .../platform/renesas/rzv2h-ivc/rzv2h-ivc-subdev.c | 379 ++++++++++++
> .../platform/renesas/rzv2h-ivc/rzv2h-ivc-video.c | 678 +++++++++++++++++++++
> .../media/platform/renesas/rzv2h-ivc/rzv2h-ivc.h | 133 ++++
> 10 files changed, 1560 insertions(+)
> ---
> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
> change-id: 20250624-ivc-833d24376167
That's b4, right? So where is the changelog with lore link to previous
version?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-24 12:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 12:35 [PATCH v2 0/3] Add Input Video Control Block driver for RZ/V2H Daniel Scally
2025-06-24 12:35 ` [PATCH v2 1/3] dt-bindings: media: Add bindings for the RZ/V2H IVC block Daniel Scally
2025-06-24 13:16 ` Krzysztof Kozlowski
2025-06-24 14:17 ` Dan Scally
2025-06-24 15:41 ` Krzysztof Kozlowski
2025-06-24 16:45 ` Geert Uytterhoeven
2025-06-24 17:50 ` Dan Scally
2025-06-24 12:35 ` [PATCH v2 2/3] media: platform: Add Renesas Input Video Control block driver Daniel Scally
2025-06-30 16:05 ` Jacopo Mondi
2025-06-30 21:32 ` Dan Scally
2025-07-01 11:10 ` Jacopo Mondi
2025-07-01 11:27 ` Dan Scally
2025-07-01 12:58 ` Jacopo Mondi
2025-07-01 13:01 ` Dan Scally
2025-07-01 13:17 ` Jacopo Mondi
2025-07-01 13:21 ` Dan Scally
2025-07-01 13:31 ` Jacopo Mondi
2025-07-01 13:33 ` Dan Scally
2025-07-01 8:34 ` Philipp Zabel
2025-07-01 13:24 ` Dan Scally
2025-06-24 12:36 ` [PATCH v2 3/3] MAINTAINERS: Add entry for rzv2h-ivc driver Daniel Scally
2025-06-24 12:52 ` Krzysztof Kozlowski [this message]
2025-06-24 13:10 ` [PATCH v2 0/3] Add Input Video Control Block driver for RZ/V2H Dan Scally
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=145fbca0-bb55-4809-9c13-cbfa50e5b1ec@kernel.org \
--to=krzk@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox