From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Cc: "Chris Packham" <judge.packham@gmail.com>,
"Bin Meng" <bmeng.cn@gmail.com>, "Marc Zyngier" <maz@kernel.org>,
"Peng Fan" <peng.fan@nxp.com>,
"Pierre-Clément Tosi" <ptosi@google.com>,
"Simon Glass" <sjg@chromium.org>,
"Will Deacon" <willdeacon@google.com>, "Ye Li" <ye.li@nxp.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
meitao <meitaogao@asrmicro.com>
Subject: [PATCH 0/3] Revert HAFDBS changes
Date: Fri, 27 Oct 2023 13:23:51 +1300 [thread overview]
Message-ID: <20231027002409.430285-1-judge.packham@gmail.com> (raw)
As discussed this series reverts the HAFDBS changes that caused an issue
on AC5/AC5X. I think there are some improvements that can be made to the
initial memory map for the AC5/AC5X but so far nothing I've found makes
it compatible with the HAFDBS changes.
Chris Packham (3):
Revert "armv8: enable HAFDBS for other ELx when FEAT_HAFDBS is
present"
Revert "arm64: Use level-2 for largest block mappings when FEAT_HAFDBS
is present"
Revert "arm64: Use FEAT_HAFDBS to track dirty pages when available"
arch/arm/cpu/armv8/cache_v8.c | 30 +++---------------------------
arch/arm/include/asm/armv8/mmu.h | 20 ++++----------------
arch/arm/include/asm/global_data.h | 2 --
3 files changed, 7 insertions(+), 45 deletions(-)
--
2.42.0
next reply other threads:[~2023-10-27 0:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 0:23 Chris Packham [this message]
2023-10-27 0:23 ` [PATCH 1/3] Revert "armv8: enable HAFDBS for other ELx when FEAT_HAFDBS is present" Chris Packham
2023-11-17 19:42 ` Tom Rini
2023-10-27 0:23 ` [PATCH 2/3] Revert "arm64: Use level-2 for largest block mappings " Chris Packham
2023-11-17 19:42 ` Tom Rini
2023-10-27 0:23 ` [PATCH 3/3] Revert "arm64: Use FEAT_HAFDBS to track dirty pages when available" Chris Packham
2023-11-17 19:42 ` Tom Rini
2023-10-27 9:49 ` [PATCH 0/3] Revert HAFDBS changes Pierre-Clément Tosi
2023-10-27 17:22 ` Tom Rini
2023-11-09 21:33 ` Tom Rini
2023-11-10 5:38 ` Chris Packham
2023-11-17 19:41 ` Tom Rini
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=20231027002409.430285-1-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=maz@kernel.org \
--cc=meitaogao@asrmicro.com \
--cc=paul.liu@linaro.org \
--cc=peng.fan@nxp.com \
--cc=ptosi@google.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=willdeacon@google.com \
--cc=ye.li@nxp.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