From: "Marek Behún" <kabel@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: pali@kernel.org, "U-Boot Mailing List" <u-boot@lists.denx.de>,
"Marek Behún" <kabel@kernel.org>
Subject: [PATCH u-boot-marvell 0/5] mvebu important fixes
Date: Thu, 8 Sep 2022 16:06:49 +0200 [thread overview]
Message-ID: <20220908140654.7051-1-kabel@kernel.org> (raw)
Hello Stefan,
could you please test and send these patches to Tom for the next rc,
if possible?
I discovered that loadb does not work with higher speeds and lzmadec
is way too slow, bisected to one of Pali's commits, and then Pali
investigated that there are some issues with cache settings.
Marek
Pali Rohár (5):
arm: mvebu: Fix function enable_caches
arm: mvebu: Guard non-AXP code by checking for AXP
arm: mvebu: lowlevel.S: Use CR_M from asm/system.h
arm: mvebu: Enable L2 cache also on Armada 38x
arm: mvebu: Fix moving internal registers
arch/arm/include/asm/pl310.h | 9 +++++++--
arch/arm/mach-mvebu/cpu.c | 37 +++++++++++++++-------------------
arch/arm/mach-mvebu/lowlevel.S | 30 ++++++++++++++++++++++++++-
3 files changed, 52 insertions(+), 24 deletions(-)
--
2.35.1
next reply other threads:[~2022-09-08 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 14:06 Marek Behún [this message]
2022-09-08 14:06 ` [PATCH u-boot-marvell 1/5] arm: mvebu: Fix function enable_caches Marek Behún
2022-09-12 6:57 ` Stefan Roese
2022-09-08 14:06 ` [PATCH u-boot-marvell 2/5] arm: mvebu: Guard non-AXP code by checking for AXP Marek Behún
2022-09-12 6:58 ` Stefan Roese
2022-09-08 14:06 ` [PATCH u-boot-marvell 3/5] arm: mvebu: lowlevel.S: Use CR_M from asm/system.h Marek Behún
2022-09-12 6:58 ` Stefan Roese
2022-09-08 14:06 ` [PATCH u-boot-marvell 4/5] arm: mvebu: Enable L2 cache also on Armada 38x Marek Behún
2022-09-12 6:58 ` Stefan Roese
2022-09-08 14:06 ` [PATCH u-boot-marvell 5/5] arm: mvebu: Fix moving internal registers Marek Behún
2022-09-12 6:59 ` Stefan Roese
2022-09-12 7:04 ` [PATCH u-boot-marvell 0/5] mvebu important fixes Stefan Roese
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=20220908140654.7051-1-kabel@kernel.org \
--to=kabel@kernel.org \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--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