From: Shengjiu Wang <shengjiu.wang@gmail.com>
To: Chancel Liu <chancel.liu@nxp.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
lgirdwood@gmail.com, linuxppc-dev@lists.ozlabs.org,
Xiubo.Lee@gmail.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, tiwai@suse.com, nicoleotsuka@gmail.com,
broonie@kernel.org, krzysztof.kozlowski+dt@linaro.org,
perex@perex.cz, festevam@gmail.com
Subject: Re: [PATCH v3 2/7] ASoC: imx-audio-rpmsg: Create rpmsg channel for MICFIL
Date: Sun, 9 Oct 2022 14:17:09 +0800 [thread overview]
Message-ID: <CAA+D8AO5qoPA3m8_-8jq6nYhNOSHaXimDGX3HRqrX54pbcQn3Q@mail.gmail.com> (raw)
In-Reply-To: <20220930064441.2548505-3-chancel.liu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
On Fri, Sep 30, 2022 at 2:46 PM Chancel Liu <chancel.liu@nxp.com> wrote:
> Rpmsg channel for MICFIL can also be created through rpmsg name service
> announcement. If this driver is probed, Cortex-A can access MICFIL
> which is actually controlled by Cortex-M through rpmsg channel for
> MICFIL. This driver also helps register ASoC platform device thus use
> of PLATFORM_DEVID_AUTO macro in API can automatically create device for
> each rpmsg channel.
>
> Signed-off-by: Chancel Liu <chancel.liu@nxp.com>
>
Acked-by: Shengjiu Wang <shengjiu.wang@gmail.com>
Best regards
Wang Shengjiu
> ---
> sound/soc/fsl/imx-audio-rpmsg.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/sound/soc/fsl/imx-audio-rpmsg.c
> b/sound/soc/fsl/imx-audio-rpmsg.c
> index 905c3a071300..d5234ac4b09b 100644
> --- a/sound/soc/fsl/imx-audio-rpmsg.c
> +++ b/sound/soc/fsl/imx-audio-rpmsg.c
> @@ -88,7 +88,7 @@ static int imx_audio_rpmsg_probe(struct rpmsg_device
> *rpdev)
> /* Register platform driver for rpmsg routine */
> data->rpmsg_pdev = platform_device_register_data(&rpdev->dev,
> IMX_PCM_DRV_NAME,
> -
> PLATFORM_DEVID_NONE,
> +
> PLATFORM_DEVID_AUTO,
> NULL, 0);
> if (IS_ERR(data->rpmsg_pdev)) {
> dev_err(&rpdev->dev, "failed to register rpmsg
> platform.\n");
> @@ -110,6 +110,7 @@ static void imx_audio_rpmsg_remove(struct rpmsg_device
> *rpdev)
>
> static struct rpmsg_device_id imx_audio_rpmsg_id_table[] = {
> { .name = "rpmsg-audio-channel" },
> + { .name = "rpmsg-micfil-channel" },
> { },
> };
>
> --
> 2.25.1
>
>
[-- Attachment #2: Type: text/html, Size: 2739 bytes --]
next prev parent reply other threads:[~2022-10-09 6:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 6:44 [PATCH v3 0/7] Create a new sound card to access MICFIL based on rpmsg channel Chancel Liu
2022-09-30 6:44 ` [PATCH v3 1/7] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign the " 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 [this message]
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=CAA+D8AO5qoPA3m8_-8jq6nYhNOSHaXimDGX3HRqrX54pbcQn3Q@mail.gmail.com \
--to=shengjiu.wang@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chancel.liu@nxp.com \
--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=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).