From: Krzysztof Kozlowski <krzk@kernel.org>
To: Prabhakar <prabhakar.csengg@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v4 1/9] dt-bindings: soc: renesas: Document RZ/V2H EVK board
Date: Wed, 28 Aug 2024 16:34:23 +0200 [thread overview]
Message-ID: <28106585-59d1-42c4-af56-89820b15bdfb@kernel.org> (raw)
In-Reply-To: <20240828124134.188864-2-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 28/08/2024 14:41, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> Add "renesas,rzv2h-evk" which targets the Renesas RZ/V2H ("R9A09G057")
> EVK board.
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> ---
> Hi Rob, I have restored your Ack with the below change, I hope that's OK.
>
> Cheers, Prabhakar
>
> v1->v4
> - Updated 'renesas,gp-evk # GP-EVK' -> 'renesas,rzv2h-evk # RZ/V2H EVK'
> - Updated commit message
>
> v1: https://patchwork.kernel.org/project/linux-renesas-soc/patch/20240724094707.569596-2-prabhakar.mahadev-lad.rj@bp.renesas.com/
> ---
> Documentation/devicetree/bindings/soc/renesas/renesas.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> index d582992aaf0e..b7acb65bdecd 100644
> --- a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> +++ b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> @@ -527,6 +527,8 @@ properties:
>
> - description: RZ/V2H(P) (R9A09G057)
> items:
> + - enum:
> + - renesas,rzv2h-evk # RZ/V2H EVK
> - enum:
This is unusual pattern for me, but maybe I miss here something. Commit
message does not explain why EXISTING boards needs to be changed. What
does it mean "rzv2h-evk targets evk board"? How does this work?
You have EVK board and now it is not valid anymore?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-28 14:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 12:41 [PATCH v4 0/9] Add support for Renesas RZ/V2H(P) SoC and RZV2H-EVK platform Prabhakar
2024-08-28 12:41 ` [PATCH v4 1/9] dt-bindings: soc: renesas: Document RZ/V2H EVK board Prabhakar
2024-08-28 14:34 ` Krzysztof Kozlowski [this message]
2024-08-28 20:09 ` Lad, Prabhakar
2024-08-29 5:59 ` Krzysztof Kozlowski
2024-08-29 7:35 ` Geert Uytterhoeven
2024-08-30 10:04 ` Krzysztof Kozlowski
2024-08-29 10:09 ` Geert Uytterhoeven
2024-08-30 10:04 ` Krzysztof Kozlowski
2024-08-28 12:41 ` [PATCH v4 2/9] arm64: dts: renesas: Add initial SoC DTSI for RZ/V2H(P) SoC Prabhakar
2024-08-29 10:21 ` Geert Uytterhoeven
2024-08-28 12:41 ` [PATCH v4 3/9] arm64: dts: renesas: Add initial DTS for RZ/V2H EVK board Prabhakar
2024-08-29 10:22 ` Geert Uytterhoeven
2024-08-28 12:41 ` [PATCH v4 4/9] arm64: dts: renesas: r9a09g057: Add OSTM0-OSTM7 nodes Prabhakar
2024-08-29 10:23 ` Geert Uytterhoeven
2024-08-28 12:41 ` [PATCH v4 5/9] arm64: dts: renesas: r9a09g057: Add RIIC0-RIIC8 nodes Prabhakar
2024-08-29 10:24 ` Geert Uytterhoeven
2024-08-29 19:40 ` Lad, Prabhakar
2024-08-28 12:41 ` [PATCH v4 6/9] arm64: dts: renesas: r9a09g057: Add SDHI0-SDHI2 nodes Prabhakar
2024-08-29 10:26 ` Geert Uytterhoeven
2024-08-28 12:41 ` [PATCH v4 7/9] arm64: dts: renesas: r9a09g057: Add WDT0-WDT3 nodes Prabhakar
2024-08-29 10:26 ` Geert Uytterhoeven
2024-08-28 12:41 ` [PATCH v4 8/9] arm64: dts: renesas: r9a09g057h44-rzv2h-evk: Enable OSTM, I2C, and SDHI Prabhakar
2024-08-29 10:27 ` Geert Uytterhoeven
2024-08-28 12:41 ` [PATCH v4 9/9] arm64: dts: renesas: r9a09g057h44-rzv2h-evk: Enable watchdog Prabhakar
2024-08-29 10:28 ` Geert Uytterhoeven
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=28106585-59d1-42c4-af56-89820b15bdfb@kernel.org \
--to=krzk@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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
all inboxes | Powered by JetHome®