Skip to content

Enable SOF driver to support DP-MST (DisportPort's Multi-Stream Transport) #136

Closed

Description

@mengdonglin
No description provided.

Activity

  1. added
    enhancementNew feature or request
    P2Critical bugs or normal features
    on Sep 16, 2018
  2. libinyang commented on Feb 27, 2019

    @libinyang

    DPMST hub mode works. And daisy chain mode can't be tested as the display is unstable. Will try to find why display is not stable.

  3. libinyang commented on Mar 11, 2019

    @libinyang

    Daisy-chain mode works after using another Dell model moniter. (u2414Hb REV A01).
    Now the status is: Daisy-chain mode works, DP-MST hub mode works. DP-MST with HDMI (3 monitors) doesn't work. Can't playback the third PCM.

  4. libinyang commented on Mar 12, 2019

    @libinyang

    Now Now HDMI together with DPMST both works after I used the latest topology.

  5. mengdonglin commented on Mar 13, 2019

    @mengdonglin
    Author

    @libinyang could you share your recipe (kernel, firrmware branch/commit and topology m4) for testing on UP2?

  6. lgirdwood commented on Mar 14, 2019

    @lgirdwood
    Member

    @libinyang since this is a non trivial recipe, can you add some detail on enabling this in sof-docs.

  7. libinyang commented on Mar 24, 2019

    @libinyang

    @libinyang since this is a non trivial recipe, can you add some detail on enabling this in sof-docs.

    @lgirdwood
    I would like to. Where can I get the sof-docs and add the information to?

  8. libinyang commented on Mar 24, 2019

    @libinyang

    Now DPMST works very well with different DPMST modes, differnent DPMST hub on different platforms.
    Here is the summary for the DPMST:

    kernel: 41e4680
    SOF: 52f99da
    tplg: 52f99da

    Platforms: UP2, WHL are both OK
    mode: DPMST, Daisy-chain mode are both OK
    DPMST hub: club, StarTech are both OK (StarTech has compatibility issue with monitors)
    DPMST + HDMI mode: is OK
    DPMST S3: is OK (after HDMI S3 RFC patches are merged)

  9. plbossart commented on Mar 24, 2019

    @plbossart
    Member

    @libinyang you clearly found a problem for S3 that needs to be fixed and that's really good progress. However, the feedback from Takashi is clearly that a different solution needs to be found. Are you working on an update? I'd rather merge an update or better yet get the solution through the weekly alsa-devel backport than take the existing patches as is and revert.

    Also what topology did you use on Up2?

  10. libinyang commented on Mar 25, 2019

    @libinyang

    @plbossart Yes, I'm working on it. I will check whether Takashi's solution is reasonable to implement. I will work on it today. I didn't give the updated patch last 2 days because I don't have environment at home to test to see if Takashi's suggestion is feasible.

    tplg: 52f99da

    @libinyang you clearly found a problem for S3 that needs to be fixed and that's really good progress. However, the feedback from Takashi is clearly that a different solution needs to be found. Are you working on an update? I'd rather merge an update or better yet get the solution through the weekly alsa-devel backport than take the existing patches as is and revert.

    Also what topology did you use on Up2?

  11. plbossart commented on Mar 25, 2019

    @plbossart
    Member

    tplg: 52f99da

    I was asking about the topology filename (HDMI alone or PCM512-hdmi?)

  12. libinyang commented on Mar 25, 2019

    @libinyang

    @plbossart

    It is sof-apl-pcm512x.tplg.

  13. mengdonglin commented on Mar 28, 2019

    @mengdonglin
    Author

    Close this issue based on #136 (comment)
    We can track HDMI audio failure after S3 by #737 and #489

  14. added a commit that references this issue on May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2Critical bugs or normal featuresenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions