On Wed, 13 Feb 2019 16:42:19 +0100, Paul Menzel wrote:
Dear Takashi,
On 02/13/19 16:12, Takashi Iwai wrote:
On Wed, 13 Feb 2019 15:58:44 +0100, Paul Menzel wrote:
Why the i915 driver gets initialized *so late*?
Maybe, because it’s built as a module?
$ grep I915 /boot/config-4.20.8.mx64.245 CONFIG_DRM_I915=m # CONFIG_DRM_I915_ALPHA_SUPPORT is not set CONFIG_DRM_I915_CAPTURE_ERROR=y CONFIG_DRM_I915_COMPRESS_ERROR=y CONFIG_DRM_I915_USERPTR=y # CONFIG_DRM_I915_GVT is not set CONFIG_SND_HDA_I915=yThat explains. You built the HD-audio as built-in while the graphics as module. This makes the binding impossible at the time of sound driver initialization.
If you build the graphics driver as a module, built the sound driver also as a module.
Can this be enforced by the Kconfig configuration?
This is the restriction only needed if i915 HDMI audio is used, so you can't stop the configuration statically. Your setup would still work except for HDMI, for example.
If not, should the warning/error message be extended with this hint?
Possible, but why such a weird configuration at the first place...?
Takashi