From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Cc: Paul Elder <paul.elder@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Julien Stephan <jstephan@baylibre.com>,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: media: Add bindings for THine THP7312 ISP
Date: Thu, 12 Oct 2023 21:57:38 +0200 [thread overview]
Message-ID: <aaa41ff2-d2e3-4c25-9654-065a02275619@linaro.org> (raw)
In-Reply-To: <20231012193737.7251-2-laurent.pinchart@ideasonboard.com>
On 12/10/2023 21:37, Laurent Pinchart wrote:
Thanks for the changes
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + additionalProperties: false
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + data-lanes:
> + description:
> + This property is for lane reordering between the THP7312 and the
> + SoC. The sensor supports either two-lane, or four-lane operation.
> + If this property is omitted four-lane operation is assumed. For
> + two-lane operation the property must be set to <1 2>.
> + minItems: 2
> + maxItems: 4
> + items:
> + maximum: 4
> +
> + sensors:
> + type: object
> + description: List of connected sensors
I don't understand why do you list sensors here. From the binding
description I understood these are external sensors, which usually sit
on I2C bus.
> +
> + properties:
> + "#address-cells":
> + const: 1
> +
> + "#size-cells":
> + const: 0
> +
> + patternProperties:
> + "^sensor@[01]":
> + type: object
> + description:
> + Sensors connected to the first and second input, with one node per
> + sensor.
> +
> + properties:
> + thine,model:
> + $ref: /schemas/types.yaml#/definitions/string
> + description:
> + Model of the connected sensors. Must be a valid compatible string.
Then why this isn't compatible?
> +
> + reg:
> + maxItems: 1
> + description: THP7312 input port number
> +
> + data-lanes:
> + $ref: /schemas/media/video-interfaces.yaml#/properties/data-lanes
> + items:
> + maxItems: 4
> + description:
> + This property is for lane reordering between the THP7312 and the imaging
> + sensor that it is connected to.
> +
> + patternProperties:
> + ".*-supply":
> + description: Power supplies for the sensor
> +
> + required:
> + - reg
> + - data-lanes
> +
> + additionalProperties: false
> +
> + required:
> + - "#address-cells"
> + - "#size-cells"
> +
> + additionalProperties: false
> +
> +required:
> + - compatible
> + - reg
> + - reset-gpios
> + - clocks
> + - vddcore-supply
> + - vhtermrx-supply
> + - vddtx-supply
> + - vddhost-supply
> + - vddcmos-supply
> + - vddgpio-0-supply
> + - vddgpio-1-supply
> + - sensors
> + - port
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + camera@61 {
> + compatible = "thine,thp7312";
> + reg = <0x61>;
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&cam1_pins_default>;
> +
> + reset-gpios = <&pio 119 GPIO_ACTIVE_LOW>;
> + clocks = <&camera61_clk>;
> +
> + vddcore-supply = <&vsys_v4p2>;
> + vhtermrx-supply = <&vsys_v4p2>;
> + vddtx-supply = <&vsys_v4p2>;
> + vddhost-supply = <&vsys_v4p2>;
> + vddcmos-supply = <&vsys_v4p2>;
> + vddgpio-0-supply = <&vsys_v4p2>;
> + vddgpio-1-supply = <&vsys_v4p2>;
> +
> + orientation = <0>;
> + rotation = <0>;
> +
> + sensors {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + sensor@0 {
> + thine,model = "sony,imx258";
> + reg = <0>;
> +
> + data-lanes = <4 1 3 2>;
> +
> + dovdd-supply = <&vsys_v4p2>;
> + avdd-supply = <&vsys_v4p2>;
> + dvdd-supply = <&vsys_v4p2>;
> + };
> + };
> +
> + port {
> + thp7312_2_endpoint: endpoint {
> + remote-endpoint = <&mipi_thp7312_2>;
> + data-lanes = <4 2 1 3>;
> + };
> + };
> + };
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-10-12 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 19:37 [PATCH v3 0/3] media: i2c: Add driver for THine THP7312 ISP Laurent Pinchart
2023-10-12 19:37 ` [PATCH v3 1/3] dt-bindings: media: Add bindings " Laurent Pinchart
2023-10-12 19:57 ` Krzysztof Kozlowski [this message]
2023-10-15 12:39 ` Laurent Pinchart
2023-10-16 5:06 ` Krzysztof Kozlowski
2023-10-12 19:37 ` [PATCH v3 2/3] media: uapi: Add controls for the " Laurent Pinchart
2023-10-12 19:37 ` [PATCH v3 3/3] media: i2c: Add driver for THine THP7312 Laurent Pinchart
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=aaa41ff2-d2e3-4c25-9654-065a02275619@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jstephan@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=paul.elder@ideasonboard.com \
--cc=robh+dt@kernel.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).