From: Rob Herring <robh@kernel.org>
To: Mehdi Djait <mehdi.djait@bootlin.com>
Cc: mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
laurent.pinchart@ideasonboard.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, alexandre.belloni@bootlin.com,
maxime.chevallier@bootlin.com, paul.kocialkowski@bootlin.com
Subject: Re: [PATCH v7 2/3] media: dt-bindings: media: i2c: Add bindings for TW9900
Date: Tue, 17 Oct 2023 14:48:50 -0500 [thread overview]
Message-ID: <20231017194850.GA2565799-robh@kernel.org> (raw)
In-Reply-To: <d5b2b2584fd471a037e574086bfd193b22fb9587.1697463708.git.mehdi.djait@bootlin.com>
On Mon, Oct 16, 2023 at 03:58:32PM +0200, Mehdi Djait wrote:
> The Techwell TW9900 is a video decoder supporting multiple input
> standards, such as PAL and NTSC, and outputs a BT.656 video
> signal.
>
> It's designed to be low-power, posesses some features such as a
> programmable comb-filter, and automatic input standard detection
>
> Signed-off-by: Mehdi Djait <mehdi.djait@bootlin.com>
> ---
> V6->V7:
> - added powerdown-gpios and input ports
> - used 4 spaces for example identation
>
> V5->V6:
> - This commit had a "Reviewed-by: Rob Herring <robh@kernel.org>" Tag but
> decided not to collect it because the last Iteration was more than 2
> years ago
> - removed SECAM from the mentioned standards
> - changed maintainer
>
> V4->V5:
> - renamed the file to match the compatible string, and referenced
> the graph.yaml schema
>
> V3->V4:
> - add the missing reset-gpios node to the binding
>
> V2->V3:
> - fix the example not compiling due to a typo in the reset-gpios
> node.
>
> .../bindings/media/i2c/techwell,tw9900.yaml | 82 +++++++++++++++++++
> 1 file changed, 82 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/techwell,tw9900.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/techwell,tw9900.yaml b/Documentation/devicetree/bindings/media/i2c/techwell,tw9900.yaml
> new file mode 100644
> index 000000000000..244289a9a3e0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/techwell,tw9900.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/techwell,tw9900.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Techwell TW9900 NTSC/PAL video decoder
> +
> +maintainers:
> + - Mehdi Djait <mehdi.djait@bootlin.com>
> +
> +description:
> + The tw9900 is a multi-standard video decoder, supporting NTSC, PAL standards
> + with auto-detection features.
> +
> +properties:
> + compatible:
> + const: techwell,tw9900
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply:
> + description: VDD power supply
> +
> + reset-gpios:
> + description: GPIO descriptor for the RESET input pin
> + maxItems: 1
> +
> + powerdown-gpios:
> + description: GPIO descriptor for the POWERDOWN input pin
> + maxItems: 1
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> + properties:
> + port@3:
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Video port for the decoder output.
> +
> + patternProperties:
> + "^port@[0-2]$":
> + $ref: /schemas/graph.yaml#/properties/port
> + description: Analog video input port.
You need to define each port (0, 1, 2). Are those each component or
composite, s-video, and component? The latter would make more sense as I
don't think there would be a need to route each component to different
place. It's logically just 1 stream.
> +
> + required:
> + - port@3
> +
> +required:
> + - compatible
> + - ports
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + video-decoder@44 {
> + compatible = "techwell,tw9900";
> + reg = <0x44>;
> +
> + vdd-supply = <&tw9900_supply>;
> + reset-gpios = <&gpio2 5 GPIO_ACTIVE_LOW>;
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + port@3 {
> + reg = <3>;
> + endpoint {
> + remote-endpoint = <&vip_in>;
> + };
> + };
> + };
> + };
> + };
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-10-17 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:58 [PATCH v7 0/3] media: i2c: Introduce driver for the TW9900 video decoder Mehdi Djait
2023-10-16 13:58 ` [PATCH v7 1/3] dt-bindings: vendor-prefixes: Add techwell vendor prefix Mehdi Djait
2023-10-16 13:58 ` [PATCH v7 2/3] media: dt-bindings: media: i2c: Add bindings for TW9900 Mehdi Djait
2023-10-17 7:45 ` Conor Dooley
2023-10-17 19:48 ` Rob Herring [this message]
2023-10-16 13:58 ` [PATCH v7 3/3] media: i2c: Introduce a driver for the Techwell TW9900 decoder Mehdi Djait
2023-11-02 10:03 ` Paul Kocialkowski
2023-11-06 14:58 ` Mehdi Djait
2023-11-06 15:25 ` Paul Kocialkowski
2023-11-06 15:49 ` Mehdi Djait
2023-11-06 17:58 ` Paul Kocialkowski
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=20231017194850.GA2565799-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=thomas.petazzoni@bootlin.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