linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Fix 740t support and remove more unused ARMv3 code
Date: Wed, 30 Jan 2013 14:27:43 +0000	[thread overview]
Message-ID: <1359556069-28289-1-git-send-email-will.deacon@arm.com> (raw)

Hello,

When looking at the remaining ARMv3 code that we still have kicking
around, I noticed that the only user of the cache-flushing routines is
the 740t, an ARMv4 chip. Having read the datasheet, we can actually use
our ARMv4 cache-flushing code and remove cache-v3.S.

After making that change, I thought I'd better do some testing, which is
where the fun began...

Even after getting hold of a 740t Integrator/AP core-tile, I ran into
many problems with the CPU support, which I don't believe has *ever*
worked. Anyway, having fixed those, the board runs like a charm.

Next stop is the 940t, which looks to be broken in similar ways.

Will


Will Deacon (6):
  ARM: tlbflush: remove ARMv3 support
  ARM: cache: remove ARMv3 support code
  ARM: mm: fix numerous hideous errors in proc-arm740.S
  ARM: mm: remove broken condition check for v4 flushing
  ARM: modules: don't export cpu_set_pte_ext when !MMU
  ARM: integrator: ensure ap_syscon_base is initialised when
    !CONFIG_MMU

 arch/arm/include/asm/glue-cache.h        |   8 --
 arch/arm/include/asm/tlbflush.h          |  11 +--
 arch/arm/mach-integrator/integrator_ap.c |   2 +-
 arch/arm/mm/Kconfig                      |   5 +-
 arch/arm/mm/Makefile                     |   1 -
 arch/arm/mm/cache-v3.S                   | 137 -------------------------------
 arch/arm/mm/cache-v4.S                   |   2 +-
 arch/arm/mm/proc-arm740.S                |  30 ++++---
 arch/arm/mm/proc-syms.c                  |   2 +
 9 files changed, 24 insertions(+), 174 deletions(-)
 delete mode 100644 arch/arm/mm/cache-v3.S

-- 
1.8.0

             reply	other threads:[~2013-01-30 14:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 14:27 Will Deacon [this message]
2013-01-30 14:27 ` [PATCH 1/6] ARM: tlbflush: remove ARMv3 support Will Deacon
2013-01-30 14:27 ` [PATCH 2/6] ARM: cache: remove ARMv3 support code Will Deacon
2013-01-31  0:40   ` Hyok S. Choi
2013-01-31  9:56     ` Will Deacon
2013-01-30 14:27 ` [PATCH 3/6] ARM: mm: fix numerous hideous errors in proc-arm740.S Will Deacon
2013-02-01 11:10   ` Hyok S. Choi
2013-01-30 14:27 ` [PATCH 4/6] ARM: mm: remove broken condition check for v4 flushing Will Deacon
2013-01-30 14:27 ` [PATCH 5/6] ARM: modules: don't export cpu_set_pte_ext when !MMU Will Deacon
2013-01-30 14:27 ` [PATCH 6/6] ARM: integrator: ensure ap_syscon_base is initialised when !CONFIG_MMU Will Deacon
2013-01-31 20:21   ` Linus Walleij
2013-01-31 22:34     ` Will Deacon
2013-01-31 22:56       ` Olof Johansson
2013-02-03 11:48         ` Will Deacon
2013-02-04 21:49           ` Arnd Bergmann
2013-02-06 18:25             ` Will Deacon
2013-02-10  0:29               ` Olof Johansson

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=1359556069-28289-1-git-send-email-will.deacon@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).