From: Mark Brown <broonie@kernel.org>
To: peter.ujfalusi@ti.com, lgirdwood@gmail.com, tony@atomide.com,
Pavel Machek <pavel@ucw.cz>,
perex@perex.cz, linux-kernel@vger.kernel.org, tiwai@suse.com,
alsa-devel@alsa-project.org, kuninori.morimoto.gx@renesas.com
Cc: Sebastian Reichel <sre@kernel.org>,
"Arthur D." <spinal.by@gmail.com>,
Merlijn Wajer <merlijn@wizzup.org>
Subject: Re: ASoC: cpcap: Implement set_tdm_slot for voice call support
Date: Thu, 21 Jan 2021 00:05:34 +0000 [thread overview]
Message-ID: <161118753482.45718.9232559568095752872.b4-ty@kernel.org> (raw)
In-Reply-To: <20210112174704.GA13496@duo.ucw.cz>
On Tue, 12 Jan 2021 18:47:04 +0100, Pavel Machek wrote:
> From: Tony Lindgren <tony@atomide.com>
>
> ASoC: cpcap: Implement set_tdm_slot for voice call support
>
> For using cpcap for voice calls, we need to route audio directly from
> the modem to cpcap for TDM (Time Division Multiplexing). The voice call
> is direct data between the modem and cpcap with no CPU involvment. In
> this mode, the cpcap related audio mixer controls work for the speaker
> selection and volume though.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: cpcap: Implement set_tdm_slot for voice call support
commit: 0dedbde5062dbc3cf71ab1ba40792c04a68008e9
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
next prev parent reply other threads:[~2021-01-21 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 17:47 Pavel Machek
2021-01-21 0:05 ` Mark Brown [this message]
2021-01-23 18:28 ` ASoC: audio-graph-card: Add audio mixer for Motorola mdm6600 Pavel Machek
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=161118753482.45718.9232559568095752872.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@ucw.cz \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=spinal.by@gmail.com \
--cc=sre@kernel.org \
--cc=tiwai@suse.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®