Re: [BUG] platform/x86: int3472/discrete: unknown GPIO type 0x08 breaks OV13858 rear camera on Surface Pro 11/12 Business (INT3472:00 / OVTID858)

[Sergey Lebedev <lsa.uz@pm.me>]

Andy, this answers your question of 3 September in this thread - "I can't see
that commit in many trees from kernel.org nor in media.git" - in case it is
still open. I am writing from a machine that has the same problem, not on
anyone's behalf. My reply may arrive unthreaded, which is why the question is
quoted rather than assumed.

The commit is 34e31390a3b939db2e0cbfef4c40d95052572df0, "platform/x86: int3472:
support the POWER1 GPIO type", by Jakob Berg Jespersen. Authored 29 August,
committed 2 September at 08:05 UTC - about 33 hours before you looked, which
may be the whole of it.

Checked today, 11 September:

  git.linuxtv.org/media.git, branch next        present
  git.kernel.org .../next/linux-next.git        present
  git.kernel.org .../torvalds/linux.git         absent

So the answer to what you actually asked is yes: it is in linux-next now, and
it is not yet in mainline.

(One trap I walked into on the way: api.github.com will hand you that commit
from repos/torvalds/linux in full, because the object is reachable through the
fork network. kernel.org's cgit 404s on it correctly.)

For German's original report: this commit is necessary but not sufficient. With
it, INT3472:00-dvdd becomes a real regulator instead of an unknown-type
warning. The rear sensor still fails to probe afterwards, because the in-tree
ov13858 driver requests no supplies, takes no reset GPIO and enables no clock -
it acquires one and never turns it on. That part is a separate patch, sent to
linux-media on 31 August and still unreviewed:

  https://lore.kernel.org/linux-media/20260831130312.26296-1-lsa.uz@pm.me/

Sergey