From: Mark Brown <broonie@kernel.org>
To: linuxppc-dev@lists.ozlabs.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, Xiubo.Lee@gmail.com, tiwai@suse.com,
linux-kernel@vger.kernel.org, shengjiu.wang@gmail.com,
krzysztof.kozlowski+dt@linaro.org, nicoleotsuka@gmail.com,
alsa-devel@alsa-project.org, lgirdwood@gmail.com,
Chancel Liu <chancel.liu@nxp.com>,
festevam@gmail.com, perex@perex.cz
Subject: Re: [PATCH v3 0/7] Create a new sound card to access MICFIL based on rpmsg channel
Date: Tue, 18 Oct 2022 12:28:13 +0100 [thread overview]
Message-ID: <166609249377.155136.8150989631074960130.b4-ty@kernel.org> (raw)
In-Reply-To: <20220930064441.2548505-1-chancel.liu@nxp.com>
On Fri, 30 Sep 2022 14:44:34 +0800, Chancel Liu wrote:
> 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.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign the rpmsg channel
commit: 3570e6873b1a506bca4b5788d71141944c55132c
[2/7] ASoC: imx-audio-rpmsg: Create rpmsg channel for MICFIL
commit: f04189e0b85f6bbd10679e71061bf6d1ced5c539
[3/7] ASoC: imx-pcm-rpmsg: Register different platform drivers
commit: b2c2a947b3412f6edb9a86f5b12d6420958e67ba
[4/7] ASoC: imx-pcm-rpmsg: Multi-channel support for sound card based on rpmsg
commit: bdc0f6ca1c079ba790e0e227cff6164feae90460
[5/7] ASoC: fsl_rpmsg: Register different ASoC machine devices
commit: 76a874caeab596972f529968aa0d19d4ba1d2197
[6/7] ASoC: fsl_rpmsg: Multi-channel support in CPU DAI driver
commit: f26c1bb8a8ebe72748a3bb6f5d75079b642a33e8
[7/7] ASoC: imx-rpmsg: Assign platform driver used by machine driver to link with
commit: 4b48440ea390bada41928920446928beb3652a76
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2022-10-18 11:29 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
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 ` Mark Brown [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=166609249377.155136.8150989631074960130.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.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=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).