Skip to content

Conversation

@vstehle
Copy link
Collaborator

@vstehle vstehle commented Apr 16, 2025

On AArch64, when SCMI is implemented, in a table:

  • Require minimum protocol versions (as in SCMI 2.0)
  • Recommend minimum protocol versions (as in SCMI 3.2)

@vstehle

This comment was marked as outdated.

xypron

This comment was marked as resolved.

@vstehle

This comment was marked as resolved.

@vstehle vstehle marked this pull request as draft April 23, 2025 14:22
@vstehle vstehle marked this pull request as ready for review April 30, 2025 12:12
@xypron
Copy link
Contributor

xypron commented May 7, 2025

LGTM

Reviewed-by: @xypron

@vstehle vstehle marked this pull request as draft May 7, 2025 13:50
@vstehle

This comment was marked as outdated.

@vstehle

This comment was marked as resolved.

@vstehle

This comment was marked as outdated.

@vstehle vstehle force-pushed the scmi branch 2 times, most recently from fabe677 to f68b665 Compare September 1, 2025 13:32
@vstehle

This comment was marked as outdated.

@vstehle vstehle force-pushed the scmi branch 2 times, most recently from dc78988 to 6699c6b Compare September 17, 2025 14:20
@vstehle vstehle changed the title Conditionally require SCMI 2.x, x >= 1 recommended SCMI requirements Sep 17, 2025
@vstehle vstehle marked this pull request as ready for review September 19, 2025 16:41
@vstehle
Copy link
Collaborator Author

vstehle commented Sep 19, 2025

This is a bit refined now:

  • Broaden the requirements to all cases of transport to encompass the case of a remote processor behind a mailbox.
  • Consider all standard protocols; not only the base one.
  • Convert to a table for clarity

The requirements correspond to spec version 2.0 B. They are supported by TF-A and (almost) by OP-TEE. They should be aligned with the (upcoming) Arm SystemReady SRS 3.1 and should be sufficient for Linux, which is very permissive.

The recommendations correspond to spec version 3.2 E. They should benefit to recent Linux kernels, which default to those versions and can negotiate to some extend.

Copy link
Contributor

@xypron xypron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@vstehle
Copy link
Collaborator Author

vstehle commented Sep 24, 2025

Updated the pull request as per the EBBR call of Sep 24:

  • Reference SCMI spec v3.2, do not mention the letter, remove the telemetry protocol from the table
  • Mention v1.0 in all table fields where necessary

While at it, transform the note after the table on version negotiation into a footnote.

Add a reference to the SCMI specification v3.2, to prepare adding
requirements around SCMI.

Signed-off-by: Vincent Stehlé <[email protected]>
Add requirements on AArch64 platforms, when SCMI is implemented.
The requirements are on the minimum required and recommended versions for
the implemented SCMI protocols.
This corresponds to requiring at least SCMI 2.0 B, and ideally SCMI 3.2 E.

Signed-off-by: Vincent Stehlé <[email protected]>
@vstehle
Copy link
Collaborator Author

vstehle commented Sep 30, 2025

Rebased, and in the mean time added one missing comma to the SCMI reference.

@xypron
Copy link
Contributor

xypron commented Nov 5, 2025

I think this is good to merge. But I have not checked all the version numbers.

@vstehle
Copy link
Collaborator Author

vstehle commented Nov 5, 2025

Accepted during the EBBR call of Nov 5.

@vstehle vstehle merged commit 1fb2ef7 into ARM-software:main Nov 5, 2025
1 check passed
@vstehle vstehle deleted the scmi branch November 13, 2025 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants