From: Conor Dooley <conor@kernel.org>
To: Robert Bozik <robertbozik@gmail.com>
Cc: linux-media@vger.kernel.org,
Sakari Ailus <sakari.ailus@linux.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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4
Date: Wed, 26 Aug 2026 17:13:27 +0100 [thread overview]
Message-ID: <20260826-copy-arise-bb7e9eb5e908@spud> (raw)
In-Reply-To: <20260826072002.14357-2-robertbozik@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4445 bytes --]
On Wed, Aug 26, 2026 at 09:20:00AM +0200, Robert Bozik wrote:
> Add a binding for the OmniVision OV32C4, a 32 megapixel RGBC CMOS image
> sensor with on-chip 4-cell fusion, a 4-lane MIPI CSI-2 D-PHY transmitter
> and the standard SCCB command interface.
>
> The sensor ships in laptops as an under-display camera, where it is
> described by ACPI; the binding follows ovti,ov08x40.yaml, which covers
> the closest relative already in tree.
>
> Signed-off-by: Robert Bozik <robertbozik@gmail.com>
> Assisted-by: Claude:claude-opus-5 sparse
> Assisted-by: Claude:claude-fable-5 sparse
> ---
> .../bindings/media/i2c/ovti,ov32c4.yaml | 109 ++++++++++++++++++
> 1 file changed, 109 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov32c4.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov32c4.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov32c4.yaml
> new file mode 100644
> index 000000000..be6067c75
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov32c4.yaml
> @@ -0,0 +1,109 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/ovti,ov32c4.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: OmniVision OV32C4 Image Sensor
> +
> +maintainers:
> + - Robert Bozik <robertbozik@gmail.com>
> +
> +description:
> + The OmniVision OV32C4 is a 32 megapixel RGBC (red, green, blue and clear)
> + CMOS image sensor in a 4-cell arrangement, with on-chip 4-cell fusion and
> + binning. It has a 6528x4896 active pixel array, a 4-lane MIPI CSI-2 D-PHY
> + transmitter and the standard SCCB command interface. The driver supports
> + 3264x1840 at 30 fps, 10-bit Bayer, at a link frequency of 400 MHz.
> +
> +allOf:
> + - $ref: /schemas/media/video-interface-devices.yaml#
> +
> +properties:
> + compatible:
> + const: ovti,ov32c4
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> + description: Input clock (XVCLK), 19.2 MHz.
Where do this name and frequency come from? pin name I presume for the
former? Is 19.2 MHz a mandatory frequency?
> +
> + avdd-supply:
> + description: Analogue circuit voltage supply.
> +
> + dovdd-supply:
> + description: I/O circuit voltage supply.
> +
> + dvdd-supply:
> + description: Digital core voltage supply.
These 3 can just be :true, what they do should be obvious, provided they
match the pin names of the device.
Generally this looks fine to me though..
Cheers,
Conor.
> +
> + reset-gpios:
> + maxItems: 1
> + description: Active low GPIO connected to the XSHUTDOWN pad of the sensor.
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + additionalProperties: false
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + additionalProperties: false
> +
> + properties:
> + data-lanes:
> + items:
> + - const: 1
> + - const: 2
> + - const: 3
> + - const: 4
> + link-frequencies: true
> + remote-endpoint: true
> +
> + 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>;
> +
> + camera@36 {
> + compatible = "ovti,ov32c4";
> + reg = <0x36>;
> +
> + clocks = <&ov32c4_clk>;
> + assigned-clocks = <&ov32c4_clk>;
> + assigned-clock-rates = <19200000>;
> +
> + avdd-supply = <&vreg_2p8>;
> + dovdd-supply = <&vreg_1p8>;
> + dvdd-supply = <&vreg_1p1>;
> +
> + reset-gpios = <&tlmm 111 GPIO_ACTIVE_LOW>;
> +
> + port {
> + ov32c4_ep: endpoint {
> + remote-endpoint = <&csiphy0_ep>;
> + data-lanes = <1 2 3 4>;
> + link-frequencies = /bits/ 64 <400000000>;
> + };
> + };
> + };
> + };
> +...
> --
> 2.53.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-26 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 7:19 [PATCH 0/3] media: Add OmniVision OV32C4 sensor driver Robert Bozik
2026-08-26 7:20 ` [PATCH 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4 Robert Bozik
2026-08-26 16:13 ` Conor Dooley [this message]
[not found] ` <CALSBEvTvrhniBrM29Y7sery15W-onz7t_8ZQhg1TW8nBDgYKxg@mail.gmail.com>
2026-08-26 22:47 ` Conor Dooley
2026-08-26 7:20 ` [PATCH 2/3] media: i2c: Add driver for " Robert Bozik
2026-08-26 7:31 ` sashiko-bot
2026-08-26 7:20 ` [PATCH 3/3] media: ipu-bridge: Add " Robert Bozik
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=20260826-copy-arise-bb7e9eb5e908@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robertbozik@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.