| 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>
|
|
|
|
|
|
|
|
|
|
| |
Choose correct llog by changing LOCAL_LDFLAGS to LOCAL_LDLIBS
for llog.
(cherry picked from commit ead6372c32dd20ee4de99ee3a2d6673e3274a861)
Change-Id: I86164615edf114d2fdc6a633561c6ce6641afb2e
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
|
|
|
|
|
|
|
| |
Remove sdrv_crypto.h
(cherry picked from commit d45edb436df2990e792f4ce375e197143de3e201)
Change-Id: I85ba6afccf55afd3a5e5c68a5329a09cbfef98d7
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
These three components have not changed with this release.
Only changing version header for clarity.
(cherry picked from commit 54cc5c655243e9bb73763040c8a04cdc366aa25e)
Change-Id: Ife51d93403429513bc6a99adccb2f2c88184b0e4
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The TEE Client API defines a communications API for connecting
Client Applications running in a rich operating environment with
the Secure Services running inside the Trusted Foundations execution
environment.
The TEE Client API is a static library that must be linked with the
calling application or library.
The TEE Client API is used to implement higher-level APIs, such as
cryptography or secure storage.
(cherry picked from commit ccc83471b660f62b65fbc8f566e8a7e404c64540)
Change-Id: I4f1d40ddf8fb9eec0b62e2982fc0e25db36ce6a0
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
Signed-off-by: Yong Zhi <y-zhi@ti.com>
Signed-off-by: Jorge E. Solano <x0062302@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This contains the C header files for compiling both the normal-world and
secure-world software. The rest of the SDK is available in the mshield
package.
Some of these headers are:
cryptoki.h - definitions for the External Cry ptographic API
sst.h - definitions for the External Secure Storage API
mtc.h - definitions for the External Monotonic Counter API
ssdi.h - definitions for SSDI
tee_client_api.h - definitions for the TF Client API
(cherry picked from commit 41ab3216ed1b54184d0575ef9601394e7ba53f0d)
Change-Id: I24828f423456ac12f014a406acee42b60b40ae17
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The user-space SMC Daemon is takes care in particular of the effective
storage of the SMC secure storage within the device file system. The files
in which the SMC persistent data are stored are defined in the
Normal-World Configuration File.
All the security properties such as confidentiality, integrity, atomicity,
anti-rollback and bounding to the device are managed at the SMC PA level.
(cherry picked from commit c08b0dc330e67f33fa0a8fb9c62f38b07a9103c9)
Change-Id: I62714c8bb3b43ef2897a4b0efd49f88700a1ce55
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
A user-land tool application used to install the signed SMC PA in the
Secure Environment. This application is just needed for the startup of the
SMC PA then it is no longer running.
(cherry picked from commit b6f0610ea54d990c121761a11e543e716a63c7ec)
Change-Id: I01c02f192b843bf8b8f1b12055c828d9b8e5ff12
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Modifying the Android.mk files in the security area to ensure that
they are only run for OMAP4/5. They are not used by OMAP3 and this
patch ensures that they will not be compiled for customer boards.
Change-Id: I245f77280de2ba079104b36649f314b682f0f5bb
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Andrii Beregovenko <a.beregovenko@ti.com>
Signed-off-by: Daniel Levin <dendy@ti.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>
|
|
|
|
| |
Change-Id: I6ff0478e34b0782265474bc2d0ddc0b80cf185dd
|
|
|
|
|
|
|
|
| |
Enable the build of the SMC userspace components if a device has the
BOARD_USES_SECURE_SERVICES flag enabled in a configuration file.
Change-Id: Iadbd38bbf7d7d0495541c995f38919b3a8dee055
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
|
|
These userspace components are used to load secure services in the normal
(non-secure) world. The SMC kernel driver is required to use these binaries.
Secure services enable certain security features such as
hardware-accelerated crypto, secure storage, drm, and much more.
Author: "Trusted Logic <smc_support@trusted-logic.com>." Gerrit refuses to
accept.
Change-Id: Ie81604d3fee31abc319643401c3cc66888f9f848
Signed-off-by: Bryan Buckley <bryan.buckley@ti.com>
Signed-off-by: Trusted Logic <smc_support@trusted-logic.com>
|