Skip to content

failed to get afg sub nodes on ChromeOS devices #1642

Closed

Description

@kv2019i

Multiple sightings have been reported of failure to probe the HDMI codec in i915 at boot, specifically on ChromeOS devices and a recent 5.4/5.5 kernel.

Error logs:
[ 79.756783] snd_hda_codec_hdmi ehdaudio0D2: HDMI: failed to get afg sub nodes
[ 79.756800] snd_hda_codec_hdmi ehdaudio0D2: patch failed -22
[ 79.756862] snd_hda_codec_hdmi ehdaudio0D2: ASoC: failed to probe
component -22
[ 79.756930] bxt_da7219_max98357a glk_da7219_max98357a: ASoC: failed
to instantiate card -22
...
[ 79.769445] bxt_da7219_max98357a: probe of glk_da7219_max98357a failed with error -22

Fixes to #1001 , #1183 and #1374 do not help as e.g. 5.5-rc1 has all the fixes included and the error still happens.

Activity

  1. added
    bugSomething isn't working
    GLKApplies to Gemini Lake
    ChromeRelated to Chrome integration
    JSLJasper Lake platform issues
    on Dec 19, 2019
  2. self-assigned this
    on Dec 19, 2019
  3. kv2019i commented on Dec 19, 2019

    @kv2019i
    CollaboratorAuthor

    FYI @yongzhi1 and @cujomalainey
    I've still not been able to reproduce this myself on any device (including a GLK device running ChromeOS, but will continue to try ith this one). As it seems we have to gather sightings and data from a larger set of devices, filing a bug for tracking.

  4. added
    HDAApplies to HD-Audio bus for codec connection
    on Dec 19, 2019
  5. kv2019i commented on Dec 30, 2019

    @kv2019i
    CollaboratorAuthor

    @yongzhi1 and @cujomalainey -- I've now reproduced the issue on a GLK Chromebook using a kernel module load-unload stress test.

    Flow-wise there is nothing wrong in the sequence, but I did notice a slight difference between legacy-HDA and SOF drivers. If I add an extra GET_PARAMETERS HDA verb to the SOF flow (right after power-up) to imitate what happens with legacy HDA driver, the errors are gone. I'll continue investigating (why this flow change helps and how to turn it into a upstream-acceptable fix).

  6. kv2019i commented on Jan 3, 2020

    @kv2019i
    CollaboratorAuthor
  7. cujomalainey commented on Jan 7, 2020

    @cujomalainey

    Been trying to bisect this but failures go back pretty far. Your branch by itself is fine.

  8. kv2019i commented on Jan 10, 2020

    @kv2019i
    CollaboratorAuthor

    It seems the above fix does not work on all Bobba devices. I posted a 2nd experimental patch to the above branch:
    kv2019i@b3c8d21
    https://github.com/kv2019i/linux/tree/topic/cras/l5.4-glk-hdmi-afg-fix
    ... waiting to gather more data whether this helps. Still no signs of this issue in CI or from other reporters.

  9. cujomalainey commented on Jan 10, 2020

    @cujomalainey

    @kv2019i probe works with that second patch and I get devices 😺

    I cherry-picked over the top 2 commits to sof-dev and I have playback again. Thanks so much.

  10. kv2019i commented on Jan 13, 2020

    @kv2019i
    CollaboratorAuthor

    @cujomalainey wrote

    @kv2019i probe works with that second patch and I get devices 😺

    I cherry-picked over the top 2 commits to sof-dev and I have playback again. Thanks so much.

    Excellent! 😎 I'll start working out an upstream-worthy patchset. 2nd patch should be easy, but first one may require some more effort to get through.

  11. 52 remaining items

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

Metadata

Metadata

Assignees

Labels

ChromeRelated to Chrome integrationGLKApplies to Gemini LakeHDAApplies to HD-Audio bus for codec connectionJSLJasper Lake platform issuesP2Critical bugs or normal featuresTGLApplies to Tiger Lake platformbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions