linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rdunlap@infradead.org (Randy Dunlap)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH -next] sound: rockchip: fix build when SPI_MASTER is not enabled
Date: Wed, 24 Aug 2016 10:57:20 -0700	[thread overview]
Message-ID: <22fcb876-1a27-0ff4-3f18-5079281c247e@infradead.org> (raw)

From: Randy Dunlap <rdunlap@infradead.org>

Fix multiple build errors in sound/soc/rockchip/ drivers by
adding "depends on SPI_MASTER".

Fixes these build errors:
sound/built-in.o: In function `rt5514_spi_burst_read':
(.text+0x6c26c): undefined reference to `spi_sync'
sound/built-in.o: In function `rt5514_spi_burst_write':
(.text+0x6c96e): undefined reference to `spi_sync'
sound/built-in.o: In function `rockchip_sound_probe':
rk3399_gru_sound.c:(.text+0x9f579): undefined reference to `spi_bus_type'
sound/built-in.o: In function `rt5514_spi_driver_init':
rt5514-spi.c:(.init.text+0x983): undefined reference to `__spi_register_driver'

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc:	Heiko Stuebner <heiko@sntech.de>
Cc:	linux-arm-kernel at lists.infradead.org
Cc:	linux-rockchip at lists.infradead.org
---
 sound/soc/rockchip/Kconfig |    1 +
 1 file changed, 1 insertion(+)

--- linux-next-20160824.orig/sound/soc/rockchip/Kconfig
+++ linux-next-20160824/sound/soc/rockchip/Kconfig
@@ -45,6 +45,7 @@ config SND_SOC_ROCKCHIP_RT5645
 config SND_SOC_RK3399_GRU_SOUND
 	tristate "ASoC support multiple codecs for Rockchip RK3399 GRU boards"
 	depends on SND_SOC_ROCKCHIP && I2C && GPIOLIB && CLKDEV_LOOKUP
+	depends on SPI_MASTER
 	select SND_SOC_ROCKCHIP_I2S
 	select SND_SOC_MAX98357A
 	select SND_SOC_RT5514

                 reply	other threads:[~2016-08-24 17:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=22fcb876-1a27-0ff4-3f18-5079281c247e@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).