Thread (1 message) 1 message, 1 author, 2015-01-09

[PATCH v2] ARM: dts: Add dts file for odroid XU3 board

From: khilman@kernel.org (Kevin Hilman)
Date: 2015-01-09 21:06:52
Also in: linux-devicetree, linux-samsung-soc

Sjoerd Simons [off-list ref] writes:
On Wed, 2015-01-07 at 23:49 +0000, Jonathan Stone -SISA wrote:
quoted
On On Wed, 2015-01-07 at 18:37 +0000, Sjoerd Simons writes wrote:
quoted
On Wed, 2015-01-07 at 18:37 +0000, Anand Moon wrote:>
[...]
quoted
quoted
Only 4 core cpu's are on my board. Also CpuFreq is not working.
Can you share some point on this.
quoted
The defconfig is using the bL switcher, which pairs up big and
little cores to make them appear as one core.. So for 8 real
cores, you'll get
4 "virtual cores".
That configuration is appropriate for the 5420, which allegedly has
a hardware bug in the cache-coherence between the Cortex-A7 block
and the Cortex-A15 block.
Newer Exynos 5 SoCs -- 5422/5800, 5620, etc -- don't have that
bug. The scheduler should configured to do HMP on all 8 (or 6)
cores.
I don't have a 5410, but I assume it has the same bug as the 5420.
Yes the kernel/scheduler could be configured like that, but
exynos_defconfig turns on bL rather then HMP. 

Now it's not unthinkable to add code/dts properties to select the
right/preferred scheduling strategy depending on the board (HMP vs. bL).
But proper HMP scheduling is still a work in progress in mainline 
Yes, HMP scheduling is not yet ready for mainline, which is why the
switcher is enabled by default.  If you turn the switcher off, you will
indeed get all 8 cores, but you may get some rather strange and
sub-optimal results with performance since from the scheduler
perspective, it will balance tasks across all 8 CPUs as if they were
identical.
and iirc specifically on the XU3 there are open issue wrt. MCPM and
its secure firmware. I've added Kevin to the CC as he's been working
on this topic so should know the status a lot better then i do.
The broken firmware issues don't affect scheduling directly, but affect
the low-power states that are available to the kernel.  Since the
firwmware doesn't allow proper access to CCI, low-power states that
require MCPM are not available, which, among other things, means the
clusters can not be powered down.
quoted
The XU3 kernel supplied by HardKernel shows all 8 cores, and does HMP scheduling across all 8.
Yes, that's independant of the dts though as mentioned above. Also there
are still opne issues to booting up all cores on an XU3 afaik. See 
   http://www.spinics.net/lists/linux-samsung-soc/msg39523.html
I haven't looked closely at the hardkernel tree to see what HMP
scheduling patches they're using, but it must be something out of tree.

Kevin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help