From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Tarang Raval <tarang.raval@siliconsignals.io>
Subject: Re: [PATCH v2 0/2] media: i2c: Add OmniVision OG0VE1B image sensor driver
Date: Tue, 2 Sep 2025 13:07:29 +0300 [thread overview]
Message-ID: <aLbB4SlFMUJkXLzY@kekkonen.localdomain> (raw)
In-Reply-To: <da59038d-edd6-4444-861f-adb65b040d0e@linaro.org>
Hi Vladimir,
On Tue, Sep 02, 2025 at 12:33:40PM +0300, Vladimir Zapolskiy wrote:
> Hi Sakari.
>
> On 8/29/25 17:42, Vladimir Zapolskiy wrote:
> > OmniVision OG0VE1B is a monochrome image sensor, which produces frames
> > in 8/10-bit raw output format and supports 640x480, 400x400, 200x200
> > and 100x100 output image resolution modes.
> >
> > At the moment the only supported resolution in the device driver is
> > 640x480@120fps (Y8).
> >
> > The driver version is based on top of media/master, which contains
> > a new devm_v4l2_sensor_clk_get() helper function.
>
> I'm not very well familiar with the linux-media processes, let me ask
> you about an expected interpretation of a "Superseded" patch status,
> which is assigned to this driver and another OV6211 one.
>
> Is there anything else expected to be done on my side?
>
> Thank you in advance.
I intended to mark the two latest series as "under review" but I'll have to
recheck (and of course Patchwork is down). These are nonetheless in my tree
now.
--
Kind regrds,
Sakari Ailus
prev parent reply other threads:[~2025-09-02 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 14:42 [PATCH v2 0/2] media: i2c: Add OmniVision OG0VE1B image sensor driver Vladimir Zapolskiy
2025-08-29 14:42 ` [PATCH v2 1/2] dt-bindings: media: i2c: Add OmniVision OG0VE1B camera sensor Vladimir Zapolskiy
2025-08-29 14:42 ` [PATCH v2 2/2] " Vladimir Zapolskiy
2025-08-29 16:19 ` [PATCH v2 0/2] media: i2c: Add OmniVision OG0VE1B image sensor driver Vladimir Zapolskiy
2025-09-02 9:33 ` Vladimir Zapolskiy
2025-09-02 10:07 ` Sakari Ailus [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=aLbB4SlFMUJkXLzY@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=tarang.raval@siliconsignals.io \
--cc=vladimir.zapolskiy@linaro.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