From: Conor Dooley <conor@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@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>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"biju.das.au" <biju.das.au@gmail.com>
Subject: Re: [PATCH 03/19] dt-bindings: serial: renesas,rsci: Document RZ/G3E support
Date: Tue, 28 Oct 2025 19:51:49 +0000 [thread overview]
Message-ID: <20251028-veteran-smell-963bb76ab3ff@spud> (raw)
In-Reply-To: <TY3PR01MB11346372AB6D191D30B4F058B86FDA@TY3PR01MB11346.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Tue, Oct 28, 2025 at 07:41:33PM +0000, Biju Das wrote:
> > > + - if:
> > > + properties:
> > > + compatible:
> > > + contains:
> > > + enum:
> > > + - renesas,r9a09g047-rsci
> > > + - renesas,r9a09g047-rscif
> > > + then:
> > > + properties:
> > > + clocks:
> > > + minItems: 5
> > > +
> > > + clock-names:
> > > + minItems: 5
> > > +
> > > + required:
> > > + - resets
> > > + - reset-names
> >
> > Does this need an "else: properties: resets: false"? Or do other devices actually have resets too?
>
> It is not required as resets are optional for RZ/T2H and RZ/N2H. RZ/T2H and N2H does not have
> Resets.
This is a contradiction. Either they are optional for these platforms or
the platforms do not have resets. Cannot be both!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-10-28 19:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 15:45 [PATCH 00/19] Add RZ/G3E RSCI support Biju Das
2025-10-27 15:45 ` [PATCH 02/19] dt-bindings: serial: rsci: Drop "uart-has-rtscts: false" Biju Das
2025-10-28 19:28 ` Conor Dooley
2025-10-28 19:39 ` Biju Das
2025-10-28 19:50 ` Conor Dooley
2025-10-28 20:27 ` Biju Das
2025-10-27 15:45 ` [PATCH 03/19] dt-bindings: serial: renesas,rsci: Document RZ/G3E support Biju Das
2025-10-28 19:30 ` Conor Dooley
2025-10-28 19:41 ` Biju Das
2025-10-28 19:51 ` Conor Dooley [this message]
2025-10-28 20:26 ` Biju Das
2025-10-29 17:20 ` Conor Dooley
2025-10-27 15:45 ` [PATCH 04/19] serial: sh-sci: Fix deadlock during RSCI FIFO overrun error Biju Das
2025-10-28 8:40 ` Greg Kroah-Hartman
2025-10-28 9:08 ` Biju Das
2025-10-27 15:45 ` [PATCH 05/19] serial: rsci: Drop rsci_clear_CFC() Biju Das
2025-10-27 15:45 ` [PATCH 06/19] serial: sh-sci: Drop extra line Biju Das
2025-10-28 14:35 ` Hugo Villeneuve
2025-10-30 14:43 ` Biju Das
2025-10-27 15:45 ` [PATCH 07/19] serial: rsci: Drop unused macro DCR Biju Das
2025-10-27 15:45 ` [PATCH 08/19] serial: rsci: Drop unused TDR register Biju Das
2025-10-27 15:45 ` [PATCH 09/19] serial: sh-sci: Use devm_reset_control_array_get_exclusive() Biju Das
2025-10-27 15:45 ` [PATCH 10/19] serial: sh-sci: Add RSCI_PORT_{SCI,SCIF} port IDs Biju Das
2025-10-27 15:45 ` [PATCH 11/19] serial: sh-sci: Add sci_is_rsci_type() Biju Das
2025-10-27 15:45 ` [PATCH 12/19] serial: sh-sci: Add support for RZ/G3E RSCI clks Biju Das
2025-10-28 14:51 ` Hugo Villeneuve
2025-10-28 15:08 ` Biju Das
2025-10-28 15:37 ` Hugo Villeneuve
2025-10-27 15:46 ` [PATCH 13/19] serial: sh-sci: Make sci_scbrr_calc() public Biju Das
2025-10-27 15:46 ` [PATCH 14/19] serial: sh-sci: Add finish_console_write() callback Biju Das
2025-10-27 15:46 ` [PATCH 15/19] serial: sh-sci: Add support for RZ/G3E RSCI SCIF Biju Das
2025-10-28 15:22 ` Hugo Villeneuve
2025-10-27 15:46 ` [PATCH 16/19] serial: sh-sci: Add support for RZ/G3E RSCI SCI Biju Das
2025-10-28 8:41 ` [PATCH 00/19] Add RZ/G3E RSCI support Greg Kroah-Hartman
2025-10-28 9:12 ` Biju Das
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=20251028-veteran-smell-963bb76ab3ff@spud \
--to=conor@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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