Skip to content

[FEATURE] Add ABI versioning to IPC4 interface #9080

Open

Description

@kv2019i

Is your feature request related to a problem? Please describe.
SOF has established ABI process for IPC3 extensions -> https://thesofproject.github.io/latest/contribute/process/abiprocess.html

We do not have same for IPC4 yet and no guidelines how to push IPC4 changes through the process. With release of SOF2.7, we now have first shipping product that is using SOF IPC4 interface (Intel Meteor Lake), so there is now also the need to track ABI extensions. Notably, FW currently sets:

#define SOF_ABI_MAJOR 3
#define SOF_ABI_MINOR 30

... and there's no way to describe IPC4 version.

Describe the solution you'd like
Something like IPC3.

Describe alternatives you've considered

Additional context
Triggered by review of #9032

Activity

  1. kv2019i commented on Apr 24, 2024

    @kv2019i
    CollaboratorAuthor
  2. added
    ABIABI change involved
    IPC4Issues observed with IPC4 (same IPC as Windows)
    on Apr 24, 2024
  3. kv2019i commented on Apr 24, 2024

    @kv2019i
    CollaboratorAuthor

    FYI to SOF Linux driver folks @plbossart @ranj063 @bardliao @ujfalusi

  4. changed the title [-][FEATURE] Add ABI versinoning to IPC4 interface[/-] [+][FEATURE] Add ABI versioning to IPC4 interface[/+] on Apr 24, 2024
  5. lgirdwood commented on Apr 25, 2024

    @lgirdwood
    Member

    Ack, we can do the same as IPC3 - i.e. we label and create a github project to do semantic versioning of IPC4 ABI in a backwards compatible manner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ABIABI change involvedIPC4Issues observed with IPC4 (same IPC as Windows)enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions