From: Chancel Liu <chancel.liu@nxp.com>
To: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
nicoleotsuka@gmail.com, linuxppc-dev@lists.ozlabs.org
Cc: Chancel Liu <chancel.liu@nxp.com>
Subject: [PATCH v3 0/7] Create a new sound card to access MICFIL based on rpmsg channel
Date: Fri, 30 Sep 2022 14:44:34 +0800 [thread overview]
Message-ID: <20220930064441.2548505-1-chancel.liu@nxp.com> (raw)
At a previous time, we have successfully created a virtual sound card
based on rpmsg. The sound card works under this mechanism Cortex-A core
tells the Cortex-M core the format, rate, channel, .etc configuration
of the PCM parameters and Cortex-M controls real hardware devices such
as SAI and DMA. From the view of Linux side, the sound card is bound to
a rpmsg channel through which it can access SAI.
Here these patches are introduced to create a new virtual sound card to
access MICFIL based on a new created rpmsg channel. It's easy to create
a new rpmsg channel for MICFIL through rpmsg name service announcment.
Also the other ASoC components bound to this rpmsg MICFIL sound card
will be registered with these patches.
If other sound cards using different hardware devices needs to be
created over rpmsg in the future, these patches can be referred.
changes in v3
- Delete the statement referring to linux drivers in dts
changes in v2:
- Rename property in bindings file according to Krzysztof's comments
- Update codes and comments according to Shengjiu's comments
Chancel Liu (7):
ASoC: dt-bindings: fsl_rpmsg: Add a property to assign the rpmsg
channel
ASoC: imx-audio-rpmsg: Create rpmsg channel for MICFIL
ASoC: imx-pcm-rpmsg: Register different platform drivers
ASoC: imx-pcm-rpmsg: Multi-channel support for sound card based on
rpmsg
ASoC: fsl_rpmsg: Register different ASoC machine devices
ASoC: fsl_rpmsg: Multi-channel support in CPU DAI driver
ASoC: imx-rpmsg: Assign platform driver used by machine driver to link
with
.../devicetree/bindings/sound/fsl,rpmsg.yaml | 36 +++++++++++++++++--
sound/soc/fsl/fsl_rpmsg.c | 6 ++--
sound/soc/fsl/imx-audio-rpmsg.c | 3 +-
sound/soc/fsl/imx-pcm-rpmsg.c | 10 ++++--
sound/soc/fsl/imx-rpmsg.c | 6 +++-
5 files changed, 51 insertions(+), 10 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-30 6:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 6:44 Chancel Liu [this message]
2022-09-30 6:44 ` [PATCH v3 1/7] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign the rpmsg channel Chancel Liu
2022-10-03 16:20 ` Rob Herring
2022-09-30 6:44 ` [PATCH v3 2/7] ASoC: imx-audio-rpmsg: Create rpmsg channel for MICFIL Chancel Liu
2022-10-09 6:17 ` Shengjiu Wang
2022-09-30 6:44 ` [PATCH v3 3/7] ASoC: imx-pcm-rpmsg: Register different platform drivers Chancel Liu
2022-10-09 6:17 ` Shengjiu Wang
2022-09-30 6:44 ` [PATCH v3 4/7] ASoC: imx-pcm-rpmsg: Multi-channel support for sound card based on rpmsg Chancel Liu
2022-10-09 6:18 ` Shengjiu Wang
2022-09-30 6:44 ` [PATCH v3 5/7] ASoC: fsl_rpmsg: Register different ASoC machine devices Chancel Liu
2022-10-09 6:18 ` Shengjiu Wang
2022-09-30 6:44 ` [PATCH v3 6/7] ASoC: fsl_rpmsg: Multi-channel support in CPU DAI driver Chancel Liu
2022-10-09 6:19 ` Shengjiu Wang
2022-09-30 6:44 ` [PATCH v3 7/7] ASoC: imx-rpmsg: Assign platform driver used by machine driver to link with Chancel Liu
2022-10-09 6:19 ` Shengjiu Wang
2022-10-18 11:28 ` [PATCH v3 0/7] Create a new sound card to access MICFIL based on rpmsg channel Mark Brown
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=20220930064441.2548505-1-chancel.liu@nxp.com \
--to=chancel.liu@nxp.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=krzysztof.kozlowski+dt@linaro.org \
--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=shengjiu.wang@gmail.com \
--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).