[PATCH 0/5] ARM: SMP: support Broadcom mobile SoCs

From: Alex Elder
Date: Thu Apr 03 2014 - 22:17:57 EST


This series adds SMP support for two Broadcom mobile SoC families.
It uses CPU_METHOD_OF_DECLARE() (or rather a new variant of that)
so that SMP operations are assigned using device tree rather than
adding it to a machine definition in a board file.

The first patch adds the ability to extract information from device
tree nodes having a matching "enable-method" value. This allows
additional parameters to be associated with the enable method. This
is used for the Broadcom SoCs to efficiently determine the location
of a special register used in coordinating the start of secondary
CPUs.

I have not included a device tree document update here; I would like
suggestions on where the new enable method and its parameter should
be documented. (I presume in .../arm/cpus.txt, but that could get
out of hand as more boards define new enable methods.)

-Alex

Note:
This series is based on the current arm-soc/for-next branch:
e98cd72 arm-soc: document samsung merges
Plus one more recently-posted patch:
http://permalink.gmane.org/gmane.linux.kernel/1677714

This series is available here:
http://git.linaro.org/landing-teams/working/broadcom/kernel.git
Branch review/bcm-smp

Alex Elder (5):
ARM: introduce CPU_METHOD_OF_DECLARE_SETUP()
ARM: add SMP support for Broadcom mobile SoCs
ARM: configs: enable SMP in bcm_defconfig
ARM: dts: enable SMP support for bcm28155
ARM: dts: enable SMP support for bcm21664

arch/arm/boot/dts/bcm11351.dtsi | 19 ++++
arch/arm/boot/dts/bcm21664.dtsi | 19 ++++
arch/arm/configs/bcm_defconfig | 2 +
arch/arm/include/asm/smp.h | 10 +-
arch/arm/kernel/devtree.c | 31 +++++--
arch/arm/mach-bcm/Kconfig | 18 +++-
arch/arm/mach-bcm/Makefile | 5 +-
arch/arm/mach-bcm/platsmp.c | 194 +++++++++++++++++++++++++++++++++++++++
8 files changed, 286 insertions(+), 12 deletions(-)
create mode 100644 arch/arm/mach-bcm/platsmp.c

--
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/