From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>,
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-i3c@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC 3/7] dt-bindings: i3c: renesas,i3c: Add binding for Renesas I3C controller
Date: Mon, 30 Jun 2025 21:43:18 +0200 [thread overview]
Message-ID: <aGLo1mlrHT_IZHQv@shikoro> (raw)
In-Reply-To: <20250625200709.GA2125481-robh@kernel.org>
> > + interrupt-names:
> > + items:
> > + - const: ierr
> > + - const: terr
> > + - const: abort
> > + - const: resp
> > + - const: cmd
> > + - const: ibi
> > + - const: rx
> > + - const: tx
> > + - const: rcv
> > + - const: st
> > + - const: sp
> > + - const: tend
> > + - const: nack
> > + - const: al
> > + - const: tmo
> > + - const: wu
> > + - const: exit
> > + minItems: 16
> > +
> > + clocks:
> > + oneOf:
> > + - items:
> > + - description: APB bus clock
> > + - description: transfer clock
> > + - items:
> > + - description: APB bus clock
> > + - description: SFRs clock
> > + - description: transfer clock
>
> It's a new binding, why don't you put SFRs clock last and simplify the
> schema?
Similar how we handle interrupts? 16 for the one SoC, 17 for the other?
Putting the optional entry to the end of the array? Tommaso, can you
integrate this change, please?
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2025-06-30 19:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 9:39 [PATCH RFC 0/7] i3c: add driver for the Renesas IP and support RZ/G3S+G3E Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 3/7] dt-bindings: i3c: renesas,i3c: Add binding for Renesas I3C controller Wolfram Sang
2025-06-11 15:40 ` Frank Li
2025-06-12 14:31 ` Wolfram Sang
2025-06-12 14:51 ` Tommaso Merciai
2025-06-12 15:35 ` Frank Li
2025-06-25 20:04 ` Rob Herring
2025-06-26 1:37 ` Frank Li
2025-06-25 20:07 ` Rob Herring
2025-06-30 19:43 ` Wolfram Sang [this message]
2025-07-01 9:09 ` Tommaso Merciai
2025-07-03 7:18 ` Wolfram Sang
2025-06-11 9:39 ` [PATCH RFC 4/7] i3c: add driver for Renesas I3C IP Wolfram Sang
2025-06-11 16:37 ` Frank Li
2025-06-12 14:55 ` Wolfram Sang
2025-06-12 16:42 ` Frank Li
2025-06-13 9:42 ` Wolfram Sang
2025-06-13 12:23 ` Geert Uytterhoeven
2025-06-13 13:10 ` Wolfram Sang
2025-06-17 7:12 ` Geert Uytterhoeven
2025-06-17 11:22 ` Wolfram Sang
2025-06-25 10:00 ` Wolfram Sang
2025-06-24 20:34 ` Wolfram Sang
2025-06-13 14:41 ` Frank Li
2025-06-17 9:42 ` Wolfram Sang
2025-07-24 8:58 ` Wolfram Sang
2025-06-11 13:11 ` [PATCH RFC 0/7] i3c: add driver for the Renesas IP and support RZ/G3S+G3E Rob Herring (Arm)
2025-06-11 18:56 ` 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=aGLo1mlrHT_IZHQv@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh@kernel.org \
--cc=tommaso.merciai.xr@bp.renesas.com \
/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).