From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 0/7] ARM: vf610m4: Add Vybrid Cortex-M4 support
Date: Sun, 12 Oct 2014 20:13:54 +0200 [thread overview]
Message-ID: <cover.1413136383.git.stefan@agner.ch> (raw)
This adds Vybrid SoC support for the !MMU Cortex-M4 core. The patchset is
its current state is more a collection of hacks than anything mergabel,
advice and ideas how to beat it in good shape are welcome. I added some
thoughts as comments in the individual patches.
I wrote also some more info about Vybrid Cortex-M4 support in my blog
post:
http://falstaff.agner.ch/2014/10/05/make-it-two-tuxes-on-one-soc/
One thing I noticed that when I move the xipImage below the DRAM base
address, the kernel freezes:
...
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[freeze]
I think it happens when the scheduler gets started. Any idea what could
go wrong here?
Stefan Agner (7):
ARM: vf610: add low level debug support for !MMU
clocksource: add dependencies for Vybrid pit clocksource
ARM: vf610m4: add new machine and SoC for Vybrid on Cortex-M4
ARM: dts: add support for Vybrid running on Cortex-M4
irqchip: nvic: increase number of external interrupts to 112
ARM: vf610m4: HACK: get dtb pointer from SRC_GPR3
ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4
arch/arm/Kconfig | 12 ++++
arch/arm/Kconfig.debug | 4 +-
arch/arm/Makefile | 1 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/armv7-m.dtsi | 1 -
arch/arm/boot/dts/vf610m4.dts | 144 +++++++++++++++++++++++++++++++++++++
arch/arm/configs/vf610m4_defconfig | 37 ++++++++++
arch/arm/include/debug/vf.S | 10 +++
arch/arm/kernel/entry-v7m.S | 4 +-
arch/arm/kernel/head-nommu.S | 8 +++
arch/arm/mach-imx/Kconfig | 22 ++++++
arch/arm/mach-imx/Makefile | 1 +
arch/arm/mach-imx/Makefile.boot | 0
arch/arm/mach-imx/mach-vf610m4.c | 16 +++++
drivers/clocksource/Kconfig | 2 +
drivers/irqchip/irq-nvic.c | 2 +
drivers/mmc/host/Kconfig | 2 +-
drivers/pinctrl/Kconfig | 2 +-
18 files changed, 262 insertions(+), 7 deletions(-)
create mode 100644 arch/arm/boot/dts/vf610m4.dts
create mode 100644 arch/arm/configs/vf610m4_defconfig
create mode 100644 arch/arm/mach-imx/Makefile.boot
create mode 100644 arch/arm/mach-imx/mach-vf610m4.c
--
2.1.2
next reply other threads:[~2014-10-12 18:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 18:13 Stefan Agner [this message]
2014-10-12 18:13 ` [RFC 1/7] ARM: vf610: add low level debug support for !MMU Stefan Agner
2014-10-12 18:48 ` Arnd Bergmann
2014-10-13 9:26 ` Stefan Agner
2014-10-12 18:13 ` [RFC 2/7] clocksource: add dependencies for Vybrid pit clocksource Stefan Agner
2014-10-12 18:18 ` Uwe Kleine-König
2014-10-13 9:46 ` Stefan Agner
2014-10-13 10:57 ` Uwe Kleine-König
2014-10-12 18:13 ` [RFC 3/7] ARM: vf610m4: add new machine and SoC for Vybrid on Cortex-M4 Stefan Agner
2014-10-12 18:51 ` Arnd Bergmann
2014-10-13 10:03 ` Stefan Agner
2014-10-13 10:57 ` Arnd Bergmann
2014-10-12 18:13 ` [RFC 4/7] ARM: dts: add support for Vybrid running " Stefan Agner
2014-10-12 18:56 ` Arnd Bergmann
2014-10-13 10:41 ` Stefan Agner
2014-10-13 10:32 ` Mark Rutland
2014-10-13 11:08 ` Stefan Agner
2014-10-13 11:24 ` Arnd Bergmann
2014-10-13 16:11 ` Stefan Agner
2014-10-13 19:54 ` Arnd Bergmann
2014-10-13 21:20 ` Stefan Agner
2014-10-14 10:01 ` Arnd Bergmann
2014-10-12 18:13 ` [RFC 5/7] irqchip: nvic: increase number of external interrupts to 112 Stefan Agner
2014-10-12 18:14 ` [RFC 6/7] ARM: vf610m4: HACK: get dtb pointer from SRC_GPR3 Stefan Agner
2014-10-12 19:00 ` Arnd Bergmann
2014-10-13 10:10 ` Stefan Agner
2014-10-12 18:14 ` [RFC 7/7] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4 Stefan Agner
2014-11-28 14:17 ` [RFC 0/7] ARM: vf610m4: Add Vybrid Cortex-M4 support Andreas Färber
2014-11-28 16:00 ` Stefan Agner
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=cover.1413136383.git.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).