On Tue, 2012-10-09 at 12:45 +0100, Pawel Moll wrote:
On Tue, 2012-10-09 at 12:34 +0100, Viresh Kumar wrote:
On 9 October 2012 16:24, Pawel Moll pawel.moll@arm.com wrote:
On Tue, 2012-10-09 at 11:42 +0100, Sudeep KarkadaNagesha wrote:
Robin raised a valid point that this driver is TC2 specific and bL is not appropriate name for it including the file name(my bad choice at first).
Just to be painfully precise ;-) I must say it's not TC2 specific, but V2P-CA15_A7 specific. TC2 == Test Chip 2, also known as Garuda. The SPC that the driver talks to is _not_ a part of the TC2, it's a separate component of the V2P-CA15_A7 core tile (HBI0249).
Why is it CA15_A7 specific? It looks to me like a simple cpufreq driver for vexpress board, that may support any coretile... Single cluster, multicluster (big LITTLE or otherwise)...
What's in there for CA15 or A7 ?
It's not about A15 or A7, but about V2P-CA15_A7 ;-) That's what the "TC2 core tile" is officially called.
The driver talks to firmware running on the microcontroller on the tile. No other VE tile (so far) has similar interface available, so it is specific for this particular core tile.
Now, _if_ some of future boards share the same interface for the power management firmware (and the _if_ is a big _IF_ ;-), it still wouldn't be TC2-specific (because the future boards will not use TC2). So maybe we want to call it something like "vexpress-spc" (or whatever three letter acronym we use here ;-) and hope for the best?
I've gone with this "vexpress-spc" name for the coming Linaro release.