public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Anirudh Srinivasan <asrinivasan@oss.tenstorrent.com>
Cc: Drew Fustini <dfustini@oss.tenstorrent.com>,
	Joel Stanley <jms@oss.tenstorrent.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	joel@jms.id.au, fustini@kernel.org, mpe@kernel.org,
	mpe@oss.tenstorrent.com, npiggin@oss.tenstorrent.com,
	agross@kernel.org, agross@oss.tenstorrent.com,
	bmasney@redhat.com
Subject: Re: [PATCH v5 1/3] dt-bindings: clk: tenstorrent: Add tenstorrent,atlantis-prcm
Date: Sat, 7 Feb 2026 10:37:02 +0100	[thread overview]
Message-ID: <e242a327-b53e-4b24-a9c1-9ae990de901e@kernel.org> (raw)
In-Reply-To: <CAEev2e99LEoi83_d09NEJwzcSiYdFFZvLOFZUTRRrYtL_qCErw@mail.gmail.com>

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

  reply	other threads:[~2026-02-07  9:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 19:46 [PATCH v5 0/3] Add Tenstorrent Atlantis Clock/Reset Controller Anirudh Srinivasan
2026-02-02 19:46 ` [PATCH v5 1/3] dt-bindings: clk: tenstorrent: Add tenstorrent,atlantis-prcm Anirudh Srinivasan
2026-02-05  9:23   ` Krzysztof Kozlowski
2026-02-05 14:31     ` Anirudh Srinivasan
2026-02-05 18:45       ` Krzysztof Kozlowski
2026-02-07  4:18         ` Anirudh Srinivasan
2026-02-07  9:37           ` Krzysztof Kozlowski [this message]
2026-02-07 14:54             ` Conor Dooley
2026-02-07 18:39               ` Krzysztof Kozlowski
2026-02-08 21:39                 ` Anirudh Srinivasan
2026-02-09 18:54                   ` Conor Dooley
2026-02-02 19:46 ` [PATCH v5 2/3] reset: tenstorrent: Add reset controller for Atlantis Anirudh Srinivasan
2026-02-05  9:27   ` Krzysztof Kozlowski
2026-02-05 14:18     ` Anirudh Srinivasan
2026-02-05 18:47       ` Krzysztof Kozlowski
2026-02-07  4:10         ` Anirudh Srinivasan
2026-02-02 19:46 ` [PATCH v5 3/3] clk: tenstorrent: Add Atlantis clock controller driver Anirudh Srinivasan
2026-02-05  9:25   ` Krzysztof Kozlowski

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=e242a327-b53e-4b24-a9c1-9ae990de901e@kernel.org \
    --to=krzk@kernel.org \
    --cc=agross@kernel.org \
    --cc=agross@oss.tenstorrent.com \
    --cc=asrinivasan@oss.tenstorrent.com \
    --cc=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dfustini@oss.tenstorrent.com \
    --cc=fustini@kernel.org \
    --cc=jms@oss.tenstorrent.com \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mpe@kernel.org \
    --cc=mpe@oss.tenstorrent.com \
    --cc=mturquette@baylibre.com \
    --cc=npiggin@oss.tenstorrent.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sboyd@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