From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: geocausa@gmail.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
Subject: Re: [PATCH 1/2] dt-bindings: media: i2c: Add OmniVision OV13858
Date: Sun, 18 Oct 2026 23:24:40 +0300 [thread overview]
Message-ID: <atUrCG-efqA_x2bM@kekkonen.localdomain> (raw)
In-Reply-To: <20261015-ov13858-x1e-v1-1-acdd918f4fb6@gmail.com>
Hi George,
On Thu, Oct 15, 2026 at 10:48:19PM +0100, George Neacsu via B4 Relay wrote:
> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov13858.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov13858.yaml
> new file mode 100644
> index 0000000..a1cbdb1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov13858.yaml
> @@ -0,0 +1,113 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/ovti,ov13858.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: OmniVision OV13858 CMOS Sensor
> +
> +maintainers:
> + - George Neacsu <geocausa@gmail.com>
> +
> +description:
> + The OmniVision OV13858 is a 13 megapixel CMOS image sensor with an I2C
> + control interface. It outputs 10-bit Bayer data over a four-lane MIPI
> + CSI-2 D-PHY interface and takes a 19.2 MHz input clock.
I wouldn't mention the input clock frequency here...
> +
> +allOf:
> + - $ref: /schemas/media/video-interface-devices.yaml#
> +
> +properties:
> + compatible:
> + const: ovti,ov13858
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + description: Input clock (19.2 MHz)
...because it's also documented here.
The frequency range is from 6 to 27 MHz.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-10-18 20:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 21:48 [PATCH 0/2] media: ov13858: device tree support for the Surface Pro 11 (Snapdragon) George Neacsu via B4 Relay
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 [this message]
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=atUrCG-efqA_x2bM@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--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 \
/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