https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_372/fi-tgl-u/igt@kms_hdmi_inject@inject-audio.html Starting subtest: inject-audio Test requirement not met in function hdmi_inject_audio, file ../tests/kms_hdmi_inject.c:145: Test requirement: eld_is_supported() Subtest inject-audio: SKIP (0.000s)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@kms_hdmi_inject@inject-audio - skip - Test requirement: eld_is_supported(), SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_372/fi-tgl-u/igt@kms_hdmi_inject@inject-audio.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_372/fi-tgl-u2/igt@kms_hdmi_inject@inject-audio.html
I just cross-checked the test, kms_hdmi_inject.c. This test is supposed to be running for a disconnected HDMI display, so that it can insert a known EDID, and can check if the EDID parsing is correct. Now, the test is looking for an alsa sound card entry in /proc/asound/card*/eld#*, without which it assumes that ELD is not supported in this platform, and seems it's not getting that. This can be again a setup issue or an audio issue.
(In reply to shashank.sharma@intel.com from comment #2) > I just cross-checked the test, kms_hdmi_inject.c. This test is supposed to > be running for a disconnected HDMI display, so that it can insert a known > EDID, and can check if the EDID parsing is correct. > > Now, the test is looking for an alsa sound card entry in > /proc/asound/card*/eld#*, without which it assumes that ELD is not supported > in this platform, and seems it's not getting that. This can be again a setup > issue or an audio issue. @Filip, any comments from audio team?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/433.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.