Lines Matching refs:service

7 This document describes how to add a runtime service to the EL3 Runtime
17 SMC Functions are grouped together based on the implementor of the service, for
24 dispatched to their respective service implementation - the
80 handler will be responsible for all SMC Functions within a given service type.
86 each owning entity can place the implementation of its runtime service. The
89 Runtime service sources will need to include the ``runtime_svc.h`` header file.
91 Registering a runtime service
94 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
95 the name of the service, the range of OENs covered, the type of service and
130 During initialization the services framework validates each declared service
138 ``std_svc_setup.c`` provides an example of registering a runtime service:
142     /* Register Standard Service Calls as runtime service */
152 Initializing a runtime service
157 performs basic validation of the declared service before calling
158 the service initialization function (``_setup`` in the declaration). This
167     Error initializing runtime service <name of the service>
169 and then ignore the service - the system will continue to boot but SMC calls
170 will not be passed to the service handler and instead return the *Unknown SMC
173 If the system must not be allowed to proceed without the service, the
176 If the service uses per-CPU data this must either be initialized for all CPUs
178 service.
180 Handling runtime service requests
183 SMC calls for a service are forwarded by the framework to the service's SMC
184 handler function (``_smch`` in the service declaration). This function must have
207    the framework will forward all calls to the service handler.
234 #. Providing the service requested by the SMC Function, utilizing the
244    the implementation of the service. These are the Call Count, Implementor
245    UID and Revision Details for each service documented in section 6 of the
292 example, the Standard calls service handles ``0x84000000``-``0x8400FFFF`` and
293 ``0xC4000000``-``0xC400FFFF`` functions. Within that range, the `PSCI`_ service
295 In that respect, `PSCI`_ is a 'sub-service' of the Standard calls service. In
297 service which perform independent functions.
302 part of the SMC Function ID to identify the sub-service. TF-A does not provide
305 Secure-EL1 Payload Dispatcher service (SPD)
330 .. _ARM SiP Services: arm-sip-service.rst
331 .. _Vendor Specific EL3 Monitor Service Calls: ven-el3-service.rst