public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] schemas: Allow clocks: property in cache nodes
Date: Sun, 3 May 2026 19:09:26 +0100	[thread overview]
Message-ID: <20260503-vagabond-barge-dac8ececfc11@spud> (raw)
In-Reply-To: <20260503154439.27362-1-marek.vasut+renesas@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Sun, May 03, 2026 at 05:44:13PM +0200, Marek Vasut wrote:
> Renesas R-Mobile APE6 currently describes clock which supply the cache
> controller in their DT using "clocks" property. This is not the only
> hardware that has cache controller clock controllable via some sort of
> clock controller, for example Altera SoCFPGA Cyclone V and Arria V also
> has controllable cache controller clock. Allow clocks: property in cache
> controller node to allow users to fully describe such hardware.

Hmm, shouldn't these cache controllers have dedicated bindings that
enforce their clock requirements?

> 
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
> ---
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: linux-renesas-soc@vger.kernel.org
> ---
>  dtschema/schemas/cache.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/dtschema/schemas/cache.yaml b/dtschema/schemas/cache.yaml
> index 73d345f..dee1cd5 100644
> --- a/dtschema/schemas/cache.yaml
> +++ b/dtschema/schemas/cache.yaml
> @@ -33,6 +33,9 @@ properties:
>    compatible:
>      const: cache
>  
> +  clocks:
> +    maxItems: 1
> +
>    power-domains:
>      maxItems: 1
>  
> -- 
> 2.53.0
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-03 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 15:44 [PATCH] schemas: Allow clocks: property in cache nodes Marek Vasut
2026-05-03 18:09 ` Conor Dooley [this message]
2026-05-04  8:19   ` Geert Uytterhoeven

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=20260503-vagabond-barge-dac8ececfc11@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marek.vasut+renesas@mailbox.org \
    --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