From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: soc: renesas: Document R-Car X5H
Date: Thu, 28 Aug 2025 17:41:09 +0100 [thread overview]
Message-ID: <20250828-platform-counting-6578d06e3526@spud> (raw)
In-Reply-To: <20250828-esoteric-vivid-raccoon-a86c9a@kuoka>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
On Thu, Aug 28, 2025 at 09:27:19AM +0200, Krzysztof Kozlowski wrote:
> On Wed, Aug 27, 2025 at 11:34:09PM +0000, Kuninori Morimoto wrote:
> > Document the compatible values for the Renesas R-Car X5H (R8A78000) SoC
> >
> > Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> > ---
> > v1 -> v2
> > - add empty enum to avoid allowing invalid use.
>
> I don't understand why do you need this. Where is any user of it? There
> is no such in this patchset, so this must be explicitly explained in the
> commit msg.
>
> >
> > Documentation/devicetree/bindings/soc/renesas/renesas.yaml | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > index 5f9d541d177a..e2fec2afbc6d 100644
> > --- a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > +++ b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > @@ -473,6 +473,12 @@ properties:
> > - const: renesas,r8a779mb
> > - const: renesas,r8a7795
> >
> > + - description: R-Car X5H (R8A78000)
> > + items:
> > + - enum:
> > + - {} # avoid allowing invalid use. will be replaced to actual board name
>
> We don't allow such cases because it is pointless.
>
> Otherwise explain in the commit msg why this is needed, why exception is
> justified.
>
> You have entire commit msg to explain anything unusual and if you look
> at source code you will not notice such syntax for boards, so clearly
> this is unusual.
They have a soc driver that binds to the compatible, which is why I
suggested this rather than refusing the patch. I do agree it should be
mentioned though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-28 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 23:34 [PATCH v2] dt-bindings: soc: renesas: Document R-Car X5H Kuninori Morimoto
2025-08-28 7:27 ` Krzysztof Kozlowski
2025-08-28 16:41 ` Conor Dooley [this message]
2025-09-01 0:06 ` Kuninori Morimoto
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=20250828-platform-counting-6578d06e3526@spud \
--to=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.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).