From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v3 00/10] media: ov5645: Add support for streams
Date: Tue, 5 Nov 2024 11:18:32 +0000 [thread overview]
Message-ID: <Zyn_CHKpENoIoDVs@kekkonen.localdomain> (raw)
In-Reply-To: <20241018153230.235647-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
Hi Prabhakar,
On Fri, Oct 18, 2024 at 04:32:20PM +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Hi All,
>
> This patch series aims to add the below features,
> - Support subdev active state
> - Support for streams
> - Support for virtual channel
> - Code cleanup
Thanks for these!
I've taken patches 2--8, 1st is redundant with recent framework improvement
and the last two need the metadata patches (and agreeing on the sensor
interface). I've marked the two last as "changes requested", please repost
once we have the new API agreed on.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2024-11-05 11:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:32 [PATCH v3 00/10] media: ov5645: Add support for streams Prabhakar
2024-10-18 15:32 ` [PATCH v3 01/10] media: i2c: ov5645: Add V4L2_SUBDEV_FL_HAS_EVENTS and subscribe hooks Prabhakar
2024-10-18 15:32 ` [PATCH v3 02/10] media: i2c: ov5645: Use local `dev` pointer for subdev device assignment Prabhakar
2024-10-21 7:16 ` Tommaso Merciai
2024-10-18 15:32 ` [PATCH v3 03/10] media: i2c: ov5645: Replace dev_err with dev_err_probe in probe function Prabhakar
2024-10-20 22:33 ` Laurent Pinchart
2024-10-18 15:32 ` [PATCH v3 04/10] media: i2c: ov5645: Use v4l2_async_register_subdev_sensor() Prabhakar
2024-10-18 15:32 ` [PATCH v3 05/10] media: i2c: ov5645: Drop `power_lock` mutex Prabhakar
2024-10-18 15:32 ` [PATCH v3 06/10] media: i2c: ov5645: Use subdev active state Prabhakar
2024-10-18 15:32 ` [PATCH v3 07/10] media: i2c: ov5645: Switch to {enable,disable}_streams Prabhakar
2024-10-18 15:32 ` [PATCH v3 08/10] media: i2c: ov5645: Report streams using frame descriptors Prabhakar
2024-11-05 12:07 ` Sakari Ailus
2024-10-18 15:32 ` [PATCH v3 09/10] media: i2c: ov5645: Add internal image sink pad Prabhakar
2024-10-18 15:32 ` [PATCH v3 10/10] media: i2c: ov5645: Report internal routes to userspace Prabhakar
2024-10-20 22:39 ` [PATCH v3 00/10] media: ov5645: Add support for streams Laurent Pinchart
2024-10-21 8:06 ` Lad, Prabhakar
2024-11-04 23:32 ` Lad, Prabhakar
2024-10-21 8:10 ` Tommaso Merciai
2024-10-21 9:22 ` Lad, Prabhakar
2024-11-05 11:18 ` Sakari Ailus [this message]
2024-11-05 11:23 ` Lad, Prabhakar
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=Zyn_CHKpENoIoDVs@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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