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: Tue, 7 Oct 2025 23:30:02 +0200 [thread overview]
Message-ID: <aOWGWkQn1AK22tJB@shikoro> (raw)
In-Reply-To: <CAMuHMdUChRoJ-A4W-PBBQssMvsn1GZY5zXmWxJ9y+EA8M2p3gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Hi Geert,
> > +patternProperties:
> > + # All other properties should be child nodes with unit-address and 'reg'
> > + "^[a-zA-Z][a-zA-Z0-9,+\\-._]{0,63}@[0-9a-fA-F]+$":
>
> I take it the "\\-" means escaped dash, to avoid it being interpreted
> as a range? I usually put the dash at the end, so it needs no escaping,
> but I am not sure that would work in yaml.
>
> I would drop the "A-F", as upper-case hex in unit addresses is very
> rare, and non-existent in *upstream) Renesas DTS files.
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?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-07 21:30 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 [this message]
2025-10-08 9:56 ` Geert Uytterhoeven
2025-10-08 10:02 ` Wolfram Sang
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=aOWGWkQn1AK22tJB@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