mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: George Neacsu via B4 Relay <devnull+geocausa.gmail.com@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	 Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Sergey Lebedev <lsa.uz@pm.me>,
	 German Pablo Lindo <germanpapulindez@gmail.com>,
	 Bryan O'Donoghue <bod@kernel.org>,
	linux-media@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,  linux-kernel@vger.kernel.org,
	George Neacsu <geocausa@gmail.com>
Subject: [PATCH 0/2] media: ov13858: device tree support for the Surface Pro 11 (Snapdragon)
Date: Thu, 15 Oct 2026 22:48:18 +0100	[thread overview]
Message-ID: <20261015-ov13858-x1e-v1-0-acdd918f4fb6@gmail.com> (raw)

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@pm.me/

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@gmail.com>



             reply	other threads:[~2026-10-15 21:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 21:48 George Neacsu via B4 Relay [this message]
2026-10-15 21:48 ` [PATCH 1/2] dt-bindings: media: i2c: Add OmniVision OV13858 George Neacsu via B4 Relay
2026-10-16 20:49   ` Bryan O'Donoghue
2026-10-17 16:57     ` Krzysztof Kozlowski
2026-10-17 21:28       ` Bryan O'Donoghue
2026-10-17 16:58   ` Krzysztof Kozlowski
2026-10-18 20:24   ` Sakari Ailus
2026-10-15 21:48 ` [PATCH 2/2] media: i2c: ov13858: Add device tree support George Neacsu via B4 Relay
2026-10-16 16:06   ` Bryan O'Donoghue
2026-10-16 16:16     ` George Neacsu
2026-10-16 20:43       ` Bryan O'Donoghue
2026-10-16 21:08         ` Sergey Lebedev
2026-10-16 21:48           ` George Neacsu
2026-10-16 22:25           ` George Neacsu
2026-10-18 20:35   ` Sakari Ailus
2026-10-16  7:01 ` [PATCH 0/2] media: ov13858: device tree support for the Surface Pro 11 (Snapdragon) Sergey Lebedev
2026-10-16 14:55   ` George Neacsu

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=20261015-ov13858-x1e-v1-0-acdd918f4fb6@gmail.com \
    --to=devnull+geocausa.gmail.com@kernel.org \
    --cc=bod@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geocausa@gmail.com \
    --cc=germanpapulindez@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lsa.uz@pm.me \
    --cc=mchehab@kernel.org \
    --cc=robh@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®