linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: "Alim Akhtar" <alim.akhtar@samsung.com>
Cc: "'Devang Tailor'" <dev.tailor@samsung.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-samsung-soc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <faraz.ata@samsung.com>
Subject: Re: [PATCH v2] arm64: dts: add cpu cache information to ExynosAuto-v920
Date: Fri, 31 Jan 2025 13:27:03 +0000	[thread overview]
Message-ID: <Z5zPpz6WAbPJX701@bogus> (raw)
In-Reply-To: <006401db73d6$2af35fb0$80da1f10$@samsung.com>

On Fri, Jan 31, 2025 at 05:19:09PM +0530, Alim Akhtar wrote:
> Hi Devang
>
> >
> > Add CPU caches information to its dt nodes so that the same is available to
> > userspace via sysfs. This SoC has 64/64 KB I/D cache and 256KB of L2 cache for
> > each core, 2 MB of shared L3 cache for each quad cpu cluster and 1 MB of
> > shared L3 cache for the dual cpu cluster.
> >
> > Signed-off-by: Devang Tailor <dev.tailor@samsung.com>
> >
> > ---
> > Changes in v2:
> > - Added L3 cache for all the three cpu clusters
> > - Corrected L2 cache numbering as a part of review comments from Krzysztof
> >   and updated as per cpus clusters.
> > - Link to v1: https://patchwork.kernel.org/project/linux-arm-
> > kernel/patch/20241231064350.523713-1-dev.tailor@samsung.com/
> > ---
> >  .../arm64/boot/dts/exynos/exynosautov920.dtsi | 127
> > ++++++++++++++++++
> >  1 file changed, 127 insertions(+)
> >
> [snip]
>  > +		l3_cache_cl0: l3-cache0 {
> You can add one node for cl0 and cl1, say "l3_cache_cl0_cl1" and
> Remove the specific node for CL1, because both are same.
>

What do you mean by "both are same" ?
Do you mean both have exact same properties but are physically different
caches ? OR
Do you mean it is just one shared cache ?

If former, we still need distinct node to get the cacheinfo about
shareability correct. If this is about avoiding duplication of errors,
you can probably define some macro and avoid it, but we need 2 nodes in
the devicetree.

If latter, you suggestion is correct.

--
Regards,
Sudeep


  reply	other threads:[~2025-01-31 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250108054224epcas5p399f3d734f8d9f82e5ae75d183d1a5344@epcas5p3.samsung.com>
2025-01-08  5:50 ` [PATCH v2] arm64: dts: add cpu cache information to ExynosAuto-v920 Devang Tailor
2025-01-31 11:49   ` Alim Akhtar
2025-01-31 13:27     ` Sudeep Holla [this message]
2025-02-05 15:52       ` Krzysztof Kozlowski
2025-02-05 16:10         ` Alim Akhtar
2025-02-17  8:45           ` Devang Tailor
2025-02-05 16:07       ` Alim Akhtar
2025-02-17 10:36   ` 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=Z5zPpz6WAbPJX701@bogus \
    --to=sudeep.holla@arm.com \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=dev.tailor@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=faraz.ata@samsung.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).