linux-kernel - Re: [PATCH 05/12] dt-bindings: rtc: renesas,rzg3s-rtc: Document the Renesas RZ/G3S RTC

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20240615-unwell-hardcover-e95af7c4a43b@spud>
Date: Sat, 15 Jun 2024 13:16:26 +0100
From: Conor Dooley <conor@...nel.org>
To: Biju Das <biju.das.jz@...renesas.com>
Cc: "Claudiu.Beznea" <claudiu.beznea@...on.dev>,
	"geert+renesas@...der.be" <geert+renesas@...der.be>,
	"mturquette@...libre.com" <mturquette@...libre.com>,
	"sboyd@...nel.org" <sboyd@...nel.org>,
	"robh@...nel.org" <robh@...nel.org>,
	"krzk+dt@...nel.org" <krzk+dt@...nel.org>,
	"conor+dt@...nel.org" <conor+dt@...nel.org>,
	"lee@...nel.org" <lee@...nel.org>,
	"alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>,
	"magnus.damm@...il.com" <magnus.damm@...il.com>,
	"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
	"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-rtc@...r.kernel.org" <linux-rtc@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>,
	Claudiu Beznea <claudiu.beznea.uj@...renesas.com>
Subject: Re: [PATCH 05/12] dt-bindings: rtc: renesas,rzg3s-rtc: Document the
 Renesas RZ/G3S RTC

On Fri, Jun 14, 2024 at 08:22:57AM +0000, Biju Das wrote:

> > >> +$id: http://devicetree.org/schemas/rtc/renesas,rzg3s-rtc.yaml#
> > >
> > > Please make it generic renesas,rtca3-rtc.yaml. Future SoCs may use this IP.
> > > So use IP name instead.
> > 
> > From what I know the file name should correspond with the compatible that file was introduced with,
> > and this one shouldn't be generic but SoC specific.
> 
> I maybe wrong, I was under the impression, we should use "vendor,ipname" for the filename
> and compatible should use vendor,ipname as generic compatible.
> If there are differences between SoCs, then use SoC specific compatible.
> 
> Currently there is one device, so not sure??

The usual policy for new files is "filename matching a compatible".

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)