nvidia-tegra-modules.git/include/linux/trusty/smcall.h, branch rtss22-ae NVIDIA's kernel modules to support tegra chips (used in Jetson boards) trusty: smc_entity_guest_reset smc for hypervisor 2018-07-27T21:12:44+00:00 Steven Kao skao@nvidia.com 2016-03-18T06:17:16+00:00 af5f3aec798ad724697053b9e993fc53eefbfadd This smc is called by the hypervisor before hypervisor guest reset. VFND-1273 Bug 200145347 Change-Id: I9f599943768038c50e87e5f2b299d06099ee8a36 Signed-off-by: Steven Kao <skao@nvidia.com> Reviewed-on: http://git-master/r/1114457 (cherry picked from commit c8e2d669e69541da8bfa6ad795839f30874e2fbc) Reviewed-on: http://git-master/r/1219491 (cherry picked from commit c334664e2208dee4c1e4480da76e5f2f23f202f3) Reviewed-on: https://git-master.nvidia.com/r/1538684 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> GVS: Gerrit_Virtual_Submit 
This smc is called by the hypervisor before
hypervisor guest reset.

VFND-1273
Bug 200145347

Change-Id: I9f599943768038c50e87e5f2b299d06099ee8a36
Signed-off-by: Steven Kao <skao@nvidia.com>
Reviewed-on: http://git-master/r/1114457
(cherry picked from commit c8e2d669e69541da8bfa6ad795839f30874e2fbc)
Reviewed-on: http://git-master/r/1219491
(cherry picked from commit c334664e2208dee4c1e4480da76e5f2f23f202f3)
Reviewed-on: https://git-master.nvidia.com/r/1538684
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
GVS: Gerrit_Virtual_Submit
trusty: switch to use version 3 of TRUSTY_API 2018-07-27T21:12:44+00:00 Michael Ryleev gmar@google.com 2016-10-14T23:24:38+00:00 c9c0123938f306aeb4e066300dc8c3fcdb89b29d Version 3 of Trusty API adds support for new command (SMC_NC_VDEV_KICK_VQ) that can be used to notify virtqueue that new item is available. This command is a parameterized NOP, it has to be queued using trusty_enqueue_nop API and as such can be executed concurrently on multiple CPUs. Change-Id: Ic979e628e780fe8b0c9de5058c897c0944006615 Signed-off-by: Michael Ryleev <gmar@google.com> 
Version 3 of Trusty API adds support for new command
(SMC_NC_VDEV_KICK_VQ) that can be used to notify virtqueue
that new item is available. This command is a parameterized
NOP, it has to be queued using trusty_enqueue_nop API and as
such can be executed concurrently on multiple CPUs.

Change-Id: Ic979e628e780fe8b0c9de5058c897c0944006615
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: add support for parameterized NOP ops 2018-07-27T21:12:44+00:00 Michael Ryleev gmar@google.com 2016-10-11T18:01:14+00:00 27e57ad67ae0b76cdf94e323c07b6db90f11bea4 Parameterized NOPs are introduced by Trusty secure side to facilitate better SMP concurrency. They are effectively NOP calls with parameters that will be routed to appropriate handlers on secure side which can be executed concurrently on multiple CPUs. Parameterized NOPs are represented by trusty_nop structure that has to be initialized by calling trusty_nop_init call. This patch creates queue for such items, adds per CPU work queue to invoke them and adds API to enqueue and dequeue them. Change-Id: I4c450c3d6cc18b246dfd0ca4526ef8703c1c2d64 Signed-off-by: Michael Ryleev <gmar@google.com> 
Parameterized NOPs are introduced by Trusty secure side to
facilitate better SMP concurrency. They are effectively NOP
calls with parameters that will be routed to appropriate
handlers on secure side which can be executed concurrently
on multiple CPUs. Parameterized NOPs are represented by
trusty_nop structure that has to be initialized by calling
trusty_nop_init call. This patch creates queue for such items,
adds per CPU work queue to invoke them and adds API to enqueue
and dequeue them.

Change-Id: I4c450c3d6cc18b246dfd0ca4526ef8703c1c2d64
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: Add smp support 2018-07-27T21:12:44+00:00 Arve Hjønnevåg arve@android.com 2015-01-24T01:55:48+00:00 b2a435cf6598473a194b4f7168225420f57c218f Add an unlocked nop call to allow multiple cpus to enter trusty. Other standard calls are still serialized to avoid return codes getting mixed up. A new return code is used to indicate that the standard call is running on another cpu. Change-Id: Iccc0785138fbc3eb9daebf22fd79d6c1f9b23f6a Signed-off-by: Arve Hjønnevåg <arve@android.com> 
Add an unlocked nop call to allow multiple cpus to enter trusty.
Other standard calls are still serialized to avoid return codes
getting mixed up.
A new return code is used to indicate that the standard call is
running on another cpu.

