linux-kernel - Re: [PATCH v5 1/3] dt-bindings: clk: tenstorrent: Add tenstorrent,atlantis-prcm

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: <e242a327-b53e-4b24-a9c1-9ae990de901e@kernel.org>
Date: Sat, 7 Feb 2026 10:37:02 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Anirudh Srinivasan <asrinivasan@....tenstorrent.com>
Cc: Drew Fustini <dfustini@....tenstorrent.com>,
 Joel Stanley <jms@....tenstorrent.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Michael Turquette <mturquette@...libre.com>,
 Stephen Boyd <sboyd@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
 linux-riscv@...ts.infradead.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org, joel@....id.au,
 fustini@...nel.org, mpe@...nel.org, mpe@....tenstorrent.com,
 npiggin@....tenstorrent.com, agross@...nel.org, agross@....tenstorrent.com,
 bmasney@...hat.com
Subject: Re: [PATCH v5 1/3] dt-bindings: clk: tenstorrent: Add
 tenstorrent,atlantis-prcm

On 07/02/2026 05:18, Anirudh Srinivasan wrote:
>>
>>> this version and I have mentioned this in the changelog in the cover
>>> letter) named "tenstorrent,atlantis-prcm-xyz". The bindings document
>>
>> Where did you mention it? I went TWICE through it.
> 
> Conor and I were discussing these in a previous series and were
> referring to them as rcpu prcm and !rcpu prcms. I use these terms to
> refer to it in "Changes in v4".

There is no way I could have guessed it. If you remove a compatible you
say "removed compatible" not "removed !rcpu".

> 
>>
>>> suggests picking a more generic name in this case, so isn't
>>> "tenstorrent,atlantis-prcm" okay for that?
>>
>> No, because I don't want to keep guessing this. The docs clearly ask you
>> to post complete bindings, which now became less-complete, but fine.
>> Then the next rule asks you to use compatible as filename. You cannot
>> keep skipping the rules.
> 
> I will add all the compatibles back, so there will be 4 of them named
> "tenstorrent,atlantis-prcm-xyz". In that case is it appropriate for
> the filename to be "tenstorrent,atlantis-prcm.yaml"?

Yes

Best regards,
Krzysztof