From: Linus Walleij <linus.walleij@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 2/2] ARM: implement cacheinfo support
Date: Thu, 7 Nov 2024 14:55:01 +0100 [thread overview]
Message-ID: <CACRpkdZ1Pkd_iKDNE+m_R4Anbdv=dcg77oC95yqaAM_dp0BRYA@mail.gmail.com> (raw)
In-Reply-To: <20241014-armv7-cacheinfo-v2-2-38ab76d2b7fa@linaro.org>
On Mon, Oct 14, 2024 at 3:56 PM Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
> On ARMv7 / v7m machines read CTR and CLIDR registers to provide
> information regarding the cache topology. Earlier machines should
> describe full cache topology in the device tree.
>
> Note, this follows the ARM64 cacheinfo support and provides only minimal
> support required to bootstrap cache info. All useful properties should
> be decribed in Device Tree.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
It's really neat actually!
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2024-11-07 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:55 [PATCH v2 0/2] ARM: implement cacheinfo support (for v7/v7m) Dmitry Baryshkov
2024-10-14 13:55 ` [PATCH v2 1/2] ARM: add CLIDR accessor functions Dmitry Baryshkov
2024-11-07 13:51 ` Linus Walleij
2024-10-14 13:55 ` [PATCH v2 2/2] ARM: implement cacheinfo support Dmitry Baryshkov
2024-11-07 13:55 ` Linus Walleij [this message]
[not found] ` <CGME20250115101159eucas1p1261a8b3e78b83c4fec63e3ac00e4d59a@eucas1p1.samsung.com>
2025-01-15 10:11 ` Marek Szyprowski
2025-01-15 11:11 ` Dmitry Baryshkov
2024-11-04 11:51 ` [PATCH v2 0/2] ARM: implement cacheinfo support (for v7/v7m) Dmitry Baryshkov
2024-11-04 11:52 ` Ard Biesheuvel
2024-11-07 13:55 ` Linus Walleij
2024-11-07 14:34 ` Dmitry Baryshkov
2025-01-03 5:55 ` Dmitry Baryshkov
2025-01-13 15:07 ` Linus Walleij
2025-01-14 11:57 ` Dmitry Baryshkov
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='CACRpkdZ1Pkd_iKDNE+m_R4Anbdv=dcg77oC95yqaAM_dp0BRYA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andersson@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sudeep.holla@arm.com \
/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).