From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "Su, Jimmy" <jimmy.su@intel.com>
Cc: "Zhang, Qingwu" <qingwu.zhang@intel.com>,
Pierre Pinon <pierre@pinon1.fr>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans de Goede <hansg@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Vadillo, Miguel" <miguel.vadillo@intel.com>,
"Yeh, Serin" <serin.yeh@intel.com>
Subject: Re: [PATCH 2/2] media: i2c: ov08x40: Do not expose the broken 1928x1088 binned mode
Date: Thu, 10 Sep 2026 10:06:51 +0300 [thread overview]
Message-ID: <aqJXC9SbhJCz2KFJ@kekkonen.localdomain> (raw)
In-Reply-To: <DM4SPRMB0091FCB6C62990275CABC68F9DBF2@DM4SPRMB0091.namprd11.prod.outlook.com>
Hi Jimmy,
On Thu, Sep 10, 2026 at 06:28:59AM +0000, Su, Jimmy wrote:
> Hi Sakari,
> As I know, one of Chrome MTL project is using ov08x40 sensor.
> It supports "3856x2416@4 lanes linear mode" & "1928x1208@ 4 lanes linear mode".
>
> Then Linux projects support 3856x2176@ 4 lanes & 2 lanes linear mode.
> BTW, Some Linux projects have CV solution.
> From one CV vendor's feedback, 1928x1088 resolution only supports sHDR mode.
But this CVS device still works in non-binned mode. Are the exact
limitations known? Is this CVS device used in other systems?
Staggered HDR isn't supported in upstream in any case.
> But our sensor driver only supports 1928x1088@linear mode.
> It could have unexpected issue while this device has CVS board.
One way to address this would be to set the minimum image size to some
larger, known to work size, for that CVS device in the CVS driver. This may
require changes on libcamera side, too, but that's a separate issue.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2026-09-10 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 13:46 Pierre Pinon
2026-09-08 9:41 ` Sakari Ailus
2026-09-09 10:32 ` Zhang, Qingwu
2026-09-10 6:28 ` Su, Jimmy
2026-09-10 7:06 ` Sakari Ailus [this message]
[not found] ` <DM4SPRMB009141D91C6DCF0987A28C5A9DBF2@DM4SPRMB0091.namprd11.prod.outlook.com>
2026-09-10 7:52 ` Sakari Ailus
2026-09-12 10:16 ` Sakari Ailus
2026-10-02 6:26 ` Pierre PINON
2026-10-17 13:29 ` Edvinas Šulcas
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=aqJXC9SbhJCz2KFJ@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=hansg@kernel.org \
--cc=jimmy.su@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=miguel.vadillo@intel.com \
--cc=pierre@pinon1.fr \
--cc=qingwu.zhang@intel.com \
--cc=serin.yeh@intel.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
all inboxes | Powered by JetHome®