lkml.org 
[lkml]   [2018]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
Subject[Question] vendor-specific cpu enable-method
Hello.


Sorry if I am asking a stupid question.


For arm64, there are only 2 cpu methods, psci and spin-table.

Why do we still allow vendor-specific methods upstreamed
for arm 32bit ports?

To me, it looks like SoC vendors continue inventing
different (but similar) ways to do the same thing.

It is a historical reason for old platforms.

However, if I look at Documentation/devicetree/bindings/arm/cpus.txt
enable-method properties are still increasing.


psci is available in arch/arm/kernel/psci_smp.c,
but not all SoCs support the security extension.
Is there a simpler one like spin-table available for arm32?

If we force generic methods like psci or spin-table
for new platforms, we can stop proliferated smp code.
(Of course, we are just shifting the complexity
from the kernel to firmware.)

Am I missing something?


--
Best Regards
Masahiro Yamada

\
 
 \ /
  Last update: 2018-09-13 03:25    [W:0.035 / U:8.688 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site