From: Vinod Koul <vinod.koul@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: intel: fix build when ACPI is not enabled
Date: Tue, 21 Jun 2016 09:43:45 +0530 [thread overview]
Message-ID: <20160621041345.GW16910@localhost> (raw)
In-Reply-To: <575ECB6C.7050102@infradead.org>
On Mon, Jun 13, 2016 at 08:04:12AM -0700, Randy Dunlap wrote:
> On 06/12/16 21:22, Vinod Koul wrote:
> > On Thu, Jun 09, 2016 at 05:01:38PM -0700, Randy Dunlap wrote:
> >> From: Randy Dunlap <rdunlap@infradead.org>
> >>
> >> kconfig tools generate the following warning when CONFIG_ACPI is not
> >> enabled:
> >>
> >> warning: (SND_SOC_INTEL_BYTCR_RT5640_MACH && SND_SOC_INTEL_BYTCR_RT5651_MACH && SND_SOC_INTEL_CHT_BSW_RT5672_MACH && SND_SOC_INTEL_CHT_BSW_RT5645_MACH && SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH) selects SND_SST_IPC_ACPI which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && ACPI)
> >>
> >> causing these build errors:
> >>
> >> In file included from ../sound/soc/intel/atom/sst/sst_acpi.c:40:0:
> >> ../include/acpi/acpi_bus.h:65:20: error: conflicting types for 'acpi_evaluate_dsm'
> >> union acpi_object *acpi_evaluate_dsm(acpi_handle handle, const u8 *uuid,
> >> In file included from ../sound/soc/intel/atom/sst/sst_acpi.c:31:0:
> >> ../include/linux/acpi.h:676:34: note: previous definition of 'acpi_evaluate_dsm' was here
> >> static inline union acpi_object *acpi_evaluate_dsm(acpi_handle handle,
> >>
> >> I am told that ACPI is a requirement for these drivers, so make that
> >> explicit. Also end help text sentences with a period.
> >>
> >> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> >> Cc: Jie Yang <yang.jie@linux.intel.com>
> >> Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> >> Cc: alsa-devel@alsa-project.org
> >> ---
> >> sound/soc/intel/Kconfig | 12 ++++++------
> >> 1 file changed, 6 insertions(+), 6 deletions(-)
> >>
> >> Should SND_SOC_INTEL_SST and possibly other similar drivers get this
> >> same change?
> >
> > The SND_SST_IPC_ACPI has depends on ACPI.
> >
> > Can you send me your config for this.
>
> Attached.
Thanks,
I was able to test this and tried few things. The SND_SST_IPC_ACPI has
depends but someone can still selecta ACPI machine and cause these errors so
I have moved the onus on machines and thus removed the depends and moved to
all the ACPI machines. The PCI ones don't care about this so they are okay.
Thanks for reporting, patches are posted now.
--
~Vinod
prev parent reply other threads:[~2016-06-21 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 0:01 [PATCH] ASoC: intel: fix build when ACPI is not enabled Randy Dunlap
2016-06-13 4:22 ` [alsa-devel] " Vinod Koul
2016-06-13 15:04 ` Randy Dunlap
2016-06-21 4:13 ` Vinod Koul [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=20160621041345.GW16910@localhost \
--to=vinod.koul@intel.com \
--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=yang.jie@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).