From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Philippe Baetens <philippebaetens@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Jai Luthra <jai.luthra@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: media: i2c: Add Mira016 image sensor
Date: Tue, 8 Sep 2026 11:16:26 +0300 [thread overview]
Message-ID: <ap_EWstoCsLOkZ6x@kekkonen.localdomain> (raw)
In-Reply-To: <20260908-mira016-v4-1-1950504c131c@ideasonboard.com>
Hi Jacopo,
On Tue, Sep 08, 2026 at 09:57:23AM +0200, Jacopo Mondi wrote:
> Add bindings for the ams OSRAM Mira016 image sensor.
>
> Signed-off-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> .../devicetree/bindings/media/i2c/ams,mira016.yaml | 97 ++++++++++++++++++++++
> MAINTAINERS | 7 ++
> 2 files changed, 104 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ams,mira016.yaml b/Documentation/devicetree/bindings/media/i2c/ams,mira016.yaml
> new file mode 100644
> index 000000000000..49a606fca6cb
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/ams,mira016.yaml
> @@ -0,0 +1,97 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/ams,mira016.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: AMS 0.16 MP NIR enhanced global shutter image sensor
> +
> +maintainers:
> + - Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> + - Philippe Baetens <philippebaetens@gmail.com>
> +
> +description:
> + Mira016 is a 0.16 MP NIR enhanced global shutter image sensor designed for 2D
> + and 3D consumer and industrial machine vision applications. The sensor is
> + compliant to the MIPI CSI-2 v1.3 protocol interface and the D-PHY v1.2
> + physical layer specifications to transmit the image data to the host
> + processor. It uses one data lane and one clock lane operating up to 1.5 Gbps.
> +
> +allOf:
> + - $ref: /schemas/media/video-interface-devices.yaml#
> +
> +properties:
> + compatible:
> + const: ams,mira016
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + vdd28-supply:
> + description:
> + I/O voltage supply, 2.8 volts
> +
> + vdd11-supply:
> + description:
> + I/O voltage supply, 1.1 volts
> +
> + reset-gpios:
> + description: Sensor reset (RST_N) GPIO
> + maxItems: 1
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + additionalProperties: false
> + description:
> + Video output port
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + data-lanes:
> + items:
> + - const: 1
The device obviously supports non-continuous clock mode (and that's what
the driver also only does right now) but as the continous clock mode is
required by CSI-2, I presume the device can do both.
So I think you should have
clock-noncontinuous: true
here.
> +
> + required:
> + - data-lanes
> + - link-frequencies
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - vdd28-supply
> + - vdd11-supply
> + - port
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + camera@36 {
> + compatible = "ams,mira016";
> + reg = <0x36>;
> + clocks = <&cam1_clk>;
> +
> + vdd28-supply = <&cam1_reg>;
> + vdd11-supply = <&cam_dummy_reg>;
> +
> + port {
> + endpoint {
> + data-lanes = <1>;
> + link-frequencies = /bits/ 64 <750000000>;
> + };
> + };
> + };
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e12dc3ca57ab..1c24b05b378b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1454,6 +1454,13 @@ S: Maintained
> F: Documentation/devicetree/bindings/iio/light/ams,as73211.yaml
> F: drivers/iio/light/as73211.c
>
> +AMS MIRA016 DRIVER
> +M: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> +M: Philippe Baetens <philippebaetens@gmail.com>
> +L: linux-media@vger.kernel.org
> +S: Maintained
> +F: Documentation/devicetree/bindings/media/i2c/ams,mira016.yaml
> +
> AMT (Automatic Multicast Tunneling)
> M: Taehee Yoo <ap420073@gmail.com>
> L: netdev@vger.kernel.org
>
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-09-08 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 7:57 [PATCH v4 0/2] media: i2c: Add driver for Mira016 Jacopo Mondi
2026-09-08 7:57 ` [PATCH v4 1/2] dt-bindings: media: i2c: Add Mira016 image sensor Jacopo Mondi
2026-09-08 8:16 ` Sakari Ailus [this message]
2026-09-08 11:46 ` Jacopo Mondi
2026-09-08 11:48 ` Sakari Ailus
2026-09-09 7:35 ` Jacopo Mondi
2026-09-09 8:09 ` Sakari Ailus
2026-09-09 9:56 ` Jacopo Mondi
2026-09-12 11:40 ` Sakari Ailus
2026-09-08 7:57 ` [PATCH v4 2/2] media: i2c: mira016: Add driver for Mira016 Jacopo Mondi
2026-09-08 8:11 ` sashiko-bot
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=ap_EWstoCsLOkZ6x@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=jai.luthra@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=philippebaetens@gmail.com \
--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