Change-Id: Iccc0785138fbc3eb9daebf22fd79d6c1f9b23f6a
Signed-off-by: Arve Hjønnevåg <arve@android.com>
trusty: Handle fiqs without calling notifier and enabling interrupts 2018-07-27T21:12:44+00:00 Arve Hjønnevåg arve@android.com 2015-06-12T02:51:54+00:00 7abcf768d24edb227bc809d819e6b2544c496f34 Change-Id: Iab318f0efd7ca0217bd64a30918f040938af5b76 Signed-off-by: Michael Ryleev <gmar@google.com> 
Change-Id: Iab318f0efd7ca0217bd64a30918f040938af5b76
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: Select api version 2018-07-27T21:12:44+00:00 Arve Hjønnevåg arve@android.com 2015-06-12T02:34:28+00:00 4de081ad8ef79596293b299c05c2c0c67e8f2bf4 Select api version in probe, and store it in trusty_state. This enables new return codes from trusty, and will later be used to enable a nop stdcall that does not take smc_lock. Change-Id: Ib0c41b8b14e0638851d5236f83677c25507a2db6 Signed-off-by: Michael Ryleev <gmar@google.com> 
Select api version in probe, and store it in trusty_state.
This enables new return codes from trusty, and will later be used
to enable a nop stdcall that does not take smc_lock.

Change-Id: Ib0c41b8b14e0638851d5236f83677c25507a2db6
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: add trusty virtio driver 2018-07-27T21:12:44+00:00 Michael Ryleev gmar@google.com 2015-03-30T19:43:59+00:00 1db3530ea6781b888f98f5dd7724ba042a02954b Trusty virtio driver is responsible for management an interaction with virtio devices exposed by Trusty. During initialization, this driver makes an smc call to retrieve Trusty virtio device descriptor from secure side, parses it then instantiates and configures the specified set of virtio devices. Change-Id: I20a23518d5c19bedd9282f7f1d4b16957ba75408 Signed-off-by: Michael Ryleev <gmar@google.com> 
Trusty virtio driver is responsible for management an
interaction with virtio devices exposed by Trusty.
During initialization, this driver makes an smc
call to retrieve Trusty virtio device descriptor from
secure side, parses it then instantiates and configures
the specified set of virtio devices.

Change-Id: I20a23518d5c19bedd9282f7f1d4b16957ba75408
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: Add trusty logging driver. 2018-07-27T21:12:44+00:00 Riley Andrews riandrews@google.com 2016-05-05T21:42:41+00:00 751a57f1e20223d403ec77ab33e797d486e7d256 This driver is the consumer side of a ringbuffer of log data that the secure operating system dumps prints into. Trusty printfs will be dumped into the kernel log after smc calls and during panics. Change-Id: Ib4fc8b9077da5e2c628607bc6cd04dc8760dead5 Signed-off-by: Michael Ryleev <gmar@google.com> 
This driver is the consumer side of a ringbuffer of log data
that the secure operating system dumps prints into. Trusty
printfs will be dumped into the kernel log after smc calls
and during panics.

Change-Id: Ib4fc8b9077da5e2c628607bc6cd04dc8760dead5
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: arm64 fiq support 2018-07-27T21:12:44+00:00 Arve Hjønnevåg arve@android.com 2014-04-15T00:18:40+00:00 37089fcfec540f5ebe01f70f3048e850bae9d7df Change-Id: Icd7c410ea805d4f7b5318b922f269cff8a56d53e Signed-off-by: Michael Ryleev <gmar@google.com> 
Change-Id: Icd7c410ea805d4f7b5318b922f269cff8a56d53e
Signed-off-by: Michael Ryleev <gmar@google.com>
trusty: Get version string from trusty 2018-07-27T21:12:44+00:00 Arve Hjønnevåg arve@android.com 2014-10-10T04:24:17+00:00 30a030a9aff56a16e6bf4fee0ec31af7472955dd Print trusty version to kernel log on startup, and export it in sysfs. Change-Id: Ibb503a9385a223b590b882578fdd6332fc750a8d Signed-off-by: Arve Hjønnevåg <arve@android.com> 
Print trusty version to kernel log on startup, and export it in sysfs.

Change-Id: Ibb503a9385a223b590b882578fdd6332fc750a8d
Signed-off-by: Arve Hjønnevåg <arve@android.com>