Lines Matching full:tee

92  * facilitate isolated communicaiton with TEE.
94  * to TEE direct communication to perform various TEE centric operations
96  * TEE for other usages, providing TEE capabilities etc.
99  * TEE/GPU/Display for HWDRM playback.
101  * The difference between Protected Content and Protected TEE Communication
103  * point for TEE and invokes TEE only from HWDRM perspective.
115  * Execution Environment (TEE) to prepare client platform or system for DRM
117  * instructed in DRM standard) and client system TEE. The communication between
118  * provisioning servers and client system TEE uses asymmetic cryptographic
123  * servers and TEE using asymmetic cryptographic mechanism. At end of this step,
124  * client system TEE has required assets to decrypt/decode. Although these
136  * communicate with TEE and then using these protected sessions to process
140  * Note: TEE could be any secure HW device such as ME-FW or FPGA Secure
141  * Enclave or NPU Secure Enclave. There are 2 concepts here – TEE Type such
142  * as ME-FW or FPGA or NPU; TEE Type Client such as for AMT or HDCP or
147  * protected session with TEE and if required then \ref priming GPU/Display.
149  * configuration of protected session. Just for TEE tasks, protected
150  * session is parameterized/configured as TEE Communication while for
154  * TEE Communication Entrypoint
155  * With TEE Communication parameterization/configuration, client
156  * executes TEE workloads in TEE with TEE Communication protected
177  * if license acquisition is being performed then priming means that TEE is
178  * already provisioned aka TEE has some sort of "cryptographic" whitelist of
179  * servers that TEE will use to do license acquisition for video playback. If
181  * eco-system TEE/GPU/Display has proper keys to do proper video playback etc.
248  * TEE Communication Entrypoint
249  * The protected content session provides a TEE session that is used to extract
250  * TEE information. This information could be used to peform TEE operations.
284  * \subsection api_pc_exec TEE communication via vaProtectedSessionExecute()
286  * TEE Communication Entrypoint
287  * App needs to communicate with TEE to get TEE information or \ref priming
288  * "prime" TEE with  information that will be utilized for future TEE
293  * communicate  with TEE to get encrypted assets for \ref priming HWDRM pipeline
298  * In this example, the vaCreateBuffer is called with exec_buffer mainly becasue TEE
396  * The returned protected_session represents a notion of Host and TEE clients
404 /** \brief TEE Execucte Function ID. */
444     /** \brief - vtag represents TEE sandbox identification for multiple playback scenario
446      * If TEE interface is created using VAEntrypointProtectedTEEComm then
449      * If TEE interface is not created using VAEntrypointProtectedTEEComm then
500  * @param[in] id                    TEE client id to be detached
505  * \brief Execute provides a general mechanism for TEE client tasks execution.
507  * vaProtectedSessionExecute provides a mechanism for TEE clients to execute