linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH soc v8 0/3] ARM: vf610m4: Add Vybrid Cortex-M4 support
Date: Wed, 20 May 2015 00:03:49 +0200	[thread overview]
Message-ID: <1432073032-26561-1-git-send-email-stefan@agner.ch> (raw)

This is the soc part of the splitted patchset which enables Cortex-M4
support on Vybrid, as discussed in the thread of patchset v7.

Changes since v7:
- Split version for arm-soc
- Default to debug/uncompress.h for ARM_SINGLE_ARMV7M initially
- Drop EFM32 conversion (will be part of a follow-up patch)

Stefan Agner (3):
  ARM: unify MMU/!MMU addruart calls
  ARM: introduce ARM_SINGLE_ARMV7M for ARMv7-M platforms
  ARM: vf610: enable Cortex-M4 configuration on Vybrid SoC

 Documentation/devicetree/bindings/arm/fsl.txt |  3 +++
 arch/arm/Kconfig                              | 13 +++++++++
 arch/arm/Kconfig.debug                        |  5 ++--
 arch/arm/include/debug/efm32.S                |  2 +-
 arch/arm/kernel/debug.S                       |  2 +-
 arch/arm/mach-imx/Kconfig                     | 38 +++++++++++++++------------
 arch/arm/mach-imx/Makefile.boot               |  0
 arch/arm/mach-imx/mach-vf610.c                |  1 +
 8 files changed, 43 insertions(+), 21 deletions(-)
 create mode 100644 arch/arm/mach-imx/Makefile.boot

-- 
2.4.1

             reply	other threads:[~2015-05-19 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 22:03 Stefan Agner [this message]
2015-05-19 22:03 ` [PATCH soc v8 1/3] ARM: unify MMU/!MMU addruart calls Stefan Agner
2015-05-19 22:03 ` [PATCH soc v8 2/3] ARM: introduce ARM_SINGLE_ARMV7M for ARMv7-M platforms Stefan Agner
2015-05-19 22:03 ` [PATCH soc v8 3/3] ARM: vf610: enable Cortex-M4 configuration on Vybrid SoC Stefan Agner
2015-05-19 22:42 ` [PATCH soc v8 0/3] ARM: vf610m4: Add Vybrid Cortex-M4 support Stefan Agner
2015-05-20 21:29   ` Arnd Bergmann

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=1432073032-26561-1-git-send-email-stefan@agner.ch \
    --to=stefan@agner.ch \
    --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).