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>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH v2 0/2] media: ov13858: device tree support for the Surface Pro 11 (Snapdragon)
Date: Sun, 18 Oct 2026 22:10:20 +0100	[thread overview]
Message-ID: <20261018-ov13858-x1e-v2-0-cd35434cfcfe@gmail.com> (raw)

Hi Sakari,

The Surface Pro 11 with a Snapdragon X Elite (X1E80100) has an OV13858
rear camera on Qualcomm CAMSS over four D-PHY lanes. This two-patch
series adds the DT binding and the OF/endpoint support for the existing
sensor driver.

v2 keeps Sergey's power-management work as a prerequisite, updated to
his v4:
<20261016210246.58562-1-lsa.uz@pm.me>

On the Snapdragon model, the v4 runtime-PM callbacks are equivalent to
the v3 callbacks used for the hardware test. I ran 20 open/stream/close
cycles on the rear sensor; it runtime-suspended between every cycle and
streamed again each time. Three additional cycles saved complete
4224x3136 RAW10 frames. The camera rails were enabled while streaming
and disabled between sessions.

System suspend has not yet been tested on the Snapdragon model.
Suspend/resume support for this platform is currently being brought up
separately, and I plan to include the camera in that testing once it is
ready. This series therefore makes no suspend/resume claim.

Sergey tested the DT patches on the Intel Surface Pro 11: the endpoint
check passes, 4224x3136 streams at 29.95 fps, and v4l2-compliance passes
46/46 on the subdev. His Tested-by is carried on both patches.

Thanks to Sakari, Krzysztof and Bryan for the review and guidance.
Krzysztof's Reviewed-by is carried on the binding, and Sakari's latest
review feedback is folded into v2.

Changes in v2:
- update the prerequisite from Sergey's v3 to v4;
- carry Sergey's Tested-by on both patches;
- remove the fixed 19.2 MHz claim from the binding description;
- let v4l2_fwnode_endpoint_alloc_parse() handle missing-endpoint deferral;
- trim the driver commit message to the implementation change;
- document the Snapdragon runtime-PM cycle results.

Link to v1:
https://lore.kernel.org/r/20261015-ov13858-x1e-v1-0-acdd918f4fb6@gmail.com

Signed-off-by: George Neacsu <geocausa@gmail.com>
---
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                        |  54 ++++++++++
 3 files changed, 168 insertions(+)
---
base-commit: d7e7bca7169873b46e857c025c10f3336c1258d8
change-id: 20261015-ov13858-x1e-88fbdb884f82
prerequisite-patch-id: c4ab7c01d2ee19e6dd6c12f21e95e06527aec23e

Best regards,
-- 
George Neacsu <geocausa@gmail.com>



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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 21:10 George Neacsu via B4 Relay [this message]
2026-10-18 21:10 ` [PATCH v2 1/2] dt-bindings: media: i2c: Add OmniVision OV13858 George Neacsu via B4 Relay
2026-10-19  6:03   ` Krzysztof Kozlowski
2026-10-19  6:13     ` George Neacsu
2026-10-18 21:10 ` [PATCH v2 2/2] media: i2c: ov13858: Add device tree support George Neacsu via B4 Relay
2026-10-19  5:43 ` [PATCH v2 0/2] media: ov13858: device tree support for the Surface Pro 11 (Snapdragon) Sergey Lebedev
2026-10-19  6:01   ` 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=20261018-ov13858-x1e-v2-0-cd35434cfcfe@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=krzysztof.kozlowski@oss.qualcomm.com \
    --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®