All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <ben.dooks@sifive.com>, <palmer@dabbelt.com>,
	<paul.walmsley@sifive.com>, <aou@eecs.berkeley.edu>,
	<greentime.hu@sifive.com>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <devicetree@vger.kernel.org>
Subject: Re: [RESEND PATCH] dt-bindings: sifive-ccache: fix cache level for l3 cache
Date: Tue, 30 Aug 2022 12:56:34 +0000	[thread overview]
Message-ID: <b810d354-18f3-9ae0-6310-57d9e36f4f9b@microchip.com> (raw)
In-Reply-To: <20220830125133.1698781-1-ben.dooks@sifive.com>

On 30/08/2022 13:51, Ben Dooks wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> With newer cores such as the p550, the SiFive composable cache can be
> a level 3 cache. Update the cache level to be one of 2 or 3.
> 
> Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
> ---
>   Documentation/devicetree/bindings/riscv/sifive-ccache.yaml | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml b/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml
> index 1a64a5384e36..6190deb65455 100644
> --- a/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml
> +++ b/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml
> @@ -45,7 +45,7 @@ properties:
>       const: 64
> 
>     cache-level:
> -    const: 2
> +    enum: [2, 3]

Do we want to enforce the cache level like we currently do for
interrupts and cache-sets?


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <ben.dooks@sifive.com>, <palmer@dabbelt.com>,
	<paul.walmsley@sifive.com>, <aou@eecs.berkeley.edu>,
	<greentime.hu@sifive.com>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <devicetree@vger.kernel.org>
Subject: Re: [RESEND PATCH] dt-bindings: sifive-ccache: fix cache level for l3 cache
Date: Tue, 30 Aug 2022 12:56:34 +0000	[thread overview]
Message-ID: <b810d354-18f3-9ae0-6310-57d9e36f4f9b@microchip.com> (raw)
In-Reply-To: <20220830125133.1698781-1-ben.dooks@sifive.com>

On 30/08/2022 13:51, Ben Dooks wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> With newer cores such as the p550, the SiFive composable cache can be
> a level 3 cache. Update the cache level to be one of 2 or 3.
> 
> Signed-off-by: Ben Dooks <ben.dooks@sifive.com>
> ---
>   Documentation/devicetree/bindings/riscv/sifive-ccache.yaml | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml b/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml
> index 1a64a5384e36..6190deb65455 100644
> --- a/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml
> +++ b/Documentation/devicetree/bindings/riscv/sifive-ccache.yaml
> @@ -45,7 +45,7 @@ properties:
>       const: 64
> 
>     cache-level:
> -    const: 2
> +    enum: [2, 3]

Do we want to enforce the cache level like we currently do for
interrupts and cache-sets?



  reply	other threads:[~2022-08-30 12:56 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  6:21 [PATCH 0/3] Rename sifive L2 cache to sifive CCACHE Zong Li
2022-08-29  6:21 ` Zong Li
2022-08-29  6:22 ` [PATCH 1/3] dt-bindings: sifive-ccache: rename SiFive L2 cache to composible cache Zong Li
2022-08-29  6:22   ` Zong Li
2022-08-29  6:45   ` Conor.Dooley
2022-08-29  6:45     ` Conor.Dooley
2022-08-29  7:38     ` Zong Li
2022-08-29  7:38       ` Zong Li
2022-08-29 18:42   ` Rob Herring
2022-08-29 18:42     ` Rob Herring
2022-08-30  2:57     ` Zong Li
2022-08-30  2:57       ` Zong Li
2022-10-07  2:58   ` Palmer Dabbelt
2022-10-07  2:58     ` Palmer Dabbelt
2022-10-07  3:51     ` Zong Li
2022-10-07  3:51       ` Zong Li
2022-08-29  6:22 ` [PATCH 2/3] soc: sifive: l2 cache: Rename " Zong Li
2022-08-29  6:22   ` Zong Li
2022-08-29  7:05   ` Conor.Dooley
2022-08-29  7:05     ` Conor.Dooley
2022-08-29  8:40     ` Zong Li
2022-08-29  8:40       ` Zong Li
2022-08-30  8:41       ` Conor.Dooley
2022-08-30  8:41         ` Conor.Dooley
2022-08-31  5:31         ` Zong Li
2022-08-31  5:31           ` Zong Li
2022-08-30  8:18   ` Ben Dooks
2022-08-30  8:18     ` Ben Dooks
2022-08-29  6:22 ` [PATCH 3/3] EDAC/sifive: use sifive_ccache instead of sifive_l2 Zong Li
2022-08-29  6:22   ` Zong Li
2022-10-07  2:58   ` Palmer Dabbelt
2022-10-07  2:58     ` Palmer Dabbelt
2022-08-30  7:59 ` [PATCH 0/3] Rename sifive L2 cache to sifive CCACHE Ben Dooks
2022-08-30  7:59   ` Ben Dooks
2022-08-31  8:23   ` Zong Li
2022-08-31  8:23     ` Zong Li
2022-08-30  8:26 ` [PATCH] soc: sifive: ccache: reduce printing on init Ben Dooks
2022-08-30  8:26   ` Ben Dooks
2022-08-30 16:30   ` Conor.Dooley
2022-08-30 16:30     ` Conor.Dooley
2022-08-30 17:03     ` Ben Dooks
2022-08-30 17:03       ` Ben Dooks
2022-08-31  5:22       ` Zong Li
2022-08-31  5:22         ` Zong Li
2022-08-31 15:55         ` Ben Dooks
2022-08-31 15:55           ` Ben Dooks
2022-09-01  8:34           ` Zong Li
2022-09-01  8:34             ` Zong Li
2022-08-30  8:36 ` [PATCH] dt-bindings: sifive-ccache: fix cache level for l3 cache Ben Dooks
2022-08-30  8:36   ` Ben Dooks
2022-08-30 12:47   ` Rob Herring
2022-08-30 12:47     ` Rob Herring
2022-08-30 12:51 ` [RESEND PATCH] " Ben Dooks
2022-08-30 12:51   ` Ben Dooks
2022-08-30 12:56   ` Conor.Dooley [this message]
2022-08-30 12:56     ` Conor.Dooley
2022-08-30 12:58     ` Ben Dooks
2022-08-30 12:58       ` Ben Dooks
2022-08-30 13:49       ` Conor.Dooley
2022-08-30 13:49         ` Conor.Dooley
2022-08-30 16:49         ` Ben Dooks
2022-08-30 16:49           ` Ben Dooks
2022-08-30 17:08           ` Conor.Dooley
2022-08-30 17:08             ` Conor.Dooley
2022-08-31  5:17             ` Zong Li
2022-08-31  5:17               ` Zong Li
2022-08-31  6:25               ` Conor.Dooley
2022-08-31  6:25                 ` Conor.Dooley
2022-09-02 19:36   ` Rob Herring
2022-09-02 19:36     ` Rob Herring

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=b810d354-18f3-9ae0-6310-57d9e36f4f9b@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ben.dooks@sifive.com \
    --cc=devicetree@vger.kernel.org \
    --cc=greentime.hu@sifive.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.