Skip to content

[FEATURE] Skip PAUSE/RELEASE test on Smart Amp playback and capture pipelines #866

Closed

Description

@mengdonglin

Is your feature request related to a problem? Please describe.
This feature is to avoid an invalid bug caused by random pause/release on two dependent smart amplifier pipelines, e.g. thesofproject/sof#4434

Describe the solution you'd like
multiple-pause-resume.sh can check if a demux/mux or a smart amplifier component is available in a pipeline. If yes, skip doing pause/release on this pipeline.

Additional context
When a mux/demux component is there, the involved pipelines have dependency. We cannot do random pause/release on them in parallel.

Activity

  1. plbossart commented on Feb 28, 2022

    @plbossart
    Member

    @mengdonglin it's not feasible to skip a test in sof-test for a specific platform, you have to do this at the CI level.

  2. marc-hb commented on Mar 1, 2022

    @marc-hb
    Collaborator

    @mengdonglin it's not feasible to skip a test in sof-test for a specific platform,

    Why not, can you elaborate? I just did something I think is like it: ae421827a419cdef0ea

  3. mengdonglin commented on Mar 1, 2022

    @mengdonglin
    ContributorAuthor

    @plbossart @marc-hb I think we have 2 options:

    Option 1: Topology parser will check if there is a demux/mux component in the pipeline. If yes, skip doing pause/release on this pipeline. And we can still do pause/release other pipelines. This is preferred solution atm.

    Option 2: CI can skip multiple-pause-resume.sh for both TGLU_VOLT_SDW and ADLP_BRYA_SDW.

  4. plbossart commented on Mar 1, 2022

    @plbossart
    Member

    @marc-hb I don't understand your point and why we would add such work-around in sof-test.

    My point is that we don't want to encode which devices are used for smart-amp capture in the test. You can disable capture if you want, but you disable ALL capture devices then. Going to the lower level details makes no sense and is dependent on topology.

  5. marc-hb commented on Mar 1, 2022

    @marc-hb
    Collaborator

    I don't understand your point

    I don't know what point I'm trying to make, I'm merely asking why something can't or shouldn't be done.

    and why we would add such work-around in sof-test.

    If some configuration is not supported then it should not be tested; this is not a "workaround". Now there is of course the recurring problem that sof-test has neither a test runner nor a default test plan, at least none open-source and integrated but that's a different question.

    My point is that we don't want to encode which devices are used for smart-amp capture in the test.

    Agreed.

    Going to the lower level details makes no sense and is dependent on topology.

    We already have plenty of code in sof-test to analyze topologies:

    EDIT: the discussion at the bottom of this seems related

  6. keqiaozhang commented on Mar 1, 2022

    @keqiaozhang
    Contributor

    I submitted a simple PR #871 to skip the PAUSE/RELEASE test on Smart Amp playback and Echo Reference capture pipelines.
    This PR will only filter out these 2 pipelines and the rest of pipelines will still be tested.

  7. mengdonglin commented on Mar 20, 2022

    @mengdonglin
    ContributorAuthor

    Close this issue as PR #871 got merged.

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

Metadata

Metadata

Assignees

Labels

P1Blocker bugs or important features

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions