From: Jean-Francois Moine <moinejf@free.fr>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: alsa-devel@alsa-project.org,
"Dr. H. Nikolaus Schaller" <hns@goldelico.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
broonie@kernel.org, jarkko.nikula@bitmer.com
Subject: Re: dummy codec + simple card combination
Date: Fri, 3 Apr 2015 10:45:52 +0200 [thread overview]
Message-ID: <20150403104552.5c7ff4f2@armhf> (raw)
In-Reply-To: <CAAfyv34qpJcgaTZj2APhh11XuyDfOs4s+9RO2EjWqStK_uZ_Xg@mail.gmail.com>
On Thu, 2 Apr 2015 22:24:45 +0200
Belisko Marek <marek.belisko@gmail.com> wrote:
> For what kind of device do you wrote simple codec? We would use it for
> GSM and BT
At this time, I wanted to use DPCM, and a dummy codec was needed.
The simple codec could also have been used to replace empty codecs as
s/pdif and hdmi.
> (we could use bt-sco driver) which produce PCM samples (rate is
> determined by mclk and bclk).
> If your proposal wasn't accepted then I think the best would be for
> our purpose to write dummy codecs
> for both interfaces and not generic simple codec.
The generic simple codec was just a dummy codec.
Which difference do you see?
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-04-03 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 20:35 dummy codec + simple card combination Belisko Marek
2015-03-12 18:33 ` Belisko Marek
2015-03-13 9:28 ` Peter Ujfalusi
2015-03-13 9:54 ` Dr. H. Nikolaus Schaller
2015-03-17 14:07 ` Peter Ujfalusi
2015-04-01 21:08 ` Belisko Marek
2015-04-02 5:11 ` Jean-Francois Moine
2015-04-02 20:24 ` Belisko Marek
2015-04-03 8:45 ` Jean-Francois Moine [this message]
2015-04-03 12:29 ` Belisko Marek
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=20150403104552.5c7ff4f2@armhf \
--to=moinejf@free.fr \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hns@goldelico.com \
--cc=jarkko.nikula@bitmer.com \
--cc=lgirdwood@gmail.com \
--cc=marek.belisko@gmail.com \
--cc=peter.ujfalusi@ti.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.