public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Nathan Chancellor <nathan@kernel.org>,
	kernel test robot <lkp@intel.com>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
	Bard Liao <bard.liao@intel.com>
Subject: Re: ld.lld: error: undefined symbol: iosf_mbi_available
Date: Thu, 18 Jul 2024 17:16:54 +0200	[thread overview]
Message-ID: <69dfb1e2-eac6-4cd4-a9d3-caaa7f36f9b9@linux.intel.com> (raw)
In-Reply-To: <87frs6vj4m.wl-tiwai@suse.de>


>>>> diff --git a/sound/soc/intel/common/soc-intel-quirks.h
>>>> b/sound/soc/intel/common/soc-intel-quirks.h
>>>> index de4e550c5b34..ae67853f7e2e 100644
>>>> --- a/sound/soc/intel/common/soc-intel-quirks.h
>>>> +++ b/sound/soc/intel/common/soc-intel-quirks.h
>>>> @@ -11,7 +11,9 @@
>>>>
>>>>  #include <linux/platform_data/x86/soc.h>
>>>>
>>>> -#if IS_ENABLED(CONFIG_X86)
>>>> +#if IS_ENABLED(CONFIG_X86) && \
>>>> +       (IS_ENABLED(CONFIG_SND_SOC_SOF_BAYTRAIL) || \
>>>> +        IS_ENABLED(CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI))
>>>>
>>>>  #include <linux/dmi.h>
>>>>  #include <asm/iosf_mbi.h>
>>>>
>>>> also at https://github.com/thesofproject/linux/pull/5114
>>>
>>> I'm afraid it's not enough, either.  It's included in
>>> sound/soc/sof/intel/atom.c, and this one can be built-in by selected
>>> from others while CONFIG_SND_SOC_SOF_BAYTRAIL=m.  And, the reverse
>>> selection is done from CONFIG_SND_SOC_SOF_BAYTRAIL -- so
>>> CONFIG_IOSF_MBI can be m as well, and this can lead to the unresolved
>>> symbol from the built-in atom.c.
>>
>> Fair point, I was only looking at the reported failure where Baytrail
>> was completely disabled.
>>
>> I am not sure though if it makes sense to split hair in N dimensions.
>> Building Merrifield as y and Baytrail as m is a corner case that
>> shouldn't exist at all. And it's only an academic compilation issue, in
>> practice using 'y' would fail at run-time due to the usual firmware load
>> dependencies...
> 
> Surely this kind of bug won't hit anyone in practical use, but it's
> only about the randconfig failures.  The original report is in the
> same category, after all.
> 
> Maybe another (rather easier) workaround would be to use
> IS_REACHABLE(), something like below.  This should fix the original
> issue and the potential mess-up of kconfig dependencies.

The simplest solution works for me :-)

Do you want me to send a patch with your Suggested-by: tag or do it
yourself?

> --- a/sound/soc/intel/common/soc-intel-quirks.h
> +++ b/sound/soc/intel/common/soc-intel-quirks.h
> @@ -11,7 +11,7 @@
>  
>  #include <linux/platform_data/x86/soc.h>
>  
> -#if IS_ENABLED(CONFIG_X86)
> +#if IS_REACHABLE(CONFIG_IOSF_MBI)
>  
>  #include <linux/dmi.h>
>  #include <asm/iosf_mbi.h>

  reply	other threads:[~2024-07-18 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 23:07 ld.lld: error: undefined symbol: iosf_mbi_available kernel test robot
2024-07-17 11:43 ` Pierre-Louis Bossart
2024-07-17 20:28   ` Nathan Chancellor
2024-07-18  7:26     ` Takashi Iwai
2024-07-18  8:23       ` Pierre-Louis Bossart
2024-07-18  8:59         ` Takashi Iwai
2024-07-18  9:12           ` Pierre-Louis Bossart
2024-07-18 15:02             ` Takashi Iwai
2024-07-18 15:16               ` Pierre-Louis Bossart [this message]
2024-07-18 15:36                 ` Takashi Iwai
2024-07-19  6:42                   ` Pierre-Louis Bossart

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=69dfb1e2-eac6-4cd4-a9d3-caaa7f36f9b9@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=bard.liao@intel.com \
    --cc=guennadi.liakhovetski@linux.intel.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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