Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: German <germanpapulindez@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	linux-media@vger.kernel.org
Subject: Re: [BUG] platform/x86: int3472/discrete: unknown GPIO type 0x08 breaks OV13858 rear camera on Surface Pro 11/12 Business (INT3472:00 / OVTID858)
Date: Thu, 3 Sep 2026 11:25:55 +0300	[thread overview]
Message-ID: <apkvE9kbfEWHrAte@kekkonen.localdomain> (raw)
In-Reply-To: <20260903081557.16603-1-germanpapulindez@gmail.com>

Hi German,

On Thu, Sep 03, 2026 at 10:15:56AM +0200, German wrote:
> Hi,
> 
> On the Microsoft Surface Pro 11/12 Business (Intel Lunar Lake, IPU7),
> the rear camera sensor (ov13858, ACPI HID OVTID858) fails to probe.
> I've traced the root cause to int3472-discrete not recognizing one of
> the GPIO types described in the device's ACPI _DSM data, which leaves
> a power/reset-related GPIO unconfigured and the sensor unable to
> respond over I2C.
> 
> System
> ------
> - Surface Pro for Business 11th Edition with Intel (Intel Lunar Lake, IPU7)
> - Kernel: 7.2.2 (Arch Linux, vanilla)

It's usually best to test with linux-next, not with distro kernels, or in
this case, the media committers tree
<URL:https://gitlab.freedesktop.org/linux-media/media-committers> next
branch.

> - CONFIG_VIDEO_OV13858=m
> 
> Evidence
> --------
> 
>   $ dmesg | grep -iE "int3472|OVTID858"
>   [    5.555231] int3472-discrete INT3472:00: GPIO type 0x08 unknown; the sensor may not work
>   [    5.788882] ov13858 i2c-OVTID858:00: failed to find sensor: -5
>   [    5.789321] ov13858 i2c-OVTID858:00: probe with driver ov13858 failed with error -5
> 
> The "GPIO type 0x08 unknown" warning comes from the default case in
> skl_int3472_handle_gpio_resources() in drivers/platform/x86/intel/
> int3472/discrete.c:
> 
>     default:
>         dev_warn(int3472->dev,
>                  "GPIO type 0x%02x unknown; the sensor may not work\n",
>                  type);
>         ret = 1;
>         break;

This should be addressed by commit 34e31390a3b939db2e0cbfef4c40d95052572df0
.

-- 
Regards,

Sakari Ailus

  reply	other threads:[~2026-09-03  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  8:15 [BUG] platform/x86: int3472/discrete: unknown GPIO type 0x08 breaks OV13858 rear camera on Surface Pro 11/12 Business (INT3472:00 / OVTID858) German
2026-09-03  8:25 ` Sakari Ailus [this message]
2026-09-03 14:00   ` Andy Shevchenko

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=apkvE9kbfEWHrAte@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=germanpapulindez@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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