| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The omap4xxx projects are supposed to be buildable only for OMAP4 and
OMAP5 but not OMAP3.
This patch adds checking for the proper TARGET_BOARD_PLATFORM to the
root Android.mk and removes useless double checking from subprojects.
Change-Id: Ic103304d24c2ffdbb82b3a277d0b66e0e44e4bc0
Signed-off-by: Daniel Levin <dendy@ti.com>
Conflicts:
Android.mk
security/smc_pa_ctrl/Android.mk
security/tee_client_api/Android.mk
security/tf_daemon/Android.mk
|
| |
|
|
|
|
|
| |
- Align LDFLAGS to previous versions for easier comparison of changes
- Remove Android logging
Change-Id: Ib8242be6be3411fb7277147ca08d68e9fbb45b67
|
| |
|
|
|
| |
Bug: 18675947
Change-Id: I07a35782fa2f021574c4ec937920448288594288
|
| |
|
|
|
| |
Change-Id: I0cf5da4d3b5653244b8ffe9178d45c3582b48897
Signed-off-by: Mike J. Chen <mjchen@google.com>
|
|
|
libtf_crypto_sst.so is a single shared object where the Normal
World APIs are implemented for Secure Storage, Cryptographic, and
Monotonic Counter Facility. These are the "Core Secure Services"
The crypto core secure service exposing crypto functionality
for client applications supports exactly the same mechanisms as the
ones exposed by the Internal PKCS#11 SSDI Crypto API.
In order to optimize some cryptographic operations from the External
cryptoki API, the SMC makes use of the Cryptographic HW Accelerators
in public mode (in the SMC driver), through the Cryptoki Update
Shortcut (CUS) and the aggressive mode.
Change-Id: I3ebf83a0c84fb33f0f779a6224032b7aad06ef45
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
Signed-off-by: Trusted Logic <smc_support@trusted-logic.com>
|
