Lines Matching full:services

28 Secure services (aka `Service`) is the component providing secure
30 acts as a client when it is accessing its depending services.
32 Services are grouped into `Secure Partition` (aka `partition`). A partition:
34 - Contains services with the same purpose.
39 usage. Clients access services by `SID` or `Handle` through FF-M `Client API`.
100   `IPC model implementation` can handle access to the services in the `SFN`
121 services in one step, an `NSPE` client needs to cross the secure boundaries
150   - These components can provide services: SFN Partition, IPC partition, and
151     built-in services. A built-in service is built up with SPM together.
152   - All partition services must be accessed by `Client API`.
154   - Built-in services are strongly recommended to be accessed by `Client API`.
156   - Built-in services can call SPM internal interfaces directly.
260 - The partition initialization routine can access its depending services.
309 depending services during initializing, then this procedure is a
326    access depending services to prepare the response. It also can wait for
475 - The client is blocked when accessing services are handling a service
484 services inside an IPC partition.
640 - It does not provide FF-M aligned secure services.
644 - It requires specific services and mechanisms compared to common partitions.
659 - Wait in the veneer code, and get executed when NSPE accesses services.
677 - It converts received RPC events into FF-M API call to target services.
681 - It parses RPC messages to know which NSPE thread is accessing services.
689 A partition is a set of services in the same scope. Services are generally
690 implemented as functions, and the partition exposes the services in different
710 Each partition has different numbers of dependencies and services, this makes
770     * - Services and Secure Partition