mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/3] ARM64 early cache fixes
Date: Thu, 19 Dec 2019 10:13:07 +0100	[thread overview]
Message-ID: <20191219091310.27421-1-l.stach@pengutronix.de> (raw)

This is a resend of the 2 ARM64 early cache fixes by Ahmad. They were
not applied at the time, as there was a report of them breaking Barebox
on i.MX8M. I finally had time to look into that, the first patch by
me cleans the stage, so the cache fixes no longer break anything.

At least the icache invalidation patch fixes an issue I hit on one
system, were minimal (harmless) changes to the Barebox code would
break execution.

Regards,
Lucas

Ahmad Fatoum (2):
  ARM: cache_64: invalidate dcache in arm_early_mmu_cache_invalidate
  ARM: cache_64: invalidate icache in arm_early_mmu_cache_flush

Lucas Stach (1):
  ARM64: entry: save/restore potentially clobbered registers

 arch/arm/cpu/cache_64.c    |  2 ++
 arch/arm/cpu/entry_ll_64.S | 12 +++++++-----
 2 files changed, 9 insertions(+), 5 deletions(-)

-- 
2.20.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2019-12-19  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19  9:13 Lucas Stach [this message]
2019-12-19  9:13 ` [PATCH 1/3] ARM64: entry: save/restore potentially clobbered registers Lucas Stach
2019-12-20 15:34   ` Ahmad Fatoum
2019-12-20 15:42     ` Lucas Stach
2019-12-20 16:14       ` Ahmad Fatoum
2019-12-19  9:13 ` [PATCH 2/3] ARM: cache_64: invalidate dcache in arm_early_mmu_cache_invalidate Lucas Stach
2019-12-19  9:13 ` [PATCH 3/3] ARM: cache_64: invalidate icache in arm_early_mmu_cache_flush Lucas Stach
2019-12-20 15:14 ` [PATCH 0/3] ARM64 early cache fixes Sascha Hauer

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=20191219091310.27421-1-l.stach@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.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