From: Afonso Figuinha <afonso.figuinha@gmail.com>
To: Tin Posavec <tin.posavec04@gmail.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@amd.com>,
Dan Scally <dan.scally@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] media: ov9734, ipu-bridge: Enable the camera on the Intel NUC M15
Date: Fri, 6 Nov 2026 21:33:19 +0000 [thread overview]
Message-ID: <20261106213319.104745-1-afonso.figuinha@gmail.com> (raw)
In-Reply-To: <20261017-ov9734-ipu6-v1-0-86eab22ae258@gmail.com>
Hi Tin,
I tested this series on a Microsoft Surface Laptop 1, which has the
same OV9734 behind an IPU3 CIO2. There an INT3472 discrete device
provides the clock enable and the reset GPIO, and the _PR0 power
resource of the sensor does nothing.
I used 6.19.8-surface-3 with patches 1 and 2 applied (they apply with
one-line offsets). Patch 3 does not apply there because the sensor list
differs, so I added the same entry by hand.
- the sensor probes and the chip ID reads back;
- libcamera master with the OV9734 fixes from series 6330 [1] (IPU3
pipeline) streams 1280x704 NV12 at 30 fps;
- the sensor is runtime suspended when idle;
- unloading and reloading the module gives no kernel warnings;
- v4l2-compliance 1.32.0 on the subdev: 45/46, only the known
SUBSCRIBE_EVENT failure.
Not tested: probe deferral at boot with these exact patches, and
system suspend.
Tested-by: Afonso Figuinha <afonso.figuinha@gmail.com> # Surface Laptop 1 (IPU3)
I posted a duplicate series by mistake before I saw yours, and I have
withdrawn it. Its patch 4 sets V4L2_SUBDEV_FL_HAS_EVENTS and uses the
control event helpers, which fixes the SUBSCRIBE_EVENT failure. I can
send it on top of your series, or you can fold it in, as you prefer.
[1] https://patchwork.libcamera.org/project/libcamera/list/?series=6330
Thanks,
Afonso
prev parent reply other threads:[~2026-11-06 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 8:31 Tin Posavec via B4 Relay
2026-10-17 8:31 ` [PATCH 1/3] media: i2c: ov9734: Return -EPROBE_DEFER if no endpoint is found Tin Posavec via B4 Relay
2026-10-17 8:31 ` [PATCH 2/3] media: i2c: ov9734: Add power on/off sequencing support Tin Posavec via B4 Relay
2026-10-17 8:31 ` [PATCH 3/3] media: ipu-bridge: Add OV9734 sensor config Tin Posavec via B4 Relay
2026-11-06 21:33 ` Afonso Figuinha [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=20261106213319.104745-1-afonso.figuinha@gmail.com \
--to=afonso.figuinha@gmail.com \
--cc=bingbu.cao@amd.com \
--cc=dan.scally@ideasonboard.com \
--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 \
--cc=tin.posavec04@gmail.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®