[PATCH v2] Add support for generic BCM SoC chipsets

[Arnd Bergmann]

On Sunday 11 November 2012, Stephen Warren wrote:
> > I'm following the other mobile ARM SoCs which all have a single mach-
> > directory for various families of chips (mach-tegra, mach-omap2,
> > etc...). Plus the intent is to have a single set of mach files that
> > works across bcm SoCs, so it is preferable to keep it in a single mach-bcm.
> 
> It's quite possible to create one directory now, e.g. mach-bcm281xx, and
> then when consolidation with other mach-bcm* happens, merge all those
> directories into a single mach-bcm. I would tend to prefer (but only
> lightly) using mach-bcm281xx now and then renaming later, unless you
> plan on expanding the SoC support in the pretty near future.

I think the main question is how many files we expect to see in the
platform directories for each of bcm3528, bcm281xx and bcm476x. Right
now, my feeling is that each of them can be a single file, since most
of the stuff that has traditionally been in mach-* directories is
moving out to drivers now.

If that is the case, having one directory for each platform is a little
silly and we should just stick them all in one place, using the
"mach-bcm" name more as a help for people looking for the code than
an indication of being a single soc family or maintained by the same
person.  We already have some precedent in shmobile, which contains
some platforms that were completely distinct at the time they were
introduced.

You still have to work out how you want to maintain that directory though,
either just having per-file maintainers, or having multiple people
take responsible for the entire directory.

	Arnd