Skip to content

[FEATURE] Clean up SOF DMA interface(s) #9561

Closed

Description

@kv2019i

Is your feature request related to a problem? Please describe.
DMA engines are key part of the SOF and the DMA interface are used in many place (to transfer audio data, to transfer payloads of IPC message, to implement trace, to implement debug features, and so forth).

As described in the commit message and documentation added in commit 816b143 , the transition to use native Zephyr DMA interface has been one of the complex transition tasks, and this work is not complete.

Describe the solution you'd like
This issue is used to track cleanup of the DMA usage in SOF application code with following goals:

  • remove namespace overlap between SOF and Zephyr DMA APIs, making it clear which interface is used in application code (IOW, do not mix dma_ and DMA_ prefixes in definitions)
  • retain support for transition interfaces (building SOF with Zephyr but with XTOS drivers), but move the related code to separate files and/or clearly separate namespace

Describe alternatives you've considered
One option is to wait for all targets to move to Zephyr (also to native drivers) and then DMA cleanup could be done by dropping all the legacy interfaces.

Additional context
Related to enhancement work done in #9015 and #5794

Activity

  1. added
    enhancementNew feature or request
    ZephyrIssues only observed with Zephyr integrated
    on Oct 9, 2024
  2. self-assigned this
    on Oct 9, 2024
  3. kv2019i commented on Oct 9, 2024

    @kv2019i
    CollaboratorAuthor

    FYI @DINESHKUMARK1 -- this shouldn't interfere with work to enable Zephyr (#9549), but something to be aware of.

  4. lgirdwood commented on Oct 15, 2024

    @lgirdwood
    Member

    May be easiest to do a xtos interface removal after we have all ported to Zephyr.

  5. added this to the v2.12 milestone on Oct 15, 2024
  6. lgirdwood commented on Oct 15, 2024

    @lgirdwood
    Member

    Tagged for v2.12, some parts may be doable by this point, we can break down work if needed.

  7. kv2019i commented on Dec 13, 2024

    @kv2019i
    CollaboratorAuthor

    Work in progress, but won't be complete for 2.12. Feature cutoff for v2.12, moving this to v2.13.

  8. modified the milestones: v2.12, v2.13 on Dec 13, 2024
  9. kv2019i commented on May 2, 2025

    @kv2019i
    CollaboratorAuthor

    Cleanup done for Zephyr-visible code in #9753 .

    Remaining cleanup depends on removal of XTOS in main (tracked in #9983).

    Moving this to TBD milestone. This needs to be scheduled with #9983

  10. modified the milestones: v2.13, TBD on May 2, 2025
  11. kv2019i commented on Jul 3, 2025

    @kv2019i
    CollaboratorAuthor

    Resuming, last bit in review at #10090

  12. modified the milestones: TBD, v2.14 on Jul 3, 2025
  13. kv2019i commented on Jul 4, 2025

    @kv2019i
    CollaboratorAuthor

    Closed via #10090 merge

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

Metadata

Metadata

Assignees

Labels

ZephyrIssues only observed with Zephyr integratedenhancementNew feature or request

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions