From: Vishal Thanki <vishalthanki@gmail.com>
To: alsa-devel@alsa-project.org, peter.ujfalusi@ti.com,
christophe.jaillet@wanadoo.fr, elfring@users.sourceforge.net,
arvind.yadav.cs@gmail.com
Cc: Vishal Thanki <vishalthanki@gmail.com>
Subject: [PATCH 0/1] Handling of serializers
Date: Tue, 27 Feb 2018 15:51:03 +0100 [thread overview]
Message-ID: <20180227145104.5868-1-vishalthanki@gmail.com> (raw)
On a custom AM33xx based platform, we use 4 channels for audio output (2
* Left/Right) by making use of two TX serializers. The audio input path
only uses 2 channels, hence one RX serializer. If the recording is
started before the playback, the playback cannot make use of all 4
channels because of the imposed max number of channels by recording. And
if playback is started before recording, the hw_params set during
recording stream would disable an active TX serializer which causes
audio distortion. I have tried to fix this unwanted behavior in
following patch. Please comment if this should be done differently.
Vishal Thanki (1):
ASoC: davinci-mcasp: Only disable inactive serializer
sound/soc/davinci/davinci-mcasp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.14.3
next reply other threads:[~2018-02-27 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 14:51 Vishal Thanki [this message]
2018-02-27 14:51 ` [PATCH 1/1] ASoC: davinci-mcasp: Only disable inactive serializer Vishal Thanki
2018-03-05 12:42 ` Peter Ujfalusi
2018-03-27 11:34 ` Vishal Thanki
2018-03-27 11:57 ` Mark Brown
2018-03-27 11:58 ` Mark Brown
2018-05-17 16:38 ` Applied "ASoC: davinci-mcasp: Only disable inactive serializer" to the asoc tree 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=20180227145104.5868-1-vishalthanki@gmail.com \
--to=vishalthanki@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=elfring@users.sourceforge.net \
--cc=peter.ujfalusi@ti.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).