From: Krzysztof Kozlowski <krzk@kernel.org>
To: Walter Werner Schneider <contact@schnwalter.eu>,
linux-media@vger.kernel.org,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: media: i2c: Add ov2732 image sensor
Date: Thu, 18 Dec 2025 21:02:20 +0100 [thread overview]
Message-ID: <749e8633-1742-4e03-b1fd-2a601f218a0a@kernel.org> (raw)
In-Reply-To: <20251218-ov2732-driver-v2-1-fb763644d62c@schnwalter.eu>
On 18/12/2025 19:15, Walter Werner Schneider wrote:
> + avdd-supply:
> + description: Analog Domain Power Supply
> +
> + dovdd-supply:
> + description: I/O Domain Power Supply
> +
> + dvdd-supply:
> + description: Digital Domain Power Supply
> +
> + pwdn-gpios:
Use name from gpio-consumer-common, so "powerdown-gpios".
> + maxItems: 1
> + description: Reference to the GPIO connected to the pwdn pin. Active high.
high?
> +
> + reset-gpios:
> + maxItems: 1
> + description: Reference to the GPIO connected to the reset pin. Active high.
Are you sure this is active high?
> +
> + port:
> + description: MIPI CSI-2 transmitter port
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + additionalProperties: false
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + data-lanes:
> + items:
> + - const: 1
> + - const: 2
> + link-frequencies: true
Drop
> + remote-endpoint: true
Drop
> +
> + required:
> + - data-lanes
> + - link-frequencies
> + - remote-endpoint
Drop remote endpoint
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - avdd-supply
> + - dovdd-supply
> + - dvdd-supply
> + - port
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ov2732: camera@36 {
> + compatible = "ovti,ov2732";
> + reg = <0x36>;
> + clocks = <&ov2732_clk>;
> + clock-names = "xvclk";
> +
> + avdd-supply = <&ov2732_avdd>;
> + dovdd-supply = <&ov2732_dovdd>;
> + dvdd-supply = <&ov2732_dvdd>;
> +
> + pwdn-gpios = <&gpio0 13 GPIO_ACTIVE_LOW>;
> + reset-gpios = <&gpio0 8 GPIO_ACTIVE_LOW>;
And here (probably correct) active low?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-18 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 18:15 [PATCH v2 0/2] media: i2c: Add ov2732 image sensor driver Walter Werner Schneider
2025-12-18 18:15 ` [PATCH v2 1/2] dt-bindings: media: i2c: Add ov2732 image sensor Walter Werner Schneider
2025-12-18 20:02 ` Krzysztof Kozlowski [this message]
2025-12-18 18:15 ` [PATCH v2 2/2] media: i2c: Add ov2732 image sensor driver Walter Werner Schneider
2025-12-18 20:05 ` Krzysztof Kozlowski
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=749e8633-1742-4e03-b1fd-2a601f218a0a@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=contact@schnwalter.eu \
--cc=devicetree@vger.kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@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