From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Energy Micro efm32 support
Date: Mon, 4 Nov 2013 11:58:36 +0100 [thread overview]
Message-ID: <20131104105836.GI14892@pengutronix.de> (raw)
Hello,
now that 3.12 is out, I patted my efm32 tree and I consider the base
platform support ready for merging. I put it into my for-next branch at
git://git.pengutronix.de/git/ukl/linux.git for-next
so it should make it into the next next. I target 3.14-rc1 to make it
in. The patches have a few runtime (but no compile-time) dependencies on
these patches:
ARM: call of_clk_init from default time_init handler
clocksource: Provide timekeeping for efm32 SoCs
clk: new driver for efm32 SoC
All but the last patch are already in next, Mike promised to take the
last one. DEBUG_LL is broken without
ARM: DEBUG_LL on efm32 SoCs
which already is in next, too. There are no device tree source files yet
as they have a compile time dependency on the clk patch above.
I'm not using multiarch here. I'm still unsure if it makes sense or not
to use it for v7-M, I'm sticking to not using it mainly because of
Russell's objections. Still the patch adding the platform is very small
now (just a trivial machine file, a defconfig and Makefile/Kconfig
adaptions) and is easily switched to multiarch if need be.
The complete and runnable tree is available in my master branch.
I suggest to let it go in via Russell as it has less potential to
conflict with arm-soc.
As the patches changed a bit I will repost them here. Note I called them
all "v4" even though patches 1 to 3 are really only (a resent of) v1.
Any feed back is welcome.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2013-11-04 10:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 10:58 Uwe Kleine-König [this message]
2013-11-04 11:00 ` [PATCH v4 1/4] ARM: deprecate mach/timex.h for !ARCH_MULTIPLATFORM Uwe Kleine-König
2013-11-04 13:53 ` Arnd Bergmann
2013-11-05 8:33 ` Uwe Kleine-König
2013-11-05 9:03 ` [PATCH] ARM: u300: fix timekeeping when periodic mode is used Uwe Kleine-König
2013-11-05 9:44 ` Linus Walleij
2013-11-25 21:13 ` Uwe Kleine-König
2013-11-26 12:32 ` Linus Walleij
2013-11-05 9:12 ` [PATCH v5 1/4] ARM: deprecate mach/timex.h for !ARCH_MULTIPLATFORM Uwe Kleine-König
2013-11-05 9:42 ` Linus Walleij
2013-11-05 10:01 ` Uwe Kleine-König
2013-11-05 11:34 ` Arnd Bergmann
2013-11-05 11:37 ` Linus Walleij
2013-11-05 11:45 ` Russell King - ARM Linux
2013-11-05 12:26 ` Arnd Bergmann
2013-11-05 13:27 ` Uwe Kleine-König
2013-11-05 14:58 ` Arnd Bergmann
2013-11-05 11:52 ` Uwe Kleine-König
2013-11-04 11:00 ` [PATCH v4 2/4] ARM: make mach-xyz/Makefile.boot optional " Uwe Kleine-König
2013-11-11 19:35 ` Olof Johansson
2015-01-30 9:32 ` Uwe Kleine-König
2013-11-04 11:00 ` [PATCH v4 3/4] ARM: v7-M: drop using mach/entry-macro.S Uwe Kleine-König
2013-11-11 19:35 ` Olof Johansson
2013-11-04 11:00 ` [PATCH v4 4/4] ARM: new platform for Energy Micro's EFM32 Cortex-M3 SoCs Uwe Kleine-König
2013-11-04 13:56 ` Arnd Bergmann
2013-11-05 9:48 ` Uwe Kleine-König
2013-11-05 11:10 ` Arnd Bergmann
2013-11-19 10:20 ` [PATCH v4 0/4] Energy Micro efm32 support Uwe Kleine-König
2013-11-19 13:11 ` Arnd Bergmann
2013-11-19 19:08 ` Uwe Kleine-König
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=20131104105836.GI14892@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).