public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
	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,
	Masato Kiuchi <kiuchi_masato@yuridenki.co.jp>
Subject: Re: [PATCH 3/4] dt-bindings: soc: renesas: Document Yuridenki-Shokai Kakip board
Date: Sat, 11 Jan 2025 10:32:28 +0100	[thread overview]
Message-ID: <5867f54d-9ef2-4b8c-85b4-d79fd846a4c4@kernel.org> (raw)
In-Reply-To: <20250111080903.3566296-4-iwamatsu@nigauri.org>

On 11/01/2025 09:09, Nobuhiro Iwamatsu wrote:
> Add "yuridenki,kakip" which targets the Yuridenki-Shokai Kakip board.
> 
> Signed-off-by: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
> ---
>  Documentation/devicetree/bindings/soc/renesas/renesas.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> index 4f2645e8140c5c..294ac7c7ae8a5d 100644
> --- a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> +++ b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> @@ -548,6 +548,7 @@ properties:
>          items:
>            - enum:
>                - renesas,rzv2h-evk # RZ/V2H EVK
> +              - yuridenki,kakip # Yuridenki-Shokai RZ/V2H Kakip board

I know Renesas has here a bit unusual patterns, but this is even more
unusual. Why do you claim kakip goes with absolutely any of below SoCs?
I understand your motherboards doing this, but not the final product.

>            - enum:
>                - renesas,r9a09g057h41 # RZ/V2H
>                - renesas,r9a09g057h42 # RZ/V2H with Mali-G31 support


Best regards,
Krzysztof

  reply	other threads:[~2025-01-11  9:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  8:08 [PATCH 0/4] Add support Yuridenki-Shokai Kakip board Nobuhiro Iwamatsu
2025-01-11  8:09 ` [PATCH 1/4] dt-bindings: soc: renesas: Document Renesas RZ/V2H SoC variants Nobuhiro Iwamatsu
2025-01-11  9:31   ` Krzysztof Kozlowski
2025-01-11  8:09 ` [PATCH 2/4] dt-bindings: vendor-prefixes: Add Yuridenki-Shokai Co. Ltd Nobuhiro Iwamatsu
2025-01-11  9:31   ` Krzysztof Kozlowski
2025-01-11  8:09 ` [PATCH 3/4] dt-bindings: soc: renesas: Document Yuridenki-Shokai Kakip board Nobuhiro Iwamatsu
2025-01-11  9:32   ` Krzysztof Kozlowski [this message]
2025-01-14 13:31     ` Nobuhiro Iwamatsu
2025-01-11  8:09 ` [PATCH 4/4] arm64: dts: renesas: Add initial device tree for " Nobuhiro Iwamatsu
2025-01-11  9:34   ` Krzysztof Kozlowski
2025-01-14 13:34     ` Nobuhiro Iwamatsu
2025-01-14 13:44     ` Geert Uytterhoeven
2025-01-15  8:36       ` Krzysztof Kozlowski
2025-01-16 14:24       ` Nobuhiro Iwamatsu
2025-01-13  9:41 ` [PATCH 0/4] Add support " Geert Uytterhoeven
2025-01-14 13:45   ` Nobuhiro Iwamatsu

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=5867f54d-9ef2-4b8c-85b4-d79fd846a4c4@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=iwamatsu@nigauri.org \
    --cc=kiuchi_masato@yuridenki.co.jp \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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