All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Michel Hautbois <jean-michel.hautbois@vodalys.com>
To: Mark Brown <broonie@kernel.org>
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: Wed, 8 Oct 2014 17:24:49 +0200	[thread overview]
Message-ID: <CAL8zT=gPh=pETH0fk7Jfz+n+-sRm_U1hEZv2FQAoSEkywjdVKw@mail.gmail.com> (raw)
In-Reply-To: <20140924082146.GV4015@sirena.org.uk>

Hi Mark,

2014-09-24 10:21 GMT+02:00 Mark Brown <broonie@kernel.org>:
> On Tue, Sep 23, 2014 at 08:11:27AM +0200, Jean-Michel Hautbois wrote:
>> Le 23 sept. 2014 03:51, "Mark Brown" <broonie@kernel.org> a écrit :
>
>> > Depending on what the system looks like it's not at all clear that there
>> > should be any visibility at all of DPCM in the DT - it's a detail of how
>> > Linux is implemented at the end of the day.
>
>> So this should definitely be implemented directly in a specific driver for
>> my FPGA which is a DPCM right ?
>
> 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.

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.

I hope this is clearer...
Thanks !
JM
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2014-10-08 15:25 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 [this message]
2014-10-13 14:18           ` 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='CAL8zT=gPh=pETH0fk7Jfz+n+-sRm_U1hEZv2FQAoSEkywjdVKw@mail.gmail.com' \
    --to=jean-michel.hautbois@vodalys.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --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.