From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Antoine Bernard <zalnir@proton.me>
Cc: Arec Kao <arec.kao@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"~postmarketos/upstreaming@lists.sr.ht"
<~postmarketos/upstreaming@lists.sr.ht>
Subject: Re: [PATCH 2/3] media: dt-bindings: Add OmniVision OV13B10
Date: Fri, 20 Mar 2026 23:39:27 +0200 [thread overview]
Message-ID: <ab2-j6tMKTAlCDcT@kekkonen.localdomain> (raw)
In-Reply-To: <cTZxBKdzN37cy_eGcCK3hocAgzwzdfBnsqWXpJnNYFZb6Odl4FspR5333ZBJIJG5dRunnVBB3fWiRJL_pq3SmykhDKxaGPRl_T5_BShJIng=@proton.me>
Hi Antoine,
On Fri, Mar 20, 2026 at 09:27:18AM +0000, Antoine Bernard wrote:
> From: Antoine Bernard <zalnir@proton.me>
>
> Document the device tree bindings for OmniVision OV13B10 image
> sensor.
>
> Signed-off-by: Antoine Bernard <zalnir@proton.me>
> ---
> .../bindings/media/i2c/ovti,ov13b10.yaml | 99 +++++++++++++++++++
> 1 file changed, 99 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov13b10.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov13b10.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov13b10.yaml
> new file mode 100644
> index 000000000000..4d6432488b79
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov13b10.yaml
> @@ -0,0 +1,99 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/ovti,ov13b10.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Omnivision ov13b10 image sensor
> +
> +maintainers:
> + - Arec Kao <arec.kao@intel.com>
> +
> +allOf:
> + - $ref: /schemas/media/video-interface-devices.yaml#
> +
> +properties:
> + compatible:
> + const: ovti,ov13b10
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + description: System clock.
Typically this is called "external clock" or something like that.
> + maxItems: 1
> +
> + reset-gpios:
> + description: GPIO connected to the XSHUTDOWN pin. Active low.
> + maxItems: 1
> +
> + avdd-supply:
> + description: Analog circuit voltage supply.
> +
> + dvdd-supply:
> + description: Digital circuit voltage supply.
> +
> + dovdd-supply:
> + description: Digital I/O circuit voltage supply.
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + additionalProperties: false
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + additionalProperties: false
> +
> + properties:
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> + items:
> + enum: [1, 2, 3, 4]
> +
> + link-frequencies: true
> + remote-endpoint: true
These two you can drop I believe.
> +
> + required:
> + - data-lanes
> + - link-frequencies
> + - remote-endpoint
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - port
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ov13b10: camera@36 {
> + compatible = "ovti,ov13b10";
> + reg = <0x36>;
> +
> + clocks = <&sensor_xclk>;
> + reset-gpios = <&gpio 117 GPIO_ACTIVE_LOW>;
> +
> + avdd-supply = <&ov13b10_avdd>;
> + dvdd-supply = <&ov13b10_dvdd>;
> + dovdd-supply = <&ov13b10_dovdd>;
> +
> + port {
> + ov13b10_ep: endpoint {
> + data-lanes = <1 2 3 4>;
> + link-frequencies = /bits/ 64 <560000000>;
> + remote-endpoint = <&csiphy_ep>;
> + };
> + };
> + };
> + };
> +...
--
Kind regrads,
Sakari Ailus
next parent reply other threads:[~2026-03-20 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cTZxBKdzN37cy_eGcCK3hocAgzwzdfBnsqWXpJnNYFZb6Odl4FspR5333ZBJIJG5dRunnVBB3fWiRJL_pq3SmykhDKxaGPRl_T5_BShJIng=@proton.me>
2026-03-20 21:39 ` Sakari Ailus [this message]
2026-03-21 4:36 ` [PATCH v2 2/3] media: dt-bindings: Add OmniVision OV13B10 Antoine Bernard
2026-03-21 10:25 ` Krzysztof Kozlowski
2026-03-21 11:52 ` Antoine Bernard
2026-03-21 11:57 ` Krzysztof Kozlowski
2026-03-21 12:02 ` Antoine Bernard
2026-03-21 12:54 ` Krzysztof Kozlowski
2026-03-20 21:40 ` [PATCH " Sakari Ailus
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=ab2-j6tMKTAlCDcT@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=arec.kao@intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=zalnir@proton.me \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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