All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>
Subject: Re: How to correct params_format on DPCM ?
Date: Sat, 18 Apr 2015 13:32:22 +0100	[thread overview]
Message-ID: <20150418123222.GP26185@sirena.org.uk> (raw)
In-Reply-To: <87r3ro7hnu.wl%kuninori.morimoto.gx@renesas.com>


[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]

On Mon, Apr 13, 2015 at 04:54:39AM +0000, Kuninori Morimoto wrote:

> If my understanding is correct, the information which userland
> can get is setuped in .open

Yes.

> But, DPCM cases, it cares only cpu information. why it doesn't care codec ?

Like I said before for most systems that do DPCM (and certainly the ones
Liam's been working on) there's a DSP in place which rewrites all the
data between the front end and the back end so the constraints of the
CODEC aren't visible to the application layer.

> I guess DPCM should be...

>  FE.hw = fe_cpu & fe_codec
>  BE.hw = be_cpu & be_codec

Usually there's nothing "CODEC" visible at the front end for these
systems.

> And, if no FE constraint, final image will be

>  hw = FE.hw & BE.hw

Well, BE and CODEC but probably.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2015-04-18 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  5:05 How to correct params_format on DPCM ? Kuninori Morimoto
2015-04-08 18:01 ` Mark Brown
2015-04-10  7:12   ` Kuninori Morimoto
2015-04-10 15:43     ` Mark Brown
2015-04-13  0:28       ` Kuninori Morimoto
2015-04-13  4:54         ` Kuninori Morimoto
2015-04-18 12:32           ` Mark Brown [this message]
2015-04-20  0:29             ` Kuninori Morimoto

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=20150418123222.GP26185@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.