We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The TEE Internal Core API specification for function TEE_SetTAPersistentTime() mentions:
TEE_SetTAPersistentTime()
The modification is atomic and persistent across device reboots.
The current implementation keeps time offsets in memory and therefore does not comply to the requirement.
The text was updated successfully, but these errors were encountered:
Upon executing xtest 1006, i see the log from https://github.com/OP-TEE/optee_test/blob/master/ta/os_test/os_test.c#L577 is this log expected and related to this bug?
xtest 1006
Sorry, something went wrong.
Furthermore, after https://github.com/OP-TEE/optee_test/blob/master/ta/os_test/os_test.c#L592, TA time is printed as TA time 0.000. It's a bit confusing because TEE_GetTAPersistentTime() returned with TEE_SUCCESS and isn't populating the time!!
TA time 0.000
TEE_SUCCESS
@Sadiq1811 what you are observing is perfectly normal.
TEE_GetTAPersistentTime()
TEE_ERROR_TIME_NOT_SET
0.000
No branches or pull requests
The TEE Internal Core API specification for function
TEE_SetTAPersistentTime()
mentions:The current implementation keeps time offsets in memory and therefore does not comply to the requirement.
The text was updated successfully, but these errors were encountered: