From: Sergey Lebedev <lsa.uz@pm.me>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans de Goede <hansg@kernel.org>
Cc: Daniel Scally <dan.scally@ideasonboard.com>,
Jakob Berg Jespersen <dev@berg.pm>,
linux-media@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] media: i2c: ov13858: add regulator, clock and reset GPIO handling
Date: Wed, 09 Sep 2026 18:03:06 +0000 [thread overview]
Message-ID: <20260909180259.81079-1-lsa.uz@pm.me> (raw)
In-Reply-To: <20260831130312.26296-1-lsa.uz@pm.me>
New evidence for this patch, from media/next rather than from a distro kernel.
I built and booted a kernel from media/next f9536a8065 on the Surface Pro 11
today - for an unrelated series - and the back camera does not come up on it:
ov13858 i2c-OVTID858:00: failed to find sensor: -5
ov13858 i2c-OVTID858:00: probe with driver ov13858 failed with error -5
That is the mechanism Hans named on 2026-08-31 - "the ov13858 problem is not a
problem with the INT3472 driver, but rather with the ov13858 driver" - now
visible on current upstream. Reading f9536a8065: ov13858.c contains no
regulator, no supply and no gpiod reference at all, and while probe does
acquire a clock through devm_v4l2_sensor_clk_get() it never enables it. So
nothing asks INT3472 to power the sensor, and the chip-ID read talks to a part
that is still off.
https://lore.kernel.org/all/df2f3cb1-1bab-432f-a359-59e6bec9580a@kernel.org/
With this patch applied the same machine enumerates the camera and streams from
it; that has been true since 2026-08-31 and is what the original posting
reported. What is new is only that the failure is now demonstrated on the tree
this patch is aimed at, rather than argued from a 7.0.0 kernel.
Both ov13858 patches still apply to f9536a8065 unchanged - checked, not assumed
- so there is nothing to resend and I am not asking for anything here. Recording
it because the next person to read this thread should not have to take the
"camera still dead" claim on trust.
Sergey
next prev parent reply other threads:[~2026-09-09 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 13:03 Sergey Lebedev
2026-09-09 18:03 ` Sergey Lebedev [this message]
2026-09-23 12:47 ` Sergey Lebedev
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=20260909180259.81079-1-lsa.uz@pm.me \
--to=lsa.uz@pm.me \
--cc=dan.scally@ideasonboard.com \
--cc=dev@berg.pm \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=platform-driver-x86@vger.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
all inboxes | Powered by JetHome®