From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: Re: sound/pci/hda/patch_hdmi.c:1086: undefined reference to `snd_hda_get_num_devices'
Date: Thu, 6 Feb 2020 11:05:28 -0600 [thread overview]
Message-ID: <02d655fe-dd21-3fcb-6f5d-4ecde51f3240@linux.intel.com> (raw)
In-Reply-To: <s5hr1z7q12m.wl-tiwai@suse.de>
On 2/6/20 7:48 AM, Takashi Iwai wrote:
> On Thu, 06 Feb 2020 14:40:17 +0100,
> Kai Vehmanen wrote:
>>
>> Hey,
>>
>> On Thu, 6 Feb 2020, kbuild test robot wrote:
>>
>>> ld: sound/pci/hda/patch_hdmi.o: in function `intel_not_share_assigned_cvt':
>>>>> sound/pci/hda/patch_hdmi.c:1086: undefined reference to `snd_hda_get_num_devices'
>>>>> ld: sound/pci/hda/patch_hdmi.c:1098: undefined reference to `snd_hda_get_dev_select'
>>>>> ld: sound/pci/hda/patch_hdmi.c:1099: undefined reference to `snd_hda_set_dev_select'
>>
>> hmm, this seems similar case as the previous one today w.r.t
>> hda_dsp_common.c:76. Patch_hdmi.c is built-in while snd-hda is a module.
>> Maybe we need to just drop the dependency from the ASoC board files to
>> SND_HDA_CODEC_HDMI. We don't have one for SND_HDA_CODEC either.
>
> The problem is that SOF tries to do reverse-select the legacy HD-audio
> codec, but it doesn't work in general. Or it must be done very
> carefully.
>
> If something gets selected, all dependencies have to be
> reverse-selected, too. But the legacy HDA is built up in a way of
> standard top-down selection (i.e. SND_HDA_CODEC_* depends on SND_HDA,
> not other way round).
It's the same issue as the other one reported earlier, and adding the
dependency on SOF_HDA makes the unmet dependency go away.
prev parent reply other threads:[~2020-02-06 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 10:43 kbuild test robot
2020-02-06 13:40 ` Kai Vehmanen
2020-02-06 13:48 ` Takashi Iwai
2020-02-06 17:05 ` Pierre-Louis Bossart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02d655fe-dd21-3fcb-6f5d-4ecde51f3240@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®