From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: gsantosh@codeaurora.org, Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh@kernel.org>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Magnus <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
grant.likely@linaro.org, alsa-devel-bounces@alsa-project.org,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [alsa-devel] Question on Compressed offload session
Date: Fri, 14 Nov 2014 17:06:50 +0000 [thread overview]
Message-ID: <20141114170650.GG3815@sirena.org.uk> (raw)
In-Reply-To: <54662DC6.7070302@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
On Fri, Nov 14, 2014 at 10:28:54AM -0600, Pierre-Louis Bossart wrote:
> On 11/13/14, 10:08 PM, gsantosh@codeaurora.org wrote:
> >1) in Codec driver avoid adding hw_constraint during startup if compressed
> >session is routed, this recommend for codec driver to know that compress
> >session is routed to codec which I feel not the correct way to handle this
> >I was checking how to handle this situation in much better way.
> What exactly do you call a 'legacy codec'? If there is a DAI i am not sure I
> understand the problem.
I think what he's trying to say is that there's nothing automatic which
will ensure that constraints on the back end set by the CODEC driver
will be paid attention to. This is true, it's pretty much entirely up
to the machine driver to make sure it gets the back end links right.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-14 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 3:02 Question on Compressed offload session gsantosh
2014-11-13 15:27 ` [alsa-devel] " Pierre-Louis Bossart
2014-11-14 4:08 ` gsantosh
2014-11-14 16:28 ` Pierre-Louis Bossart
2014-11-14 17:06 ` 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=20141114170650.GG3815@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel-bounces@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=grant.likely@linaro.org \
--cc=gsantosh@codeaurora.org \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh@kernel.org \
--cc=swarren@wwwdotorg.org \
/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).