From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, YueHaibing <yuehaibing@huawei.com>,
lgirdwood@gmail.com, broonie@kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: SOF: Fix build error with CONFIG_SND_SOC_SOF_NOCODEC=m
Date: Fri, 10 May 2019 15:41:10 +0200 [thread overview]
Message-ID: <s5hbm0amnpl.wl-tiwai@suse.de> (raw)
In-Reply-To: <1e7e1908-a813-6c9b-5b88-122864d3a372@linux.intel.com>
On Fri, 10 May 2019 15:34:03 +0200,
Pierre-Louis Bossart wrote:
>
> On 5/10/19 8:04 AM, Takashi Iwai wrote:
> > On Fri, 10 May 2019 14:56:29 +0200,
> > Pierre-Louis Bossart wrote:
> >>
> >> On 5/10/19 2:12 AM, Takashi Iwai wrote:
> >>> On Fri, 10 May 2019 04:36:57 +0200,
> >>> YueHaibing wrote:
> >>>>
> >>>> Fix gcc build error while CONFIG_SND_SOC_SOF_NOCODEC=m
> >>>>
> >>>> sound/soc/sof/core.o: In function `snd_sof_device_probe':
> >>>> core.c:(.text+0x4af): undefined reference to `sof_nocodec_setup'
> >>>>
> >>>> Change SND_SOC_SOF_NOCODEC to bool to fix this.
> >>>>
> >>>> Reported-by: Hulk Robot <hulkci@huawei.com>
> >>>> Fixes: c16211d6226d ("ASoC: SOF: Add Sound Open Firmware driver core")
> >>>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> >>>
> >>> This change would break things severely. This won't allow to build it
> >>> as a module any longer.
> >>
> >> Isn't this fixed already?
> >> See the patch 'ASoC: SOF: core: fix undefined nocodec reference' and
> >> Takashi's follow-up to fix the unused variable warning.
> >
> > Possibly the problem still persists although I haven't seen through my
> > local build tests with randconfig. You can set SND_SOC_SOF=y and
> > SND_SOC_NOCODEC=m, i.e. built-in sof-core while nocodec is a module.
>
> YueHiabing, can you share the config and SHA1 so that we can double check?
>
> If the problem persists, we can do something like
>
> config SND_SOF_NOCODEC_SUPPORT
> bool "SOF nocodec mode support"
>
> config SND_SOF_NOCODEC
> tristate
>
> confir SND_SOC_SOF
> tristate
> select SND_SOF_NOCODEC if SND_SOF_NOCODEC_SUPPORT
>
> that way you propagate the required dependencies
Yes, that would work. OTOH, I see no merit to build an extra module
for nocodec. nocodec.c can be built together with sof-core stuff.
thanks,
Takashi
next prev parent reply other threads:[~2019-05-10 13:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 2:36 [PATCH] ASoC: SOF: Fix build error with CONFIG_SND_SOC_SOF_NOCODEC=m YueHaibing
2019-05-10 2:36 ` YueHaibing
2019-05-10 7:12 ` Takashi Iwai
2019-05-10 7:12 ` Takashi Iwai
2019-05-10 12:56 ` Pierre-Louis Bossart
2019-05-10 13:04 ` Takashi Iwai
2019-05-10 13:34 ` [alsa-devel] " Pierre-Louis Bossart
2019-05-10 13:41 ` Takashi Iwai [this message]
2019-05-10 13:56 ` Takashi Iwai
2019-05-10 15:29 ` Pierre-Louis Bossart
2019-05-10 16:57 ` Takashi Iwai
2019-05-10 17:56 ` Pierre-Louis Bossart
2019-05-10 18:05 ` Takashi Iwai
2019-05-10 13:09 ` YueHaibing
2019-05-10 13:09 ` YueHaibing
2019-05-10 13:29 ` [PATCH V2] " YueHaibing
2019-05-10 13:29 ` YueHaibing
2019-05-10 13:36 ` Pierre-Louis Bossart
2019-05-10 13:50 ` YueHaibing
2019-05-10 13:50 ` YueHaibing
2019-05-10 16:24 ` 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=s5hbm0amnpl.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=yuehaibing@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.