From: Liam Girdwood <lrg@ti.com>
To: gsantosh@codeaurora.org
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: ALSA concurrent use case for 5.1 LPCM on HDMI.
Date: Thu, 26 Jul 2012 00:07:01 +0100 [thread overview]
Message-ID: <1343257621.16982.9.camel@odin> (raw)
In-Reply-To: <16e078f384eda9134af4b78dec4ec090.squirrel@www.codeaurora.org>
On Wed, 2012-07-25 at 01:37 -0700, gsantosh@codeaurora.org wrote:
> Hi All,
>
> I have following use case I am facing an issue with the ALSA framework,
>
> Consider a use case
>
> 1) System tone or any stream running on Front End 0 with stereo channel
> configuration On Back End 0(HDMI)
> 2) Start a local file playback for 5.1 LPCM on Front End 1 with 5.1
> channel configuration On Back End 0(HDMI)
>
> Here FE0 and FE1 is routed to same BE0.
>
> When step 2 is done I see following behavior of ALSA which is not correct.
> Framework will check that the BE0 is running with FE0 routed and running,
> Framework will not trigger the fixup and hw_params callback to re
> configure the session for FE1 with 5.1 channel.
>
> With this effect we are playing the FE1 session with stereo instead of 5.1
> channel configuration, how to rectify this issue?
>
Hmm, the fixup code will currently only run when the BE0 is initially
configured via hw_params(). The problem here is that if we fixup and
reconfigure BE0 (via hw_params()) after it is running then this will
likely cause undesired audio artifacts on BE0 (since in this case it's
already playing stereo and we want to change to 6 channel).
We have a similar situation with OMAP where we support many channels (2
- 6) on one McBSP BE DAI. We always configure the BE McBSP in 6 channel
mode and that allows us to open any FE with 2...6 channels (without a
fixup and restart of the McBSP port).
Regards
Liam
> Regards,
> Santosh M G.
>
>
>
>
prev parent reply other threads:[~2012-07-25 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 8:37 ALSA concurrent use case for 5.1 LPCM on HDMI gsantosh
2012-07-25 23:07 ` Liam Girdwood [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=1343257621.16982.9.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=gsantosh@codeaurora.org \
--cc=tiwai@suse.de \
/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).