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
77 handler will be responsible for all SMC Functions within a given service type.
83 each owning entity can place the implementation of its runtime service. The
86 Runtime service sources will need to include the ``runtime_svc.h`` header file.
88 Registering a runtime service
91 A runtime service is registered using the ``DECLARE_RT_SVC()`` macro, specifying
92 the name of the service, the range of OENs covered, the type of service and
127 During initialization the services framework validates each declared service
135 ``std_svc_setup.c`` provides an example of registering a runtime service:
139 /* Register Standard Service Calls as runtime service */
149 Initializing a runtime service
154 performs basic validation of the declared service before calling
155 the service initialization function (``_setup`` in the declaration). This
164 Error initializing runtime service <name of the service>
166 and then ignore the service - the system will continue to boot but SMC calls
167 will not be passed to the service handler and instead return the *Unknown SMC
170 If the system must not be allowed to proceed without the service, the
173 If the service uses per-CPU data this must either be initialized for all CPUs
175 service.
177 Handling runtime service requests
180 SMC calls for a service are forwarded by the framework to the service's SMC
181 handler function (``_smch`` in the service declaration). This function must have
204 the framework will forward all calls to the service handler.
231 #. Providing the service requested by the SMC Function, utilizing the
241 the implementation of the service. These are the Call Count, Implementor
242 UID and Revision Details for each service documented in section 6 of the
289 example, the Standard calls service handles ``0x84000000``-``0x8400FFFF`` and
290 ``0xC4000000``-``0xC400FFFF`` functions. Within that range, the `PSCI`_ service
292 In that respect, `PSCI`_ is a 'sub-service' of the Standard calls service. In
294 service which perform independent functions.
299 part of the SMC Function ID to identify the sub-service. TF-A does not provide
302 Secure-EL1 Payload Dispatcher service (SPD)