[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <e7340230-9a5b-4caf-a7b0-d048cc335994@app.fastmail.com>
Date: Wed, 05 Oct 2022 11:57:58 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Conor Dooley" <conor@...nel.org>,
Prabhakar <prabhakar.csengg@...il.com>
Cc: "Geert Uytterhoeven" <geert+renesas@...der.be>,
"Paul Walmsley" <paul.walmsley@...ive.com>,
"Palmer Dabbelt" <palmer@...belt.com>,
"Albert Ou" <aou@...s.berkeley.edu>,
"Rob Herring" <robh+dt@...nel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@...aro.org>,
"Magnus Damm" <magnus.damm@...il.com>,
Heiko Stübner <heiko@...ech.de>,
guoren <guoren@...nel.org>,
"Conor.Dooley" <conor.dooley@...rochip.com>,
"Philipp Tomsich" <philipp.tomsich@...ll.eu>,
"Nathan Chancellor" <nathan@...nel.org>,
"Atish Patra" <atishp@...osinc.com>,
"Anup Patel" <apatel@...tanamicro.com>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org,
"Biju Das" <biju.das.jz@...renesas.com>,
"Lad, Prabhakar" <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [RFC PATCH v2 2/2] soc: renesas: Add L2 cache management for RZ/Five SoC
On Tue, Oct 4, 2022, at 7:42 PM, Conor Dooley wrote:
> On Mon, Oct 03, 2022 at 11:32:22PM +0100, Prabhakar wrote:
>>
>> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
>> ---
>> arch/riscv/include/asm/cacheflush.h | 8 +
>> arch/riscv/include/asm/errata_list.h | 2 +
>> arch/riscv/include/asm/sbi.h | 1 +
>> arch/riscv/mm/dma-noncoherent.c | 20 ++
>
> Stupid question maybe, but I assume you mixed the driver addition and
> the changes to arch/riscv for the sake of easily creating the RFC?
>
>> drivers/soc/renesas/Makefile | 4 +
>> drivers/soc/renesas/rzf/Makefile | 3 +
>> drivers/soc/renesas/rzf/ax45mp_cache.c | 365 +++++++++++++++++++++++++
>> drivers/soc/renesas/rzf/rzf_sbi.h | 27 ++
My feeling is that L2 cache behavior should live in arch/riscv
rather than drivers/soc/, since this is not specific to a SoC
family but rather the CPU core. I would also expect that the
actual implementation and DT binding can be shared with
non-renesas SoCs using the same CPU core.
Arnd
Powered by blists - more mailing lists