[PATCH] bcm53xx: initial support for the BCM5301/BCM470X SoC with ARM CPU

[cavokz@gmail.com (Domenico Andreoli)]

On Thu, Jul 25, 2013 at 02:37:07PM -0700, Christian Daudt wrote:
> On 13-07-25 01:33 PM, Hauke Mehrtens wrote:
> >On 07/25/2013 12:54 AM, Domenico Andreoli wrote:
> >>On Wed, Jul 24, 2013 at 09:21:43PM +0200, Hauke Mehrtens wrote:
> >>>On 07/24/2013 02:44 AM, Domenico Andreoli wrote:
> >>>>On Wednesday, July 24, 2013, Hauke Mehrtens <hauke@hauke-m.de
> >>>><mailto:hauke@hauke-m.de>> wrote:
> >>>>>On 07/19/2013 03:36 AM, Domenico Andreoli wrote:
> >>>>>>On Tue, Jul 16, 2013 at 05:35:21PM +0200, Hauke Mehrtens wrote:
> >>>>>>>On 07/16/2013 05:20 PM, Thomas Petazzoni wrote:
> >>>>>>>>>diff --git a/arch/arm/mach-bcm53xx/Kconfig
> >>>>b/arch/arm/mach-bcm53xx/Kconfig
> >>>>>>>>>new file mode 100644
> >>>>>>>>>index 0000000..1e16e87
> >>>>>>>>>--- /dev/null
> >>>>>>>>>+++ b/arch/arm/mach-bcm53xx/Kconfig
> >>>>>>>>>@@ -0,0 +1,10 @@
> >>>>>>>>>+config ARCH_BCM53XX
> >>>>>>>>>+  bool "Broadcom BCM47XX / BCM53XX ARM SoC"
> >>>>>>>>So the directory is named mach-bcm53xx, but you also handle BCM47xx
> >>>>>>>>SoCs. This doesn't sound really easy to follow.
> >>>>>>At the time of the BCM281XX merge we considered that such directories
> >>>>would
> >>>>>>mostly contain board files only, being these new entries DT based. Hence
> >>>>>>the choice of mach-bcm to collect all of them.
> >>>>>>
> >>>>>>I think you should then put this stuff there.
> >>>>>So you think I should move the file from
> >>>>>arch/arm/mach-bcm53xx/bcm53xx.c to arch/arm/mach-bcm/bcm53xx.c ?
> >>>>yes
> >>>>
> >>>>this looks more comsistent with the actual soc name:
> >>>>arch/arm/mach-bcm/bcm530xx.c
> >>>>
> >>>>but I find also acceptable the complete name of the "parent" soc (as I'm
> >>>>doing with the bcm4760), so: arch/arm/mach-bcm/bcm53010.c
> >>>I do not think these Broadcom ARM SoCs (bcm4760, BCM5301X, bcm11351)
> >>>have more in common than the vendor name, so I do not think it is a good
> >>>idea to place them all at mach-bcm.
> >>In an ideal DT-only world (as basically is for Broadcom ARM SoCs), whatever
> >>two or more SoCs share can hopefully modelled in a driver and as such
> >>would go in the drivers/ subtree. What's left is really SoC specific and,
> >>again hopefully, very minimal.
> >>
> >>There should not be any SoC so weird to require a whole subdirectory full
> >>of that SoC specific stuff. So grouping everything by vendor name looks
> >>quite appealing to me.
> >>
> >>Sharing the same subdir requires people working in it to talk and find
> >>agreements some more than the sparsely populated subdir did (because there
> >>is not a single maintainer who owns it). I think this is a big advantage
> >>Broadcomers can start with right now.
> >I want to be able to build the BCM5301X SoC without building the current
> >CONFIG_ARCH_BCM, so what name do you suggest for board_bcm.o ?
> >My plan would be to make CONFIG_ARCH_BCM just activate the Broadcom
> >submenu, but not build any code. Then the list of Broadcom SoCs is
> >opened like CONFIG_ARCH_BCM5301X and the "old" CONFIG_ARCH_BCM.
> >
> >
> CONFIG_ARCH_BCM wasn't the best name, but it is there now. We intend
> to upstream the (mobile-team) ARM SoCs going forward, and have them
> be multiplatform and all buildable into a single zImage with the
> ARCH_BCM config option. Which is why this option does not have a
> chip name on it.
> Take ARCH_BCM == Broadcom Mobile team SoCs (I think that's what the
> help on it says).

This solves the double linking issue I had. No need to configure
CONFIG_ARCH_BCM if you are not interested in what it brings.

diff --git a/arch/arm/Makefile b/arch/arm/Makefile
index c0ac0f5..230b5d7 100644
--- a/arch/arm/Makefile
+++ b/arch/arm/Makefile
@@ -145,7 +145,7 @@ textofs-$(CONFIG_ARCH_MSM8960) := 0x00208000
 # Machine directory name.  This list is sorted alphanumerically
 # by CONFIG_* macro name.
 machine-$(CONFIG_ARCH_AT91)            += at91
-machine-$(CONFIG_ARCH_BCM)             += bcm
+machine-y                              += bcm
 machine-$(CONFIG_ARCH_BCM2835)         += bcm2835
 machine-$(CONFIG_ARCH_CLPS711X)                += clps711x
 machine-$(CONFIG_ARCH_CNS3XXX)         += cns3xxx
 
Regards,
Domenico