From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Muni Sekhar <munisekharrms@gmail.com>,
vkoul@kernel.org, sanyog.r.kale@intel.com,
alsa-devel <alsa-devel@alsa-project.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: soundwire: device drivers for PC based hardware
Date: Wed, 1 Jun 2022 12:17:57 -0500 [thread overview]
Message-ID: <66914bd5-8bed-adba-c7a7-6cbfe1ad3520@linux.intel.com> (raw)
In-Reply-To: <CAHhAz+gqRDh=CJseQEhAJcRVEguxQ5c4vdUX8dvzdPNT=Sy3iA@mail.gmail.com>
On 5/31/22 10:17, Muni Sekhar wrote:
> Hi all,
>
> I am looking for the soundwire device drivers which run on x86 CPU for
> PC based platforms.
>
> linux/drivers/soundwire at master · torvalds/linux · GitHub
>
> Can the above mentioned mainline tree drivers can be used for this purpose?
>
> config SOUNDWIRE_INTEL
> depends on ACPI && SND_SOC
>
> config SOUNDWIRE_QCOM
> depends on SND_SOC
>
> As per the Kconfig file, both the Intel and Qualcomm SoundWire Master
> driver depend on SND_SOC, does it mean it is only possible to run on
> SoC CPU(Arm chipsets)?
Here's what you need in your .config to use SoundWire on x86-based
hardware. Today this includes mostly Dell platforms, HP x360 convertible
laptops and Intel 'bishop canyon' NUC laptops.
CONFIG_REGMAP_SOUNDWIRE=m
CONFIG_REGMAP_SOUNDWIRE_MBQ=m
CONFIG_SND_INTEL_SOUNDWIRE_ACPI=m
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE_LINK_BASELINE=m
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE=m
CONFIG_SOUNDWIRE=m
CONFIG_SOUNDWIRE_CADENCE=m
CONFIG_SOUNDWIRE_INTEL=m
# CONFIG_SOUNDWIRE_QCOM is not set
CONFIG_SOUNDWIRE_GENERIC_ALLOCATION=m
I think you can get everything if you select these 3 high-level ones:
CONFIG_SOUNDWIRE
CONFIG_SND_SOC_SOF_INTEL_SOUNDWIRE
CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH
prev parent reply other threads:[~2022-06-01 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 15:17 soundwire: device drivers for PC based hardware Muni Sekhar
2022-06-01 17:17 ` Pierre-Louis Bossart [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=66914bd5-8bed-adba-c7a7-6cbfe1ad3520@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--cc=sanyog.r.kale@intel.com \
--cc=vkoul@kernel.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).