From: Arnaud Ferraris <arnaud.ferraris@collabora.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kernel@collabora.com, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Timur Tabi <timur@kernel.org>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] ASoC: fsl-asoc-card: add support for generic codecs
Date: Thu, 2 Jul 2020 16:11:13 +0200 [thread overview]
Message-ID: <20200702141114.232688-1-arnaud.ferraris@collabora.com> (raw)
fsl-asoc-card currently only works with AC97 or a selection of codecs,
although the hardware is capable of more.
Supporting generic codecs when acting as I2S slave (codec is master)
would be useful, especially when using Bluetooth audio, as these are
generally simple I2S devices not controlled by the sound subsystem.
This will allow using simple/dummy codecs along with ASRC.
Arnaud Ferraris (2):
dt-bindings: sound: fsl-asoc-card: add new compatible for I2S slave
ASoC: fsl-asoc-card: add support for generic I2S slave use-case
Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 23 ++++++++++++++++++++++-
sound/soc/fsl/fsl-asoc-card.c | 46 +++++++++++++++++++++++++++++++++++-----------
2 files changed, 57 insertions(+), 12 deletions(-)
next reply other threads:[~2020-07-02 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:11 Arnaud Ferraris [this message]
2020-07-02 14:11 ` [PATCH 1/2] dt-bindings: sound: fsl-asoc-card: add new compatible for I2S slave Arnaud Ferraris
2020-07-02 14:31 ` Mark Brown
2020-07-02 15:28 ` Arnaud Ferraris
2020-07-02 15:42 ` Mark Brown
2020-07-03 9:23 ` Arnaud Ferraris
2020-07-02 14:11 ` [PATCH 2/2] ASoC: fsl-asoc-card: add support for generic I2S slave use-case Arnaud Ferraris
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=20200702141114.232688-1-arnaud.ferraris@collabora.com \
--to=arnaud.ferraris@collabora.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=timur@kernel.org \
--cc=tiwai@suse.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).