devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wsa+renesas <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"magnus.damm" <magnus.damm@gmail.com>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] dt-bindings: watchdog: factor out RZ/V2H(P) watchdog
Date: Mon, 6 Oct 2025 11:43:12 +0200	[thread overview]
Message-ID: <aOOPMG_bW_q8iM7C@shikoro> (raw)
In-Reply-To: <CAMuHMdVUbENsdjCCqrn7e9=mWbs+J1kcat6LYU6vAcrBHzawBw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

Hi Geert,

> We do have "fallback" comments in other places, and I think they do
> help in understanding compatible naming schemes.

Still, dunno...

> Would it be possible to handle this in dt-schema?
> Currently we have to write:
> 
>       - const: vendor,soc1-ip
> 
>       - items:
>           - enum:
>               - vendor,soc2-ip
>               - vendor,soc3-ip
>           - const: vendor,soc1-ip       # fallback

... I think '- items' makes it clear that later entries are fallback
entries. I am by no means a YAML master but this knowledge should/could
be expected? If peolpe don't know that...

What really is confusing, I'd say, is a mixture of entries with
fallbacks and without. One can overlook this easily. So, they should be
grouped IMHO. That's my previous suggestion.

> If dt-schema would automatically drop duplicates of the fallback,
> we could just write:
> 
>       - items:
>           - enum:
>               - vendor,soc1-ip
>               - vendor,soc2-ip
>               - vendor,soc3-ip
>           - const: vendor,soc1-ip       # fallback
> 
> What do you think?

(soc1 should be omitted from the enum)

Do you mean "# fallback" indicates that the fallback entry should be
created? Or just the const item?

Well, this is ultimately DT maintainers call, but my gut feeling says it
is better to be explicit than implicit. I do understand that the more
compact binding documentation would be a gain, though.

All the best,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-10-06  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 14:44 [PATCH v2 0/4] dt-bindings: watchdog: factor out RZ watchdogs Wolfram Sang
2025-10-05 14:44 ` [PATCH v2 1/4] dt-bindings: watchdog: factor out RZ/A watchdog Wolfram Sang
2025-10-05 14:44 ` [PATCH v2 2/4] dt-bindings: watchdog: factor out RZ/N1 watchdog Wolfram Sang
2025-10-05 14:44 ` [PATCH v2 3/4] dt-bindings: watchdog: factor out RZ/G2L watchdog Wolfram Sang
2025-10-05 16:04   ` Biju Das
2025-10-05 14:44 ` [PATCH v2 4/4] dt-bindings: watchdog: factor out RZ/V2H(P) watchdog Wolfram Sang
2025-10-05 16:07   ` Biju Das
2025-10-05 16:11     ` Biju Das
2025-10-05 16:19     ` wsa+renesas
2025-10-06  3:17       ` Biju Das
2025-10-06  6:30         ` wsa+renesas
2025-10-06  9:25           ` Geert Uytterhoeven
2025-10-06  9:43             ` wsa+renesas [this message]
2025-10-06  9:54               ` Geert Uytterhoeven
2025-10-09 20:00             ` Rob Herring
2025-10-06  8:39   ` Wolfram Sang

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=aOOPMG_bW_q8iM7C@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh@kernel.org \
    --cc=wim@linux-watchdog.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).