[PATCH 0/2] media: ov13858: device tree support for the Surface Pro 11 (Snapdragon)

[George Neacsu via B4 Relay]

Hi Sakari,

The Surface Pro 11 with a Snapdragon X Elite (X1E80100) has the same
OV13858 as its rear camera as the Intel model does. There it is wired to
the Qualcomm CAMSS over four D-PHY lanes and described in the device tree.
These two patches add the binding and the OF match the driver needs for
that, and the endpoint checks that come with a DT user.

They apply on top of Sergey's "media: i2c: ov13858: add regulator, clock
and reset GPIO handling" v3. The Snapdragon machine needs it too: nothing
there powers the sensor for the driver either.
https://lore.kernel.org/all/20260831130312.26296-1-lsa.uz@xxxxx/

Tested on the Surface Pro 11 (X1E80100) with mainline ov13858.c, Sergey's
v3 and these two, through an out-of-tree CAMSS capturing raw frames over
CSIPHY1, CSID0 and an RDI interface. The in-tree register lists work
unchanged at 540 MHz:
- 4224x3136 at 29.95 fps;
- the colour-bar test pattern arrives intact;
- a scene captures;
- the binding validates with dt-doc-validate, and dt-validate accepts
  the example and rejects a two-lane endpoint.

Sergey, German: on the Intel machine the IPU bridge entry for OVTID858
already lists both link frequencies, so the new endpoint check should
pass there. A quick v4l2-compliance run would confirm it.

The device tree for the Surface Pro 11 cameras will follow once Bryan's
x1e80100 camera DT series has settled.

Thanks,
George

---
George Neacsu (2):
      dt-bindings: media: i2c: Add OmniVision OV13858
      media: i2c: ov13858: Add device tree support

 .../bindings/media/i2c/ovti,ov13858.yaml           | 113 +++++++++++++++++++++
 MAINTAINERS                                        |   1 +
 drivers/media/i2c/ov13858.c                        |  62 +++++++++++
 3 files changed, 176 insertions(+)
---
base-commit: ef7407f04f644833b0d1200a2e261c1879597b94
change-id: 20261015-ov13858-x1e-88fbdb884f82

Best regards,
-- 
George Neacsu <geocausa@xxxxxxxxx>