From: Rob Herring <robh@kernel.org>
To: Andrey Konovalov <andrey.konovalov@linaro.org>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, peter.griffin@linaro.org,
ezequiel@collabora.com
Subject: Re: [PATCH v2 1/2] dt-bindings: media: i2c: Add IMX219 CMOS sensor binding
Date: Sat, 4 Jan 2020 14:53:22 -0700 [thread overview]
Message-ID: <20200104215322.GA548@bogus> (raw)
In-Reply-To: <20191227122114.23075-2-andrey.konovalov@linaro.org>
On Fri, Dec 27, 2019 at 03:21:13PM +0300, Andrey Konovalov wrote:
> Add YAML device tree binding for IMX219 CMOS image sensor, and
> the relevant MAINTAINERS entries.
>
> Signed-off-by: Andrey Konovalov <andrey.konovalov@linaro.org>
> ---
> .../devicetree/bindings/media/i2c/imx219.yaml | 134 ++++++++++++++++++
> MAINTAINERS | 8 ++
> 2 files changed, 142 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/imx219.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/imx219.yaml b/Documentation/devicetree/bindings/media/i2c/imx219.yaml
> new file mode 100644
> index 000000000000..b58aa49a7c03
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/imx219.yaml
> @@ -0,0 +1,134 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/imx219.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sony 1/4.0-Inch 8Mpixel CMOS Digital Image Sensor
> +
> +maintainers:
> + - Dave Stevenson <dave.stevenson@raspberrypi.com>
> +
> +description: |-
> + The Sony imx219 is a 1/4.0-inch CMOS active pixel digital image sensor
> + with an active array size of 3280H x 2464V. It is programmable through
> + I2C interface. The I2C address is fixed to 0x10 as per sensor data sheet.
> + Image data is sent through MIPI CSI-2, which is configured as either 2 or
> + 4 data lanes.
> +
> +properties:
> + compatible:
> + const: sony,imx219
> +
> + reg:
> + description: I2C device address
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: xclk
> +
> + VDIG-supply:
> + description:
> + Digital I/O voltage supply, 1.8 volts
> +
> + VANA-supply:
> + description:
> + Analog voltage supply, 2.8 volts
> +
> + VDDL-supply:
> + description:
> + Digital core voltage supply, 1.2 volts
> +
> + xclr-gpios:
> + description: |-
> + Reference to the GPIO connected to the xclr pin, if any.
> + Must be released (set high) after all supplies are applied.
> +
> + camera-clk:
> + type: object
> +
> + description: Clock source for imx219
This clock is external to the sensor, so a node for a fixed clock should
be too.
> +
> + properties:
> + clock-frequency: true
> +
> + required:
> + - clock-frequency
> +
> + # See ../video-interfaces.txt for more details
> + port:
> + type: object
> + properties:
> + endpoint:
> + type: object
> + properties:
> + clock-lanes:
> + const: 0
> +
> + data-lanes:
> + description: |-
> + Should be <1 2> for two-lane operation, or <1 2 3 4> for
> + four-lane operation.
> + oneOf:
> + - const: [[ 1, 2 ]]
> + - const: [[ 1, 2, 3, 4 ]]
Not sure if this actually works. If it does, it exposes how we encode
the DT yaml format which we don't want to do here.
It should be:
oneOf:
- items:
- const: 1
- const: 2
- items:
- const: 1
- const: 2
- const: 3
- const: 4
Really, I think you shouldn't need the 2nd case as that should be the
default.
> +
> + clock-noncontinuous:
> + type: boolean
> + description: |-
> + Presence of this boolean property decides whether the MIPI CSI-2
> + clock is continuous or non-continuous.
> +
> + required:
> + - clock-lanes
> + - data-lanes
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - VANA-supply
> + - VDIG-supply
> + - VDDL-supply
> + - port
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + imx219: sensor@10 {
> + compatible = "sony,imx219";
> + reg = <0x10>;
> + clocks = <&imx219_clk>;
> + clock-names = "xclk";
> + VANA-supply = <&imx219_vana>; /* 2.8v */
> + VDIG-supply = <&imx219_vdig>; /* 1.8v */
> + VDDL-supply = <&imx219_vddl>; /* 1.2v */
> +
> + imx219_clk: camera-clk {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <24000000>;
> + };
> +
> + port {
> + imx219_0: endpoint {
> + remote-endpoint = <&csi1_ep>;
> + clock-lanes = <0>;
> + data-lanes = <1 2>;
> + clock-noncontinuous;
> + };
> + };
> + };
> + };
> +
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ffa3371bc750..f7b6c24ec081 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15350,6 +15350,14 @@ S: Maintained
> F: drivers/media/i2c/imx214.c
> F: Documentation/devicetree/bindings/media/i2c/sony,imx214.txt
>
> +SONY IMX219 SENSOR DRIVER
> +M: Dave Stevenson <dave.stevenson@raspberrypi.com>
> +L: linux-media@vger.kernel.org
> +T: git git://linuxtv.org/media_tree.git
> +S: Maintained
> +F: drivers/media/i2c/imx219.c
> +F: Documentation/devicetree/bindings/media/i2c/imx219.yaml
> +
> SONY IMX258 SENSOR DRIVER
> M: Sakari Ailus <sakari.ailus@linux.intel.com>
> L: linux-media@vger.kernel.org
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-01-04 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 12:21 [PATCH v2 0/2] Add IMX219 CMOS image sensor support Andrey Konovalov
2019-12-27 12:21 ` [PATCH v2 1/2] dt-bindings: media: i2c: Add IMX219 CMOS sensor binding Andrey Konovalov
2019-12-27 14:17 ` Sakari Ailus
2019-12-27 18:26 ` Andrey Konovalov
2019-12-30 9:24 ` Sakari Ailus
2020-01-06 14:56 ` Dave Stevenson
2020-01-04 21:53 ` Rob Herring [this message]
2020-01-10 20:18 ` Andrey Konovalov
2019-12-27 12:21 ` [PATCH v2 2/2] media: i2c: Add driver for Sony IMX219 sensor Andrey Konovalov
2019-12-27 14:55 ` Sakari Ailus
2020-01-13 19:16 ` Andrey Konovalov
2020-01-14 11:34 ` Dave Stevenson
2020-01-17 8:49 ` Sakari Ailus
2020-01-17 8:39 ` Sakari Ailus
2019-12-30 16:33 ` Ezequiel Garcia
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=20200104215322.GA548@bogus \
--to=robh@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=peter.griffin@linaro.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;
as well as URLs for NNTP newsgroup(s).