-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Define SDP memory area in embedded DTB #5133
Comments
Adding stuff to DT takes a bit of consideration. We don't want to define our own standard in secure world. |
I do not thing that something has already been defined for SDP in DT. But what about reserved memory which could be used to define the SDP memory ?
|
@omasse-linaro yes it is done in linaro-swg/linux branch optee, see for instance commit linaro-swg/linux@2a766ee (plus the Edit: sorry what I mentioned is the reserved shared memory not SDP :-/ but yeah could be similar. Edit 2 |
@jforissier you are right, optee-test should now rely on DMA buff heaps to test SDP. in the meantime, optee-os could use DT to define SDP and will be tested with next version of optee-test. |
Yes, fixing SDP is on @ruchi393 roadmap, but it has lower priority for the moment IIRC. |
Please find a first draft of the modifications here #5149 Tested on imx board. Unfortunately I do not have an hickey board. |
So far we have managed to avoid defining our own bindings in OP-TEE, instead we've been able to reuse already established bindings. With this you're proposing something new. I'm not sure of the best way of doing such a thing. Are we sure there is nothing to reuse? |
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
#5177 tested on hikey. |
This issue has been marked as a stale issue because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this issue will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
As an improvement, could it be possible to define the Secure Data Path memory region in an embedded dtb instead of the scattered array ?
Probably something like that:
This memory region would not rely on a core_mmu_phys_mem structure definition, but a dtb one.
The text was updated successfully, but these errors were encountered: