Lines Matching full:calls
32 example a subset of the Function IDs are designated as "OEM Calls" (see [SMCCC]
43 IDs, Owning Entity Numbers (OEN), Fast and Standard calls, and the SMC32 and
54 with the SMC call type, which is either _Fast_ or _Standard_. Fast calls are
55 uninterruptible whereas Standard calls can be pre-empted. The majority of
56 Owning Entities only have allocated ranges for Fast calls: Standard calls are
61 Fast 0 ARM Architecture calls
62 Fast 1 CPU Service calls
63 Fast 2 SiP Service calls
64 Fast 3 OEM Service calls
65 Fast 4 Standard Service calls
67 Fast 48-49 Trusted Application calls
68 Fast 50-63 Trusted OS calls
70 Std 0- 1 Reserved for existing ARMv7 calls
71 Std 2-63 Trusted OS Standard Calls
78 within the SiP Service calls OEN range to mean different things - as these
79 calls should be specific to the SoC. The Standard Runtime Calls OEN is used for
85 rejects invalid calls that use the SMC64 calling convention but that originate
147 /* Register Standard Service Calls as runtime service */
173 and then ignore the service - the system will continue to boot but SMC calls
188 SMC calls for a service are forwarded by the framework to the service's SMC
207 state. SMC Calls can be made from both the normal and trusted worlds and
208 the framework will forward all calls to the service handler.
219 3. Truncating parameters for calls made using the SMC32 calling convention.
220 Such calls can be determined by checking the CC field in bit[30] of the
225 For such calls, the upper bits of the parameters x1-x4 and the saved
269 example, the Standard calls service handles `0x84000000`-`0x8400FFFF` and
272 In that respect, [PSCI] is a 'sub-service' of the Standard calls service. In
273 future, there could be additional such sub-services in the Standard calls
289 between the normal and secure worlds, deliver SMC Calls through to Secure-EL1
