devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names
@ 2024-04-02 17:40 Fabio Estevam
  2024-04-02 17:40 ` [PATCH v4 2/2] media: dt-bindings: ovti,ov2680: Document link-frequencies Fabio Estevam
  2024-04-03 16:51 ` [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names Rob Herring
  0 siblings, 2 replies; 4+ messages in thread
From: Fabio Estevam @ 2024-04-02 17:40 UTC (permalink / raw)
  To: sakari.ailus
  Cc: rmfrfs, laurent.pinchart, hansg, robh, krzysztof.kozlowski+dt,
	conor+dt, linux-media, devicetree, Fabio Estevam

From: Fabio Estevam <festevam@denx.de>

The original .txt bindings had the OV2680 power supply names correct,
but the transition from .txt to yaml spelled them incorrectly.

Fix the OV2680 power supply names as the original .txt bindings
as these are the names used by the OV2680 driver and in devicetree.

Fixes: 57226cd8c8bf ("media: dt-bindings: ov2680: convert bindings to yaml")
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v3:
- Newly introduced.

 .../bindings/media/i2c/ovti,ov2680.yaml        | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
index cf456f8d9ddc..c87677f5e2a2 100644
--- a/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
@@ -37,15 +37,15 @@ properties:
       active low.
     maxItems: 1
 
-  dovdd-supply:
+  DOVDD-supply:
     description:
       Definition of the regulator used as interface power supply.
 
-  avdd-supply:
+  AVDD-supply:
     description:
       Definition of the regulator used as analog power supply.
 
-  dvdd-supply:
+  DVDD-supply:
     description:
       Definition of the regulator used as digital power supply.
 
@@ -59,9 +59,9 @@ required:
   - reg
   - clocks
   - clock-names
-  - dovdd-supply
-  - avdd-supply
-  - dvdd-supply
+  - DOVDD-supply
+  - AVDD-supply
+  - DVDD-supply
   - reset-gpios
   - port
 
@@ -82,9 +82,9 @@ examples:
                 clock-names = "xvclk";
                 reset-gpios = <&gpio1 3 GPIO_ACTIVE_LOW>;
 
-                dovdd-supply = <&sw2_reg>;
-                dvdd-supply = <&sw2_reg>;
-                avdd-supply = <&reg_peri_3p15v>;
+                DOVDD-supply = <&sw2_reg>;
+                DVDD-supply = <&sw2_reg>;
+                AVDD-supply = <&reg_peri_3p15v>;
 
                 port {
                         ov2680_to_mipi: endpoint {
-- 
2.34.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* [PATCH v4 2/2] media: dt-bindings: ovti,ov2680: Document link-frequencies
  2024-04-02 17:40 [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names Fabio Estevam
@ 2024-04-02 17:40 ` Fabio Estevam
  2024-04-03 16:52   ` Rob Herring
  2024-04-03 16:51 ` [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names Rob Herring
  1 sibling, 1 reply; 4+ messages in thread
From: Fabio Estevam @ 2024-04-02 17:40 UTC (permalink / raw)
  To: sakari.ailus
  Cc: rmfrfs, laurent.pinchart, hansg, robh, krzysztof.kozlowski+dt,
	conor+dt, linux-media, devicetree, Fabio Estevam

From: Fabio Estevam <festevam@denx.de>

Document the link-frequencies property as recommended by the following
document:

https://www.kernel.org/doc/html/v6.9-rc1/driver-api/media/camera-sensor.html#handling-clocks

Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Changes since v3:
- Only document link-frequencies.

 .../bindings/media/i2c/ovti,ov2680.yaml         | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
index c87677f5e2a2..634d3b821b8c 100644
--- a/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov2680.yaml
@@ -50,9 +50,23 @@ properties:
       Definition of the regulator used as digital power supply.
 
   port:
-    $ref: /schemas/graph.yaml#/properties/port
     description:
       A node containing an output port node.
+    $ref: /schemas/graph.yaml#/$defs/port-base
+    additionalProperties: false
+
+    properties:
+      endpoint:
+        $ref: /schemas/media/video-interfaces.yaml#
+        additionalProperties: false
+
+        properties:
+          link-frequencies: true
+
+          remote-endpoint: true
+
+        required:
+          - link-frequencies
 
 required:
   - compatible
@@ -89,6 +103,7 @@ examples:
                 port {
                         ov2680_to_mipi: endpoint {
                                 remote-endpoint = <&mipi_from_sensor>;
+                                link-frequencies = /bits/ 64 <330000000>;
                         };
                 };
         };
-- 
2.34.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names
  2024-04-02 17:40 [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names Fabio Estevam
  2024-04-02 17:40 ` [PATCH v4 2/2] media: dt-bindings: ovti,ov2680: Document link-frequencies Fabio Estevam
@ 2024-04-03 16:51 ` Rob Herring
  1 sibling, 0 replies; 4+ messages in thread
From: Rob Herring @ 2024-04-03 16:51 UTC (permalink / raw)
  To: Fabio Estevam
  Cc: Fabio Estevam, krzysztof.kozlowski+dt, laurent.pinchart,
	devicetree, linux-media, hansg, sakari.ailus, conor+dt, rmfrfs


On Tue, 02 Apr 2024 14:40:27 -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
> 
> The original .txt bindings had the OV2680 power supply names correct,
> but the transition from .txt to yaml spelled them incorrectly.
> 
> Fix the OV2680 power supply names as the original .txt bindings
> as these are the names used by the OV2680 driver and in devicetree.
> 
> Fixes: 57226cd8c8bf ("media: dt-bindings: ov2680: convert bindings to yaml")
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> Changes since v3:
> - Newly introduced.
> 
>  .../bindings/media/i2c/ovti,ov2680.yaml        | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH v4 2/2] media: dt-bindings: ovti,ov2680: Document link-frequencies
  2024-04-02 17:40 ` [PATCH v4 2/2] media: dt-bindings: ovti,ov2680: Document link-frequencies Fabio Estevam
@ 2024-04-03 16:52   ` Rob Herring
  0 siblings, 0 replies; 4+ messages in thread
From: Rob Herring @ 2024-04-03 16:52 UTC (permalink / raw)
  To: Fabio Estevam
  Cc: Fabio Estevam, rmfrfs, laurent.pinchart, linux-media, conor+dt,
	sakari.ailus, krzysztof.kozlowski+dt, devicetree, hansg


On Tue, 02 Apr 2024 14:40:28 -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
> 
> Document the link-frequencies property as recommended by the following
> document:
> 
> https://www.kernel.org/doc/html/v6.9-rc1/driver-api/media/camera-sensor.html#handling-clocks
> 
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
> Changes since v3:
> - Only document link-frequencies.
> 
>  .../bindings/media/i2c/ovti,ov2680.yaml         | 17 ++++++++++++++++-
>  1 file changed, 16 insertions(+), 1 deletion(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-04-03 16:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-04-02 17:40 [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names Fabio Estevam
2024-04-02 17:40 ` [PATCH v4 2/2] media: dt-bindings: ovti,ov2680: Document link-frequencies Fabio Estevam
2024-04-03 16:52   ` Rob Herring
2024-04-03 16:51 ` [PATCH v4 1/2] media: dt-bindings: ovti,ov2680: Fix the power supply names Rob Herring

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).