From: Tomasz Figa <tfiga@chromium.org>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hao He <hao.he@bitland.com.cn>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
drinkcat@chromium.org, Xingyu Wu <wuxy@bitland.com.cn>,
dongchun.zhu@mediatek.com, sj.huang@mediatek.com,
darfur_liu@gcoreinc.com, hao.he7@gmail.com,
Tomasz Figa <tfiga@chromium.org>
Subject: [PATCH v4 2/4] media: dt-bindings: media: i2c: Add bindings for GC5035
Date: Wed, 2 Sep 2020 22:48:11 +0000 [thread overview]
Message-ID: <20200902224813.14283-3-tfiga@chromium.org> (raw)
In-Reply-To: <20200902224813.14283-1-tfiga@chromium.org>
Add YAML device tree bindings for Galaxycore Inc. GC5035 imaging sensor.
Signed-off-by: Tomasz Figa <tfiga@chromium.org>
---
.../devicetree/bindings/media/i2c/gc5035.yaml | 142 ++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/gc5035.yaml
diff --git a/Documentation/devicetree/bindings/media/i2c/gc5035.yaml b/Documentation/devicetree/bindings/media/i2c/gc5035.yaml
new file mode 100644
index 000000000000..cf8cc3b581cf
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/i2c/gc5035.yaml
@@ -0,0 +1,142 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+# Copyright (c) 2019 MediaTek Inc.
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/media/i2c/gc5035.yaml
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Galaxycore Inc. GC5035 CMOS Sensor Device Tree Bindings
+
+maintainers:
+ - Tomasz Figa <tfiga@chromium.org>
+
+description: |-
+ The Galaxycore Inc. GC5035 is a 5 megapixel, 1/5 inch CMOS 10-bit Bayer image
+ sensor that delivers 2592x1944 at 30fps. This chip is programmable through
+ an I2C interface. The image output is available via a MIPI CSI-2 interface.
+
+properties:
+ compatible:
+ const: galaxycore,gc5035
+
+ reg:
+ maxItems: 1
+
+ clocks:
+ maxItems: 1
+
+ clock-names:
+ description:
+ Input clock for the sensor.
+ items:
+ - const: inclk
+
+ clock-frequency:
+ description:
+ Frequency of the inclk clock in Hz.
+
+ iovdd-supply:
+ description:
+ Regulator driving the I/O power rail.
+
+ avdd28-supply:
+ description:
+ Regulator driving the analog power rail.
+
+ dvdd12-supply:
+ description:
+ Regulator driving the digital power rail.
+
+ resetb-gpios:
+ description:
+ The GPIO pin that drives the RESETB signal, controlling sensor reset.
+ The RESETB signal must be driven low to activate the reset, so the
+ GPIO_ACTIVE_LOW flag should be given by default.
+
+ pwdn-gpios:
+ description:
+ The GPIO pin that drives the PWDN signal, controlling sensor power-down
+ mode. The PWDN signal must be driven low to activate the power-down
+ mode, so the GPIO_ACTIVE_LOW flag should be given by default.
+
+ port:
+ type: object
+ additionalProperties: false
+ description:
+ A node containing an output port node with an endpoint definition
+ as documented in
+ Documentation/devicetree/bindings/media/video-interfaces.txt
+
+ properties:
+ endpoint:
+ type: object
+ additionalProperties: false
+
+ properties:
+ data-lanes:
+ items:
+ - const: 1
+ - const: 2
+
+ link-frequencies: true
+ remote-endpoint: true
+
+ required:
+ - data-lanes
+ - link-frequencies
+ - remote-endpoint
+
+ required:
+ - endpoint
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - clock-names
+ - clock-frequency
+ - iovdd-supply
+ - avdd28-supply
+ - dvdd12-supply
+ - resetb-gpios
+ - pwdn-gpios
+ - port
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ gc5035: camera@10 {
+ compatible = "galaxycore,gc5035";
+ reg = <0x10>;
+
+ reset-gpios = <&pio 111 GPIO_ACTIVE_LOW>;
+ pwdn-gpios = <&pio 112 GPIO_ACTIVE_LOW>;
+ pinctrl-names = "default";
+ pinctrl-0 = <&clk_24m_cam>;
+
+ clocks = <&cam_osc>;
+ clock-names = "inclk";
+ clock-frequency = <24000000>;
+
+ avdd28-supply = <&mt6358_vcama2_reg>;
+ dvdd12-supply = <&mt6358_vcamd_reg>;
+ iovdd-supply = <&mt6358_vcamio_reg>;
+
+ port {
+ wcam_out: endpoint {
+ remote-endpoint = <&mipi_in_wcam>;
+ data-lanes = <1 2>;
+ link-frequencies = /bits/ 64 <438000000>;
+ };
+ };
+ };
+ };
+...
+
--
2.28.0.402.g5ffc5be6b7-goog
next prev parent reply other threads:[~2020-09-02 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 22:48 [PATCH v4 0/4] Galaxycore GC5035 sensor driver Tomasz Figa
2020-09-02 22:48 ` [PATCH v4 1/4] dt-bindings: Add a vendor prefix for Galaxycore Inc Tomasz Figa
2020-09-14 20:26 ` Rob Herring
2020-09-02 22:48 ` Tomasz Figa [this message]
2020-09-02 23:30 ` [PATCH v4 2/4] media: dt-bindings: media: i2c: Add bindings for GC5035 Tomasz Figa
2020-09-03 16:34 ` Rob Herring
2020-09-02 22:48 ` [PATCH v4 3/4] media: i2c: Add a driver for the Galaxycore GC5035 sensor Tomasz Figa
2020-09-02 22:48 ` [PATCH v4 4/4] media: i2c: gc5035: Add OTP configuration handling Tomasz Figa
2020-09-08 9:42 ` 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=20200902224813.14283-3-tfiga@chromium.org \
--to=tfiga@chromium.org \
--cc=darfur_liu@gcoreinc.com \
--cc=devicetree@vger.kernel.org \
--cc=dongchun.zhu@mediatek.com \
--cc=drinkcat@chromium.org \
--cc=hao.he7@gmail.com \
--cc=hao.he@bitland.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sj.huang@mediatek.com \
--cc=wuxy@bitland.com.cn \
/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).