-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
Support default tz_module in event loop thread for M23/M33 #6978
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 👍
@SeppoTakalo @kjbracey-arm If y'all could check the two files, that would be great. On quick glance, (and thank you for the referenced PR @cyliangtw) this looks fine to me. |
/morph build |
1 similar comment
/morph build |
Build : ABORTEDBuild number : 2275 |
Build : ABORTEDBuild number : 2279 |
Halting CI builds until RC3 PRs are completed. Will resume after. |
/morph build |
Build : SUCCESSBuild number : 2294 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 1918 |
Test : SUCCESSBuild number : 2072 |
Description
Thread class could support default tz_module of Thread attribute for M23/M33 in #6486 , however event loop & lwip will create new thread by osThreadNew(...) directly. So, to apply the same mechanism of #6486 on these 2 features. To allow event-queue's non-secure task to access secure functions.
Pull request type
@deepikabhavnani