From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "jack.zhu" <jack.zhu@starfivetech.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Ripard <mripard@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, changhuang.liang@starfivetech.com
Subject: Re: [PATCH v1 02/11] media: dt-bindings: starfive,jh7110-mipi-csi2: add binding docmuent
Date: Fri, 3 Mar 2023 09:42:14 +0100 [thread overview]
Message-ID: <711f0e08-a8c8-45ef-08cf-6ca4f166ed4a@linaro.org> (raw)
In-Reply-To: <20230302091921.43309-3-jack.zhu@starfivetech.com>
On 02/03/2023 10:19, jack.zhu wrote:
> Add DT binding document for Starfive MIPI CSI2 receiver
Subject: drop second/last, redundant "add binding document". The
"dt-bindings" prefix is already stating that these are bindings and it
is a document. Write something useful instead.
>
> Signed-off-by: jack.zhu <jack.zhu@starfivetech.com>
> ---
> .../media/starfive,jh7110-mipi-csi2.yaml | 177 ++++++++++++++++++
> 1 file changed, 177 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/starfive,jh7110-mipi-csi2.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/starfive,jh7110-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/starfive,jh7110-mipi-csi2.yaml
> new file mode 100644
> index 000000000000..6569fac9e856
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/starfive,jh7110-mipi-csi2.yaml
> @@ -0,0 +1,177 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
Why for patch 1 and 2 you are using difference SPDX?
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/starfive,jh7110-mipi-csi2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Starfive JH7110 MIPI CSI-2 receiver
> +
> +maintainers:
> + - Jack Zhu <jack.zhu@starfivetech.com>
> + - Changhuang Liang <changhuang.liang@starfivetech.com>
> +
> +description: |-
Drop |-
> + The JH7110 MIPI CSI-2 receiver device is responsible for handling CSI2
> + protocol based camera sensor data stream.
> +
> +properties:
> + compatible:
> + enum:
> + - starfive,jh7110-csi2rx
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: CSI2Rx system clock
> + - description: Gated Register bank clock for APB interface
> + - description: pixel Clock for Stream interface 0
> + - description: pixel Clock for Stream interface 1
> + - description: pixel Clock for Stream interface 2
> + - description: pixel Clock for Stream interface 3
> +
> + clock-names:
> + items:
> + - const: sys_clk
> + - const: p_clk
> + - const: pixel_if0_clk
> + - const: pixel_if1_clk
> + - const: pixel_if2_clk
> + - const: pixel_if3_clk
Drop _clk suffixes
> +
> + resets:
> + items:
> + - description: CSI2Rx system reset
> + - description: Gated Register bank reset for APB interface
> + - description: pixel reset for Stream interface 0
> + - description: pixel reset for Stream interface 1
> + - description: pixel reset for Stream interface 2
> + - description: pixel reset for Stream interface 3
> +
> + reset-names:
> + items:
> + - const: sys_rst
Drop _rst suffixes
> + - const: p_rst
> + - const: pixel_if0_rst
> + - const: pixel_if1_rst
> + - const: pixel_if2_rst
> + - const: pixel_if3_rst
> +
> + phys:
> + maxItems: 1
> + description: MIPI D-PHY
> +
> + phy-names:
> + items:
> + - const: dphy
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + port@0:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + unevaluatedProperties: false
> + description:
> + Input port node, single endpoint describing the CSI-2 transmitter.
> +
> + properties:
> + endpoint:
> + $ref: video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + bus-type:
> + items:
This is not an array.
> + - const: 4
> +
> + clock-lanes:
> + maxItems: 1
Not an array...
> +
> + data-lanes:
> + minItems: 1
> + maxItems: 4
> + items:
> + maximum: 4
> +
> + required:
> + - bus-type
Since this is fixed 4, do you actually require it? Why?
> + - clock-lanes
> + - data-lanes
> +
> + port@1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + Output port node
> +
> + required:
> + - port@0
> + - port@1
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - resets
> + - reset-names
> + - phys
> + - phy-names
> + - ports
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> +
Drop blank line
> + csi2rx: csi-bridge@19800000 {
Maybe just "csi@"?
> + compatible = "starfive,jh7110-csi2rx";
> + reg = <0x19800000 0x10000>;
> + clocks = <&ispcrg 7>,
> + <&ispcrg 6>,
Indentation looks odd... did you align it?
> + <&ispcrg 8>,
> + <&ispcrg 9>,
> + <&ispcrg 10>,
> + <&ispcrg 11>;
> + clock-names = "sys_clk", "p_clk",
> + "pixel_if0_clk", "pixel_if1_clk",
> + "pixel_if2_clk", "pixel_if3_clk";
> + resets = <&ispcrg 9>,
> + <&ispcrg 4>,
> + <&ispcrg 5>,
> + <&ispcrg 6>,
> + <&ispcrg 7>,
> + <&ispcrg 8>;
> + reset-names = "sys_rst", "p_rst",
> + "pixel_if0_rst", "pixel_if1_rst",
> + "pixel_if2_rst", "pixel_if3_rst";
> + phys = <&csi_phy>;
> + phy-names = "dphy";
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-03 8:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302091921.43309-1-jack.zhu@starfivetech.com>
[not found] ` <20230302091921.43309-2-jack.zhu@starfivetech.com>
2023-03-03 8:34 ` [PATCH v1 01/11] media: dt-bindings: starfive,jh7110-camss: add binding document Krzysztof Kozlowski
2023-03-07 6:20 ` Jack Zhu
2023-03-03 8:35 ` Krzysztof Kozlowski
2023-03-07 6:35 ` Jack Zhu
[not found] ` <20230302091921.43309-5-jack.zhu@starfivetech.com>
2023-03-03 8:42 ` [PATCH v1 04/11] MAINTAINERS: add Starfive Camera subsystem driver Krzysztof Kozlowski
2023-03-09 2:52 ` Jack Zhu
[not found] ` <20230302091921.43309-12-jack.zhu@starfivetech.com>
2023-03-03 8:43 ` [PATCH v1 11/11] media: starfive: enable building Krzysztof Kozlowski
2023-03-07 9:46 ` Jack Zhu
2023-03-08 10:33 ` Krzysztof Kozlowski
2023-03-08 11:03 ` Jack Zhu
2023-03-08 11:07 ` Krzysztof Kozlowski
2023-03-09 2:13 ` Jack Zhu
[not found] ` <20230302091921.43309-11-jack.zhu@starfivetech.com>
2023-03-03 8:44 ` [PATCH v1 10/11] media: uapi: add user space interfaces Krzysztof Kozlowski
2023-03-09 2:22 ` Jack Zhu
[not found] ` <20230302091921.43309-7-jack.zhu@starfivetech.com>
2023-03-03 8:45 ` [PATCH v1 06/11] media: starfive: add ISP driver files Krzysztof Kozlowski
2023-03-07 9:53 ` Jack Zhu
2023-03-08 10:34 ` Krzysztof Kozlowski
2023-03-08 11:04 ` Jack Zhu
[not found] ` <20230302091921.43309-3-jack.zhu@starfivetech.com>
2023-03-03 8:42 ` Krzysztof Kozlowski [this message]
2023-03-03 8:47 ` [PATCH v1 02/11] media: dt-bindings: starfive,jh7110-mipi-csi2: add binding docmuent Krzysztof Kozlowski
2023-03-07 6:41 ` Jack Zhu
2023-03-07 7:53 ` Krzysztof Kozlowski
2023-03-07 10:08 ` Jack Zhu
2023-03-08 10:32 ` 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=711f0e08-a8c8-45ef-08cf-6ca4f166ed4a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=changhuang.liang@starfivetech.com \
--cc=devicetree@vger.kernel.org \
--cc=jack.zhu@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=todor.too@gmail.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®