devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: keke.li@amlogic.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kieran.bingham@ideasonboard.com,
	laurent.pinchart@ideasonboard.com, dan.scally@ideasonboard.com
Subject: Re: [PATCH 1/9] dt-bindings: media: Add amlogic,c3-mipi-csi2.yaml
Date: Tue, 3 Sep 2024 16:08:15 +0200	[thread overview]
Message-ID: <d3672523-11fe-42de-ad7b-643b396b8778@kernel.org> (raw)
In-Reply-To: <20240903-c3isp-v1-1-8af0edcc13c8@amlogic.com>

On 03/09/2024 08:57, Keke Li via B4 Relay wrote:
> From: Keke Li <keke.li@amlogic.com>
> 
> c3-mipi-csi2 is used to receive mipi data
> from image sensor.

Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597

> 
> Signed-off-by: Keke Li <keke.li@amlogic.com>
> ---
>  .../bindings/media/amlogic,c3-mipi-csi2.yaml       | 130 +++++++++++++++++++++
>  1 file changed, 130 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml
> new file mode 100644
> index 000000000000..85d3088d6f9f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml
> @@ -0,0 +1,130 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/amlogic,c3-mipi-csi2.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Amlogic C3 MIPI CSI-2 receiver
> +
> +maintainers:
> +  - Keke Li <keke.li@amlogic.com>
> +
> +description: |-

Do not need '|-' unless you need to preserve formatting.


> +  MIPI CSI-2 receiver contains CSI-2 RX PHY and host controller.
> +  It receives the MIPI data from the image sensor and sends MIPI data
> +  to MIPI adapter.
> +
> +properties:
> +  compatible:
> +    enum:
> +      - amlogic,c3-mipi-csi2
> +
> +  reg:
> +    minItems: 3

Drop minItems

> +    maxItems: 3
> +
> +  reg-names:
> +    items:
> +      - const: csi_aphy
> +      - const: csi_dphy
> +      - const: csi_host

Drop csi_ everywhere

> +
> +  power-domains:
> +    maxItems: 1
> +
> +  clocks:
> +    minItems: 2

Your code is random... Look how this is different than other list - reg.
Instead maxItems.

> +
> +  clock-names:
> +    items:
> +      - const: vapb
> +      - const: csi_phy0
> +
> +  ports:
> +    $ref: /schemas/graph.yaml#/properties/ports
> +
> +    properties:
> +      port@0:
> +        $ref: /schemas/graph.yaml#/$defs/port-base
> +        unevaluatedProperties: false
> +        description: input port node, connected to sensor.
> +
> +        properties:
> +          endpoint:
> +            $ref: video-interfaces.yaml#
> +            unevaluatedProperties: false
> +
> +            properties:
> +              data-lanes:
> +                minItems: 1
> +                maxItems: 4
> +
> +            required:
> +              - data-lanes
> +
> +      port@1:
> +        $ref: /schemas/graph.yaml#/properties/port
> +        description: output port node
> +
> +    required:
> +      - port@0
> +      - port@1
> +
> +required:
> +  - compatible
> +  - reg
> +  - reg-names
> +  - power-domains
> +  - clocks
> +  - clock-names
> +  - ports
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/clock/amlogic,c3-peripherals-clkc.h>
> +    #include <dt-bindings/power/amlogic,c3-pwrc.h>
> +
> +    soc {
> +        #address-cells = <2>;
> +        #size-cells = <2>;
> +
> +        csi: csi@ff018000 {
> +            compatible = "amlogic,c3-mipi-csi2";
> +

Drop blank line

> +            reg = <0x0 0xff018000 0x0 0x400>,
> +                  <0x0 0xff019000 0x0 0x300>,
> +                  <0x0 0xff01a000 0x0 0x100>;
> +

Drop blank line


> +            reg-names = "csi_aphy", "csi_dphy", "csi_host";
> +
> +            power-domains = <&pwrc PWRC_C3_MIPI_ISP_WRAP_ID>;
> +
> +            clocks =  <&clkc_periphs CLKID_VAPB>,
> +                      <&clkc_periphs CLKID_CSI_PHY0>;
> +

Drop blank line. That's poorly readable code.



Best regards,
Krzysztof


  reply	other threads:[~2024-09-03 14:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  6:57 [PATCH 0/9] Amlogic C3 ISP support Keke Li via B4 Relay
2024-09-03  6:57 ` [PATCH 1/9] dt-bindings: media: Add amlogic,c3-mipi-csi2.yaml Keke Li via B4 Relay
2024-09-03 14:08   ` Krzysztof Kozlowski [this message]
2024-09-04  8:15     ` Keke Li
2024-09-03  6:57 ` [PATCH 2/9] media: platform: Add c3 mipi csi2 driver Keke Li via B4 Relay
2024-09-03 14:10   ` Krzysztof Kozlowski
2024-09-04  8:53     ` Keke Li
2024-09-03  6:57 ` [PATCH 3/9] dt-bindings: media: Add amlogic,c3-mipi-adapter.yaml Keke Li via B4 Relay
2024-09-03 14:11   ` Krzysztof Kozlowski
2024-09-04  9:07     ` Keke Li
2024-09-03  6:57 ` [PATCH 4/9] media: platform: Add c3 mipi adapter driver Keke Li via B4 Relay
2024-09-03 14:12   ` Krzysztof Kozlowski
2024-09-04  9:16     ` Keke Li
2024-09-03  6:57 ` [PATCH 5/9] dt-bindings: media: Add amlogic,c3-isp.yaml Keke Li via B4 Relay
2024-09-03 14:11   ` Krzysztof Kozlowski
2024-09-04  9:21     ` Keke Li
2024-09-03  6:57 ` [PATCH 6/9] media: Add C3ISP_PARAMS and C3ISP_STATS meta formats Keke Li via B4 Relay
2024-09-10 16:59   ` Dan Scally
2024-09-03  6:57 ` [PATCH 7/9] media: platform: Add c3 ISP driver Keke Li via B4 Relay
2024-09-03  6:57 ` [PATCH 8/9] Documentation: media: add documentation file metafmt-c3-isp.rst Keke Li via B4 Relay
2024-09-03  6:57 ` [PATCH 9/9] Documentation: media: add documentation file c3-isp.rst Keke Li via B4 Relay

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=d3672523-11fe-42de-ad7b-643b396b8778@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=keke.li@amlogic.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@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).