All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Michael Trimarchi <michael@amarulasolutions.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: How to select input from muxer in front of SSI on i.MX6
Date: Mon, 13 Oct 2014 16:18:35 +0200	[thread overview]
Message-ID: <20141013141835.GI27755@sirena.org.uk> (raw)
In-Reply-To: <CAL8zT=gPh=pETH0fk7Jfz+n+-sRm_U1hEZv2FQAoSEkywjdVKw@mail.gmail.com>


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

On Wed, Oct 08, 2014 at 05:24:49PM +0200, Jean-Michel Hautbois wrote:
> 2014-09-24 10:21 GMT+02:00 Mark Brown <broonie@kernel.org>:

> > No, that's really not what DPCM is all about...  if this is a physically
> > separate device that's not got direct memory access it's probably more
> > appropriate to represent as a CODEC.  I was CCed in part way so don't
> > entirely know.

> OK, sorry for my late answer, but I was on a lot of things at the same time :/.
> Well, here is a tentative to explain what I want to do :
> http://paste.kde.org/pwijzty2p
> The objective is to develop the "Mux I²S" part, as this is in fact a
> FPGA with I²C registers which tell which input should go on which
> output.

OK, this probably does fit best with DPCM at this point of view as it is
such a simple straight through connection.  At least it's probably the
lowest impedence way of doing things right now, it's not really what we
want to do longer term though.

> I am reading Alsa docs, in order to fully understand what should be
> done, but it seems that this is nothing more than a simple codec with
> no effect on audio parameters... It should be visible in alsa mixer
> though, in order to drive the inputs from user space easily.

Even a dumb CODEC at least has the effect of limitng the configurations
that can be used.

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

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



      reply	other threads:[~2014-10-13 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 15:18 How to select input from muxer in front of SSI on i.MX6 Jean-Michel Hautbois
2014-09-19 17:52 ` Nicolin Chen
2014-09-22  9:08   ` Jean-Michel Hautbois
2014-09-23  1:51   ` Mark Brown
2014-09-23  6:11     ` Jean-Michel Hautbois
2014-09-24  8:21       ` Mark Brown
2014-10-08 15:24         ` Jean-Michel Hautbois
2014-10-13 14:18           ` 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=20141013141835.GI27755@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jean-michel.hautbois@vodalys.com \
    --cc=lgirdwood@gmail.com \
    --cc=michael@amarulasolutions.com \
    --cc=nicoleotsuka@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.