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@nxp.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 1/5] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign platform driver name
Date: Mon, 29 Aug 2022 15:51:40 +0800 [thread overview]
Message-ID: <20220829075144.2405000-2-chancel.liu@nxp.com> (raw)
In-Reply-To: <20220829075144.2405000-1-chancel.liu@nxp.com>
Add a string property to assign ASoC platform driver name. It also
represents the rpmsg channel this sound card sits on. This property
can be omitted if there is only one sound card and it sits on
"rpmsg-audio-channel".
Signed-off-by: Chancel Liu <chancel.liu@nxp.com>
---
.../devicetree/bindings/sound/fsl,rpmsg.yaml | 34 +++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml b/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml
index d370c98a62c7..35e3cb9f768b 100644
--- a/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml
+++ b/Documentation/devicetree/bindings/sound/fsl,rpmsg.yaml
@@ -11,8 +11,11 @@ maintainers:
description: |
fsl_rpmsg is a virtual audio device. Mapping to real hardware devices
- are SAI, DMA controlled by Cortex M core. What we see from Linux
- side is a device which provides audio service by rpmsg channel.
+ are SAI, MICFIL, DMA controlled by Cortex M core. What we see from
+ Linux side is a device which provides audio service by rpmsg channel.
+ We can create different sound cards which access different hardwares
+ such as SAI, MICFIL, .etc through building rpmsg channels between
+ Cortex-A and Cortex-M.
properties:
compatible:
@@ -85,6 +88,14 @@ properties:
This is a boolean property. If present, the receiving function
will be enabled.
+ fsl,platform:
+ $ref: /schemas/types.yaml#/definitions/string
+ description: |
+ A string property to assign ASoC platform driver name. It also
+ represents the rpmsg channel this sound card sits on. This property
+ can be omitted if there is only one sound card and it sits on
+ "rpmsg-audio-channel".
+
required:
- compatible
- model
@@ -107,3 +118,22 @@ examples:
<&clk IMX8MN_AUDIO_PLL2_OUT>;
clock-names = "ipg", "mclk", "dma", "pll8k", "pll11k";
};
+
+ - |
+ #include <dt-bindings/clock/imx8mm-clock.h>
+
+ rpmsg_micfil: rpmsg_micfil {
+ compatible = "fsl,imx8mm-rpmsg-audio";
+ model = "micfil-audio";
+ fsl,platform = "rpmsg-micfil-channel";
+ fsl,enable-lpa;
+ fsl,rpmsg-in;
+ clocks = <&clk IMX8MM_CLK_PDM_IPG>,
+ <&clk IMX8MM_CLK_PDM_ROOT>,
+ <&clk IMX8MM_CLK_SDMA3_ROOT>,
+ <&clk IMX8MM_AUDIO_PLL1_OUT>,
+ <&clk IMX8MM_AUDIO_PLL2_OUT>;
+ clock-names = "ipg", "mclk", "dma", "pll8k", "pll11k";
+ };
+
+...
--
2.25.1
next prev parent reply other threads:[~2022-08-29 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 7:51 [PATCH 0/5] Create a new sound card to access MICFIL based on rpmsg channel Chancel Liu
2022-08-29 7:51 ` Chancel Liu [this message]
2022-08-30 6:28 ` [PATCH 1/5] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign platform driver name S.J. Wang
2022-08-30 9:28 ` Krzysztof Kozlowski
2022-08-29 7:51 ` [PATCH 2/5] ASoC: imx-audio-rpmsg: Create rpmsg channel for MICFIL Chancel Liu
2022-08-29 7:51 ` [PATCH 3/5] ASoC: imx-pcm-rpmsg: Register different platform drivers Chancel Liu
2022-08-30 6:31 ` S.J. Wang
2022-08-29 7:51 ` [PATCH 4/5] ASoC: fsl_rpmsg: Register different CPU DAI drivers Chancel Liu
2022-08-29 7:51 ` [PATCH 5/5] ASoC: imx-rpmsg: Assign platform driver used by machine driver to link with Chancel Liu
-- strict thread matches above, loose matches on Subject: below --
2022-09-13 7:14 Re: [PATCH 1/5] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign platform driver name Chancel Liu
2022-09-13 8:39 ` Krzysztof Kozlowski
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=20220829075144.2405000-2-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@nxp.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).