From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, Jacopo Mondi <jacopo@jmondi.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] media: dt-bindings: media: i2c: Add MT9M114 camera sensor binding
Date: Tue, 8 Feb 2022 20:47:32 +0200 [thread overview]
Message-ID: <YgK6xAgAVHUSsQND@pendragon.ideasonboard.com> (raw)
In-Reply-To: <YgKfdR72TNavj68v@paasikivi.fi.intel.com>
Hi Sakari,
On Tue, Feb 08, 2022 at 06:51:01PM +0200, Sakari Ailus wrote:
> On Mon, Feb 07, 2022 at 03:20:54AM +0200, Laurent Pinchart wrote:
> > Add device tree binding for the onsemi MT9M114 CMOS camera sensor.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> > Changes since v1:
> >
> > - Use graph schema
> > - Drop unneeded properties
> > - Rename ON Semiconductor to onsemi
> > ---
> > .../bindings/media/i2c/onnn,mt9m114.yaml | 110 ++++++++++++++++++
> > MAINTAINERS | 7 ++
> > 2 files changed, 117 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml b/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml
> > new file mode 100644
> > index 000000000000..55b67833f9a1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/media/i2c/onnn,mt9m114.yaml
> > @@ -0,0 +1,110 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/media/i2c/onnn,mt9m114.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: onsemi 1/6-inch 720p CMOS Digital Image Sensor
> > +
> > +maintainers:
> > + - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > +
> > +description: |-
> > + The onsemi MT9M114 is a 1/6-inch 720p (1.26 Mp) CMOS digital image sensor
> > + with an active pixel-array size of 1296H x 976V. It is programmable through
> > + an I2C interface and outputs image data over a 8-bit parallel or 1-lane MIPI
> > + CSI-2 connection.
> > +
> > +properties:
> > + compatible:
> > + const: onnn,mt9m114
> > +
> > + reg:
> > + description: I2C device address
> > + enum:
> > + - 0x48
> > + - 0x5d
> > +
> > + clocks:
> > + description: EXTCLK clock signal
> > + maxItems: 1
> > +
> > + vdd-supply:
> > + description:
> > + Core digital voltage supply, 1.8V
> > +
> > + vddio-supply:
> > + description:
> > + I/O digital voltage supply, 1.8V or 2.8V
> > +
> > + vaa-supply:
> > + description:
> > + Analog voltage supply, 2.8V
> > +
> > + reset-gpios:
> > + description: |-
> > + Reference to the GPIO connected to the RESET_BAR pin, if any (active
> > + low).
> > +
> > + port:
> > + $ref: /schemas/graph.yaml#/$defs/port-base
> > + additionalProperties: false
> > +
> > + properties:
> > + endpoint:
> > + $ref: /schemas/media/video-interfaces.yaml#
> > + additionalProperties: false
> > +
> > + properties:
> > + bus-type:
> > + enum: [4, 5, 6]
>
> With bus-type 5, shouldn't you have the parallel interface sync signal
> polarity properties? Possibly also others if the hardware supports them.
As far as I can tell, the hardware has fixed polarities for all signals.
Both hsync and vsync (called LINE_VALID and FRAME_VALID here) are active
high.
> > +
> > + remote-endpoint: true
> > +
> > + # The number and mapping of lanes (for CSI-2), and the bus width and
> > + # signal polarities (for parallel and BT.656) are fixed and must not
> > + # be specified.
> > +
> > + required:
> > + - bus-type
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - clocks
> > + - vdd-supply
> > + - vddio-supply
> > + - vaa-supply
> > + - port
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/gpio/gpio.h>
> > +
> > + i2c0 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + sensor@48 {
> > + compatible = "onnn,mt9m114";
> > + reg = <0x48>;
> > +
> > + clocks = <&clk24m 0>;
> > +
> > + reset-gpios = <&gpio5 21 GPIO_ACTIVE_LOW>;
> > +
> > + vddio-supply = <®_cam_1v8>;
> > + vdd-supply = <®_cam_1v8>;
> > + vaa-supply = <®_2p8v>;
> > +
> > + port {
> > + endpoint {
> > + bus-type = <4>;
> > + remote-endpoint = <&mipi_csi_in>;
> > + };
> > + };
> > + };
> > + };
> > +...
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index f41088418aae..e9919a359c12 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -13096,6 +13096,13 @@ T: git git://linuxtv.org/media_tree.git
> > F: drivers/media/i2c/mt9m032.c
> > F: include/media/i2c/mt9m032.h
> >
> > +MT9M114 ONSEMI SENSOR DRIVER
> > +M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > +L: linux-media@vger.kernel.org
> > +S: Maintained
> > +T: git git://linuxtv.org/media_tree.git
> > +F: Documentation/devicetree/bindings/media/i2c.onnn,mt9m114.yaml
> > +
> > MT9P031 APTINA CAMERA SENSOR
> > M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > L: linux-media@vger.kernel.org
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-02-08 18:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 1:20 [PATCH v2 0/2] media: Add onsemi MT9M114 camera sensor driver Laurent Pinchart
2022-02-07 1:20 ` [PATCH v2 1/2] media: dt-bindings: media: i2c: Add MT9M114 camera sensor binding Laurent Pinchart
2022-02-08 16:51 ` Sakari Ailus
2022-02-08 18:47 ` Laurent Pinchart [this message]
2022-02-12 20:33 ` Sakari Ailus
2022-02-12 22:12 ` Laurent Pinchart
2023-02-20 23:52 ` Laurent Pinchart
2023-02-21 12:42 ` Sakari Ailus
2023-02-21 12:48 ` Laurent Pinchart
2023-09-16 22:57 ` Laurent Pinchart
2022-05-13 10:33 ` Jacopo Mondi
2023-02-20 23:46 ` Laurent Pinchart
2023-02-21 0:25 ` Laurent Pinchart
2022-02-11 16:08 ` Rob Herring
2022-02-07 1:20 ` [PATCH v2 2/2] media: i2c: Add driver for onsemi MT9M114 camera sensor Laurent Pinchart
2022-02-12 20:39 ` Sakari Ailus
2023-09-17 15:53 ` Laurent Pinchart
2022-05-13 10:27 ` Jacopo Mondi
2022-06-14 14:02 ` Jacopo Mondi
2023-09-16 23:35 ` Laurent Pinchart
2023-09-17 0:23 ` Laurent Pinchart
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=YgK6xAgAVHUSsQND@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=jacopo@jmondi.org \
--cc=linux-media@vger.kernel.org \
--cc=robh+dt@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