From: Tom Rini <trini@konsulko.com>
To: Lukasz Wiecaszek <lukasz.wiecaszek@googlemail.com>
Cc: u-boot@lists.denx.de, fenghua@phytium.com.cn,
Lukasz Wiecaszek <lukasz.wiecaszek@gmail.com>
Subject: Re: [PATCH] arm: Check FEAT_CCIDX when parsing ccsidr_el1 register
Date: Wed, 20 Mar 2024 08:41:45 -0400 [thread overview]
Message-ID: <20240320124145.GO3442575@bill-the-cat> (raw)
In-Reply-To: <20240310103003.2302-1-lukasz.wiecaszek@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Sun, Mar 10, 2024 at 11:29:58AM +0100, Lukasz Wiecaszek wrote:
> Current Cache Size ID Register (ccsidr_el1) has two "flavors"
> depending on whether FEAT_CCIDX is implemented or not.
> When FEAT_CCIDX is implemented Associativity parameter
> is coded on bits [23:3] and NumSets parameter on bits [55:32].
> When FEAT_CCIDX is not implemented then Associativity parameter
> is coded on bits [12:3] and NumSets parameter on bits [27:13].
> Current U-Boot code does not check whether FEAT_CCIDX is implemented
> and always parses ccsidr_el1 as if FEAT_CCIDX was not implemented.
> This is of course wrong on systems where FEAT_CCIDX is implemented.
> This patch fixes that problems and tests whether FEAT_CCIDX
> is implemented or not and accordingly parses the ccsidr_el1 register.
>
> Signed-off-by: Lukasz Wiecaszek <lukasz.wiecaszek@gmail.com>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2024-03-20 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 10:29 [PATCH] arm: Check FEAT_CCIDX when parsing ccsidr_el1 register Lukasz Wiecaszek
2024-03-20 12:41 ` Tom Rini [this message]
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=20240320124145.GO3442575@bill-the-cat \
--to=trini@konsulko.com \
--cc=fenghua@phytium.com.cn \
--cc=lukasz.wiecaszek@gmail.com \
--cc=lukasz.wiecaszek@googlemail.com \
--cc=u-boot@lists.denx.de \
/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