schemas: Add Google Widevine initialization parameters #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The necessary fields to initialize the widevine related functions in OP-TEE. Signed-off-by: Yi Chou <yich@google.com> Reviewed-by: Simon Glass <sjg@chromium.org>
qazwsxedcrfvtg14
changed the title
|
Please send this to the devicetree-spec list like the last version. I don't see an answer to my question whether there's more optee stuff coming or this is it? |
|
Sent this to the devicetree-spec list: And there's no plan to add more optee stuff now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The necessary fields to initialize the widevine related functions in OP-TEE.
I'm writing to follow up on our previous discussions regarding the placement of the DT binding file for OP-TEE.
We believe that this file would be more appropriately located in the dt-schema repository, as it aligns with the similar use case for U-boot that is already present there.
For reference, here are the links to the relevant discussions and code:
The DT usage in the OP-TEE:
OP-TEE/optee_os#6379
The TF-A CL:
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/20442/19
The previous discussions in the linux kernel mailing list:
https://lore.kernel.org/all/20230918194235.GA1548023-robh@kernel.org/
https://lore.kernel.org/all/CABOkjxJwT3zZfgsK8oiubQVZCZDPg6mJ8Et99yAyanp7oOLPmg@mail.gmail.com/