On Thu, Jan 07, 2016 at 04:06:55PM +0100, Michal Simek wrote:
On 6.1.2016 14:04, Mateusz Kulikowski wrote:
On 14.10.2015 18:55, Sergey Temerkhanov wrote:
This commit adds functions issuing calls to secure monitor or hypervisore. This allows using services such as Power State Coordination Interface (PSCI) provided by firmware, e.g. ARM Trusted Firmware (ATF)
The SMC call can destroy all registers declared temporary by the calling conventions. The clobber list is "x0..x17" because of this
Signed-off-by: Sergey Temerkhanov s.temerkhanov@gmail.com Signed-off-by: Corey Minyard cminyard@mvista.com Signed-off-by: Radha Mohan Chintakuntla rchintakuntla@cavium.com Reviewed-by: Simon Glass sjg@chromium.org
+1 (I may need it as well)
Tested-by: Mateusz Kulikowski mateusz.kulikowski@gmail.com
Tested on: Hikey Methodology:
Hacked smc handler in arm trusted firmware (x0=x0+x1, x1=x2+x3, x2=x4+x5, x3=x6+2) +new u-boot command (smc/hvc) using functions from this patch;
I didn't tested hvc code (would need to make some fake hypervisor), but it's basically the same.
Idea: perhaps after this series is merged we can add 2 new commands to u-boot (SMC/HVC) to play with hypervisors/secure monitors (and perhaps use some simple functionality if needed).
How this should look like?
Definitely I would like to see this code in mainline because we have code which needs to call SMCs.
I guess the answer is we either need the cavium board series re-posted without the device-tree binding change that is causing consternation elsewhere or come up with something else there, or I just pull parts of the series. I'm not quite sure which is best at this point..