From: Baojun Xu <baojun.xu@ti.com>
To: <tiwai@suse.de>
Cc: <robh+dt@kernel.org>, <andriy.shevchenko@linux.intel.com>,
<lgirdwood@gmail.com>, <perex@perex.cz>,
<pierre-louis.bossart@linux.intel.com>, <kevin-lu@ti.com>,
<13916275206@139.com>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <liam.r.girdwood@intel.com>,
<yung-chuan.liao@linux.intel.com>, <baojun.xu@ti.com>,
<broonie@kernel.org>, <soyer@irl.hu>
Subject: [PATCH v1 4/8] ALSA: hda/tas2781: Add tas2781 SPI-based driver
Date: Tue, 26 Mar 2024 09:09:01 +0800 [thread overview]
Message-ID: <20240326010905.2147-4-baojun.xu@ti.com> (raw)
In-Reply-To: <20240326010905.2147-1-baojun.xu@ti.com>
Add tas2781 spi driver files.
Signed-off-by: Baojun Xu <baojun.xu@ti.com>
---
sound/pci/hda/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/pci/hda/Makefile b/sound/pci/hda/Makefile
index 13e04e1f6..9785cddb4 100644
--- a/sound/pci/hda/Makefile
+++ b/sound/pci/hda/Makefile
@@ -39,6 +39,7 @@ snd-hda-scodec-cs35l56-spi-objs := cs35l56_hda_spi.o
snd-hda-cs-dsp-ctls-objs := hda_cs_dsp_ctl.o
snd-hda-scodec-component-objs := hda_component.o
snd-hda-scodec-tas2781-i2c-objs := tas2781_hda_i2c.o
+snd-hda-scodec-tas2781-spi-objs := tas2781_hda_spi.o tas2781_spi_fwlib.o
# common driver
obj-$(CONFIG_SND_HDA) := snd-hda-codec.o
@@ -70,6 +71,7 @@ obj-$(CONFIG_SND_HDA_SCODEC_CS35L56_SPI) += snd-hda-scodec-cs35l56-spi.o
obj-$(CONFIG_SND_HDA_CS_DSP_CONTROLS) += snd-hda-cs-dsp-ctls.o
obj-$(CONFIG_SND_HDA_SCODEC_COMPONENT) += snd-hda-scodec-component.o
obj-$(CONFIG_SND_HDA_SCODEC_TAS2781_I2C) += snd-hda-scodec-tas2781-i2c.o
+obj-$(CONFIG_SND_HDA_SCODEC_TAS2781_SPI) += snd-hda-scodec-tas2781-spi.o
# this must be the last entry after codec drivers;
# otherwise the codec patches won't be hooked before the PCI probe
--
2.40.1
next prev parent reply other threads:[~2024-03-26 1:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 1:08 [PATCH v1 1/8] ALSA: hda/tas2781: Add tas2781 SPI-based driver Baojun Xu
2024-03-26 1:08 ` [PATCH v1 2/8] " Baojun Xu
2024-03-26 15:00 ` Andy Shevchenko
2024-03-26 15:22 ` Takashi Iwai
2024-03-26 1:09 ` [PATCH v1 3/8] " Baojun Xu
2024-03-26 1:09 ` Baojun Xu [this message]
2024-03-26 15:01 ` [PATCH v1 4/8] " Andy Shevchenko
2024-03-26 15:03 ` Andy Shevchenko
2024-03-26 1:09 ` [PATCH v1 5/8] " Baojun Xu
2024-03-26 1:09 ` [PATCH v1 6/8] " Baojun Xu
2024-03-26 15:05 ` Pierre-Louis Bossart
2024-04-06 7:43 ` [EXTERNAL] " Xu, Baojun
2024-03-26 1:09 ` [PATCH v1 7/8] " Baojun Xu
2024-03-26 15:13 ` Pierre-Louis Bossart
2024-03-26 15:16 ` Andy Shevchenko
2024-03-26 15:15 ` Andy Shevchenko
2024-03-27 10:02 ` Gergo Koteles
2024-04-05 15:51 ` [EXTERNAL] " Xu, Baojun
2024-03-26 1:09 ` [PATCH v1 8/8] " Baojun Xu
2024-03-26 14:58 ` [PATCH v1 1/8] " Andy Shevchenko
2024-04-05 16:17 ` [EXTERNAL] " Xu, Baojun
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=20240326010905.2147-4-baojun.xu@ti.com \
--to=baojun.xu@ti.com \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=soyer@irl.hu \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@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