linux-kernel - RE: [PATCH v5 01/17] dt-bindings: serial: renesas,rsci: Document RZ/G3E support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <TY3PR01MB11346C9A7B587AF03D533AC9E86D9A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
Date: Wed, 3 Dec 2025 08:13:13 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: "Rob Herring (Arm)" <robh@...nel.org>, biju.das.au <biju.das.au@...il.com>
CC: magnus.damm <magnus.damm@...il.com>, Jiri Slaby <jirislaby@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Greg Kroah-Hartman
	<gregkh@...uxfoundation.org>, Geert Uytterhoeven <geert+renesas@...der.be>,
	wsa+renesas <wsa+renesas@...g-engineering.com>,
	"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Conor Dooley
	<conor+dt@...nel.org>, Prabhakar Mahadev Lad
	<prabhakar.mahadev-lad.rj@...renesas.com>
Subject: RE: [PATCH v5 01/17] dt-bindings: serial: renesas,rsci: Document
 RZ/G3E support

Hi Rob,

> -----Original Message-----
> From: Rob Herring (Arm) <robh@...nel.org>
> Sent: 29 November 2025 17:23
> Subject: Re: [PATCH v5 01/17] dt-bindings: serial: renesas,rsci: Document RZ/G3E support
> 
> 
> On Sat, 29 Nov 2025 16:42:57 +0000, Biju wrote:
> > From: Biju Das <biju.das.jz@...renesas.com>
> >
> > Add documentation for the serial communication interface (RSCI) found
> > on the Renesas RZ/G3E (R9A09G047) SoC. The RSCI IP on this SoC is
> > identical to that on the RZ/T2H (R9A09G077) SoC, but it has a 32-stage
> > FIFO compared to 16 on RZ/T2H. It supports both FIFO and non-FIFO mode
> > operation. RZ/G3E has 6 clocks(5 module clocks + 1 external clock)
> > compared to 3 clocks
> > (2 module clocks + 1 external clock) on RZ/T2H, and it has multiple resets.
> > It has 6 interrupts compared to 4 on RZ/T2H.
> >
> > Signed-off-by: Biju Das <biju.das.jz@...renesas.com>
> > ---
> > v4->v5:
> >  * Updated commit description related to IRQ difference
> >  * Added aed and bfd irqs for RZ/G3E.
> >  * Moved reset: false to RZ/T2H SoC and dropped the else part for RZ/G3E.
> >  * Updated conditional schema with interrupts and interrupts-names.
> >  * Dropped the tag as there are new changes.
> > v3->v4:
> >  * Dropped separate compatible for non-FIFO mode and instead using single
> >    compatible "renesas,r9a09g047-rsci" as non-FIFO mode can be achieved
> >    by software configuration.
> >  * Renamed clock-names bus->pclk
> >  * Rearranged clock-names tclk{4, 16, 64}
> >  * Retained the tag as the changes are trivial.
> > v2->v3:
> >  * Dropped 1st and 3rd items from clk-names and added minItems for the
> >    range.
> >  * Added minItems for clk and clk-names for RZ/T2H as the range is 2-3
> >  * Added maxItems for clk and clk-names for RZ/G3E as the range is 5-6
> >  * Retained the tag as it is trivial change.
> > v1->v2:
> >  * Updated commit message
> >  * Added resets:false for non RZ/G3E SoCs.
> > ---
> >  .../bindings/serial/renesas,rsci.yaml         | 99 ++++++++++++++++---
> >  1 file changed, 88 insertions(+), 11 deletions(-)
> >
> 
> My bot found errors running 'make dt_binding_check' on your patch:
> 
> yamllint warnings/errors:
> 
> dtschema/dtc warnings/errors:
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-
> sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-
> sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-
> sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-zones.example.dtb: /example-0/soc/thermal-
> sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-
> sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-
> sensor@...3000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-
> sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> Documentation/devicetree/bindings/thermal/thermal-sensor.example.dtb: /example-0/soc/thermal-
> sensor@...5000: failed to match any schema with compatible: ['qcom,sdm845-tsens', 'qcom,tsens-v2']
> 

Can you please check, bot is showing unrelated errors?

Cheers,
Biju