devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kanak Shilledar <kanakshilledar@gmail.com>
Cc: krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, daniel.baluta@nxp.com,
	Kanak Shilledar <kanakshilledar111@protonmail.com>
Subject: Re: [PATCH v3] dt-bindings: serial: actions,owl-uart: convert to dtschema
Date: Tue, 26 Mar 2024 12:34:46 +0100	[thread overview]
Message-ID: <5959c75f-42e0-40c2-a5f5-2725e35912f5@linaro.org> (raw)
In-Reply-To: <20240326110506.78408-1-kanakshilledar@gmail.com>

On 26/03/2024 12:05, Kanak Shilledar wrote:
> From: Kanak Shilledar <kanakshilledar111@protonmail.com>
> 
> Convert the Actions Semi Owl UART to newer DT schema.
> Created DT schema based on the .txt file which had
> `compatible`, `reg`, `clocks` and `interrupts` as the

That's not true. Old binding file did not have clocks. You did more than
conversion and I asked you to describe changes which are different than
pure conversion.

Instead of sending another version the same day, can you please read
carefully comments you receive?

> required properties. This binding is used by Actions S500, S700
> and S900 SoC. S700 and S900 use the same UART compatible string.
> Implemented a full node example for the UART, referenced S500 SoC
> devicetree include.
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Drop, you made MANY MORE changes than I asked, up to the point of making
it broken.

I don't understand. I asked three things. One you ignored, two
implemented and then added more.

> Signed-off-by: Kanak Shilledar <kanakshilledar111@protonmail.com>
> ---


...


> +  interrupts:
> +    maxItems: 1
> +
> +  clocks:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - clocks

That's surprising. Nothing in the changelog explains this.

> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/clock/actions,s500-cmu.h>
> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> +    uart0: serial@b0126000 {
> +        compatible = "actions,s500-uart", "actions,owl-uart";
> +        reg = <0xb0126000 0x1000>;
> +        clocks = <&cmu CLK_UART0>;
> +        interrupts = <GIC_SPI 32 IRQ_TYPE_LEVEL_HIGH>;
> +        status = "disabled";

NAK.

Examples are not disabled.

Best regards,
Krzysztof


  reply	other threads:[~2024-03-26 11:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21  8:43 [PATCH] dt-bindings: serial: actions,owl-uart: convert to dtschema Kanak Shilledar
2024-03-21  9:22 ` Krzysztof Kozlowski
2024-03-21  9:33   ` Conor Dooley
2024-03-26  8:58 ` [PATCH v2] " Kanak Shilledar
2024-03-26  9:15   ` Krzysztof Kozlowski
2024-03-26 11:05     ` [PATCH v3] " Kanak Shilledar
2024-03-26 11:34       ` Krzysztof Kozlowski [this message]
2024-03-26 11:31     ` [PATCH v2] " 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=5959c75f-42e0-40c2-a5f5-2725e35912f5@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kanakshilledar111@protonmail.com \
    --cc=kanakshilledar@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --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).