From: Robert Bozik <robertbozik@gmail.com>
To: linux-media@vger.kernel.org
Cc: sakari.ailus@linux.intel.com, mchehab@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Robert Bozik <robertbozik@gmail.com>
Subject: [PATCH v2 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4
Date: Fri, 28 Aug 2026 15:21:02 +0200 [thread overview]
Message-ID: <20260828132104.21473-2-robertbozik@gmail.com> (raw)
In-Reply-To: <20260828132104.21473-1-robertbozik@gmail.com>
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.
Assisted-by: Claude:claude-opus-5 sparse
Assisted-by: Claude:claude-fable-5 sparse
Signed-off-by: Robert Bozik <robertbozik@gmail.com>
---
Changes in v2:
- Drop the frequency from the xvclk description. 19.2 MHz is what this
platform provides and what the driver's register tables assume, not a
requirement of the sensor; the example keeps it in
assigned-clock-rates (Conor Dooley).
- avdd-supply, dovdd-supply and dvdd-supply are now plain "true"; the
names already say which rail is which (Conor Dooley).
- Drop the sentence listing the modes the driver supports. The binding
describes the hardware.
- Signed-off-by placed last in the trailer block (Krzysztof Kozlowski).
.../bindings/media/i2c/ovti,ov32c4.yaml | 105 ++++++++++++++++++
1 file changed, 105 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..804307cd0
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov32c4.yaml
@@ -0,0 +1,105 @@
+# 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.
+
+allOf:
+ - $ref: /schemas/media/video-interface-devices.yaml#
+
+properties:
+ compatible:
+ const: ovti,ov32c4
+
+ reg:
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+ description: Input clock (XVCLK).
+
+ avdd-supply: true
+
+ dovdd-supply: true
+
+ dvdd-supply: true
+
+ 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
next prev parent reply other threads:[~2026-08-28 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 13:21 [PATCH v2 0/3] media: Add OmniVision OV32C4 sensor driver Robert Bozik
2026-08-28 13:21 ` Robert Bozik [this message]
2026-08-28 16:23 ` [PATCH v2 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4 Conor Dooley
2026-08-28 13:21 ` [PATCH v2 2/3] media: i2c: Add driver for " Robert Bozik
[not found] ` <20260828133537.C61EC1F00A3A@smtp.kernel.org>
2026-08-28 13:59 ` Robert Bozik
2026-08-28 13:21 ` [PATCH v2 3/3] media: ipu-bridge: Add " Robert Bozik
2026-08-28 15:23 ` Sakari Ailus
2026-08-28 15:34 ` 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=20260828132104.21473-2-robertbozik@gmail.com \
--to=robertbozik@gmail.com \
--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=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®