From: Sergey Lebedev <lsa.uz@pm.me>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Hans de Goede <hansg@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: i2c: ov13858: cap analogue gain at 15.5x
Date: Sun, 13 Sep 2026 20:48:07 +0000 [thread overview]
Message-ID: <20260913204759.85961-1-lsa.uz@pm.me> (raw)
In-Reply-To: <20260831180746.68878-1-lsa.uz@pm.me>
A ping, two weeks on:
https://lore.kernel.org/linux-media/20260831180746.68878-1-lsa.uz@pm.me/
It still applies to media/next at df9e111016, checked today, and nothing in
it has changed.
Two things around it have. An ipu-bridge entry for this sensor is now on the
list and has been tested on a second Surface Pro 11, so the OV13858 is about
to be reachable on Lunar Lake by more than one machine.
And that second machine exists. The measurements in the patch are from one
device, which I would rather say plainly than leave implied; if a
confirmation on hardware other than mine would help, I can ask for one.
One note that is worth more now than when I sent it. The gain table came from
raw Bayer at the ISYS capture node, not through libcamera, so the GPU debayer
fault that has turned up on this hardware in another thread this week cannot
reach it. The luma cross-check below the scissors did go through the software
ISP, but it compares before against after on the same path.
Sergey
prev parent reply other threads:[~2026-09-13 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 18:07 [PATCH] media: i2c: ov13858: cap analogue gain at 15.5x Sergey Lebedev
2026-09-13 20:48 ` Sergey Lebedev [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=20260913204759.85961-1-lsa.uz@pm.me \
--to=lsa.uz@pm.me \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.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