https://review.trustedfirmware.org/c/trusted-firmware-m/+/2489
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2955
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 30 2019
Dec 28 2019
Dec 27 2019
Dec 26 2019
Patch for the task:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2953/1
The patch is merged, so close it.
Patches are merged, so close it.
Dec 25 2019
Hi @jf549
Any update for this ticket?
Dec 24 2019
I'm not too much versed into RAS error handling, so please take my explanation below with care.
I suggest you send the question to the TF-A ML to get more sensible insights.
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2933
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2934
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2935
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2936
Dec 23 2019
This problem had been fixed in the ticket: https://developer.trustedfirmware.org/T557
Add PSA_DOOLBELL signal to assigned_signals
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2927/
Dec 22 2019
yes, it hit a code side limit, I will check it.
Dec 20 2019
I'll post this question to mailing list as suggested.
Patches for the task:
https://review.trustedfirmware.org/q/topic:%22optional_build_sp_and_tests%22+(status:open%20OR%20status:merged)
I am not aware of any specific reason for LOG_LEVEL values being multiple of 10's. I guess at the time we thought we should leave room in between values, just in case we'd like to add more intermediate values in the future. In the end, I think it proved unnecessary but it stayed like that. I don't foresee the need for more log levels today so IMHO it would be OK to change their values to 1,2,3 and so on, as you suggested.
Bug spotted while creating test suite:
Add dependence deadlock check: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2924/
Align psa_wait() to PSA FF 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2380/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2402/
Align psa_close to psa ff 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2487/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2444/
Detect the current handling handle in psa_call
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2768/
Enhance the psa_call to process the invalid message
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2769/
Add an ipc test for psa_call
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2818/
Align psa_version to PSA FF 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2920/
As the PSA FF 1.0.0 mentioned in 3.5.2:
Add a doc about how to add a secure partition: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2921/
Dec 19 2019
Running bisect between v2.2 and master it seems this issue started from commit ab4df50c23b9 ("adding support to enable different personality of the same soc.").
I've subscribed both of you to this ticket because git blame shows you as contributors for this platform port. Sorry if you're not the right people to notify about this and feel free to bounce that back to whoever would be appropriate!
Fixed and merged on 8/10/2019:
https://git.trustedfirmware.org/TF-A/tf-a-tests.git/commit/?id=fb003380a01843d0de71ba3374394a798289c64f
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/2302 has been merged so I am closing this task.
Fixed by the following patch: https://review.trustedfirmware.org/c/TF-A/tf-a-tests/+/2834
Credit to @MarekBykowski .
If we set the LOG macros to 1,2,3 so on, we can avoid the mod and division operation when printing the msg to console.
Add additional field definition for A72 L2 control
https://review.trustedfirmware.org/#/c/TF-A/trusted-firmware-a/+/2744/
Dec 18 2019
Yes, the TZ API is not widely supported and the RTOSes which support v8m TZ are inventing their own "TZ" API for secure context switch (e.g. FreeRTOS). So, we intended to make the "Secure Context Management" ecosystem more aligned. For example, we are also introducing TZ API in RT-Thread.
But you're right, it's optional if there's no multiple secure context in TF-M. The value of NS client ID and NS access policy are use case specific. We provide the way to support that but it should be optional.
We will check if anything will go wrong if RTOS doesn't call the TZ API to TF-M. If we found issues, then will fix them.
Thanks for the valuable input!
Keep this task here since there would be another update.
Now the parameter packing method is changed and this problem is not there.
Check the patch:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2445
Now one handle could only have one message body, and this message body is allocated while handle is created. So there is no resource allocation issue for the message (we do have this problem for handle but this ticket is not the case). Close this task as done.
https://review.trustedfirmware.org/q/topic:%22dualcpu-multi-client-call%22+(status:open%20OR%20status:merged) implement multiple calls feature.
https://review.trustedfirmware.org/q/topic:%22dualcpu-test-framework%22+(status:open%20OR%20status:merged) implement a test framework for dual-cpu to verify multiple calls feature.
Dec 17 2019
TZ API is not generic - otherwise it would be widely supported by RTOSes. It is good that the implementation can be empty as there are also requirements to use TF-M without RTOS.
Patch had been merged to the master branch.
Dec 16 2019
PSA_ARCH_TEST pull request:
https://github.com/ARM-software/psa-arch-tests/pull/124
Gerrit review Patch:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2827/
The plan is:
- Will use customized implementation of 'printf' to avoid reference low-level APIs and __stdout.
- This 'printf' will call USART directly.
- SVC printf will be removed. No log output under SVC mode.
Dec 15 2019
In T615#7152, @ReinhardKeil wrote:This is related to https://lists.trustedfirmware.org/pipermail/tf-m/2019-December/000581.html.
Pictures are filed here as the email list does not support pictures.
Dec 14 2019
Related reviews:
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2814/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2815/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2816/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2817/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3046/
How can we add name? To do it we have to follow best write my essay sites where we are just waiting for those things where we just want to take from description and all which we need. So here are some simple method which tell you to add.
Dec 13 2019
This is related to https://lists.trustedfirmware.org/pipermail/tf-m/2019-December/000581.html.
Pictures are filed here as the email list does not support pictures.