From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.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>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: bus: renesas-bsc: allow additional properties
Date: Wed, 8 Oct 2025 12:02:29 +0200 [thread overview]
Message-ID: <aOY2tdEXmhdZ0Yeq@shikoro> (raw)
In-Reply-To: <CAMuHMdUXoq3d010y0vyXvvaHpgaV7rHb66VAHrwJxAZXzt+z=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
> > As said, I copied this from 'bus/allwinner,sun50i-a64-de2.yaml', so this
> > got reviewed already. I have no strong opinions on your suggestions
> > above. But whatever we agree on, it should be reused for all busses, I'd
> > say. So, we should put it where it can be referenced?
>
> In my defense, this is a DT bindings file for Renesas BSC, so we can
> (and IMHO should) add restrictions.
>
> If you want to go the fully generic way: as per the device tree
> specification, a unit-address can take all characters from the same
> set as a node name...
Well, I think consistency makes sense, but I don't even have a strong
opinion on that. If DT maintainers are fine with having multiple
patternProperties for busses, I will include the restriction you
suggested.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-08 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 3:18 [PATCH] dt-bindings: bus: renesas-bsc: allow additional properties Wolfram Sang
2025-10-07 8:44 ` Geert Uytterhoeven
2025-10-07 21:30 ` Wolfram Sang
2025-10-08 9:56 ` Geert Uytterhoeven
2025-10-08 10:02 ` Wolfram Sang [this message]
2025-10-08 22:42 ` Rob Herring
2025-10-09 6:43 ` Wolfram Sang
2025-10-09 12:41 ` Rob Herring
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=aOY2tdEXmhdZ0Yeq@shikoro \
--to=wsa+renesas@sang-engineering.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=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;
as well as URLs for NNTP newsgroup(s).