mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Robert Bozik <robertbozik@gmail.com>,
	linux-media@vger.kernel.org,
	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,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4
Date: Mon, 5 Oct 2026 12:02:32 +0100	[thread overview]
Message-ID: <asODx3YQa4WlANen@squawk> (raw)
In-Reply-To: <asNbwhGCuxF6e6Ba@kekkonen.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

On Mon, Oct 05, 2026 at 11:11:46AM +0300, Sakari Ailus wrote:
> Hi Robert,
> 
> On Mon, Oct 05, 2026 at 09:10:08AM +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.
> > 
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > Signed-off-by: Robert Bozik <robertbozik@gmail.com>
> > ---
> > Changes in v4:
> > - No changes to the binding.
> > 
> >  .../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
> 
> minItems should be 2 here, for the always-on client.

Instead, make it an items list, so that what each item is is explained.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2026-10-05 11:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05  7:10 [PATCH v4 0/3] media: Add OmniVision OV32C4 sensor driver Robert Bozik
2026-10-05  7:10 ` [PATCH v4 1/3] dt-bindings: media: i2c: Add OmniVision OV32C4 Robert Bozik
2026-10-05  8:11   ` Sakari Ailus
2026-10-05  8:36     ` Robert Bozik
2026-10-05 11:02     ` Conor Dooley [this message]
2026-10-05 12:01       ` Robert Bozik
2026-10-05  7:10 ` [PATCH v4 2/3] media: i2c: Add driver for " Robert Bozik
2026-10-05  9:23   ` Sakari Ailus
2026-10-05 10:14     ` Robert Bozik
2026-10-05 10:36       ` Sakari Ailus
2026-10-05 10:46         ` Robert Bozik
2026-10-05  7:10 ` [PATCH v4 3/3] media: ipu-bridge: Add " Robert Bozik
2026-10-05  8:04 ` [PATCH v4 0/3] media: Add OmniVision OV32C4 sensor driver 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=asODx3YQa4WlANen@squawk \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --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 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®