From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Alain Volmat <alain.volmat@foss.st.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Ondřej Jirman" <megi@xff.cz>, "Pavel Machek" <pavel@ucw.cz>,
"Arnaud Ferraris" <arnaud.ferraris@collabora.com>,
"Andrey Skvortsov" <andrej.skvortzov@gmail.com>
Subject: [PATCH 1/2] dt-bindings: media: i2c: add galaxycore,gc2145 DVP bus support
Date: Sun, 18 Feb 2024 01:03:07 +0300 [thread overview]
Message-ID: <20240217220308.594883-2-andrej.skvortzov@gmail.com> (raw)
In-Reply-To: <20240217220308.594883-1-andrej.skvortzov@gmail.com>
Don't require link-frequencies like it's done for ov5640, that
supports both CSI-2 and DVP. And v4l2_fwnode_endpoint_alloc_parse
ignores link-frequencies property for DVP endpoint. It's used only for
CSI-2 endpoints
Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
---
.../bindings/media/i2c/galaxycore,gc2145.yaml | 33 +++++++++++++++++--
1 file changed, 30 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/galaxycore,gc2145.yaml b/Documentation/devicetree/bindings/media/i2c/galaxycore,gc2145.yaml
index 1726ecca4c77..fb376b9d0f2a 100644
--- a/Documentation/devicetree/bindings/media/i2c/galaxycore,gc2145.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/galaxycore,gc2145.yaml
@@ -61,9 +61,6 @@ properties:
properties:
link-frequencies: true
- required:
- - link-frequencies
-
required:
- endpoint
@@ -110,4 +107,34 @@ examples:
};
};
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ camera@3c {
+ compatible = "galaxycore,gc2145";
+ reg = <0x3c>;
+ clocks = <&clk_ext_camera>;
+ iovdd-supply = <&scmi_v3v3_sw>;
+ avdd-supply = <&scmi_v3v3_sw>;
+ dvdd-supply = <&scmi_v3v3_sw>;
+ powerdown-gpios = <&mcp23017 3 (GPIO_ACTIVE_LOW | GPIO_PUSH_PULL)>;
+ reset-gpios = <&mcp23017 4 (GPIO_ACTIVE_LOW | GPIO_PUSH_PULL)>;
+
+ port {
+ endpoint {
+ remote-endpoint = <¶llel_from_gc2145>;
+ bus-width = <8>;
+ hsync-active = <1>;
+ vsync-active = <1>;
+ data-active = <1>;
+ pclk-sample = <1>;
+ };
+ };
+ };
+ };
+
...
--
2.43.0
next prev parent reply other threads:[~2024-02-17 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 22:03 [PATCH 0/2] media: gc2145: add basic dvp " Andrey Skvortsov
2024-02-17 22:03 ` Andrey Skvortsov [this message]
2024-02-20 10:04 ` [PATCH 1/2] dt-bindings: media: i2c: add galaxycore,gc2145 DVP " Krzysztof Kozlowski
2024-02-20 10:46 ` Sakari Ailus
2024-02-20 10:47 ` Sakari Ailus
2024-02-22 5:33 ` Andrey Skvortsov
2024-02-22 5:52 ` Andrey Skvortsov
2024-02-17 22:03 ` [PATCH 2/2] media: gc2145: implement basic dvp " Andrey Skvortsov
2024-02-20 10:55 ` Sakari Ailus
2024-02-22 5:20 ` Andrey Skvortsov
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=20240217220308.594883-2-andrej.skvortzov@gmail.com \
--to=andrej.skvortzov@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=arnaud.ferraris@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=megi@xff.cz \
--cc=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®