From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Caleb Crome <caleb@crome.org>
Cc: "Lu, Han" <han.lu@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Gautier, Bernard" <bernard.gautier@intel.com>
Subject: Re: Feasibility of adding alternative audio transport besides I2S/PWM/SPDIF, etc
Date: Fri, 09 Oct 2015 10:34:56 +0100 [thread overview]
Message-ID: <1444383296.2479.8.camel@loki> (raw)
In-Reply-To: <CAG5mAdwOugskZrHHzeQ-GSu6mAZoN3nybOvupB09FBk2oTwJnw@mail.gmail.com>
On Thu, 2015-10-08 at 08:51 -0700, Caleb Crome wrote:
> Hi All,
> I'm in a constant struggle to bring up many channel audio on each
> separate SoC.
>
> I can easily put a microcontroller in place that will collect and
> distrubute all the TDM channels to the codecs, and connect the
> hardware via an SPI interface to the SoC.
>
> So, instead of:
>
> CODECS <---TDM---> SoC
>
> It would be
>
> CODECS <---TDM---> uC <---SPI---> SoC
>
> So, my questions are:
>
> * I suspect the SPI interface could be used more universally than each
> individual I2S/TDM interface (like FSL SSI vs. Ti McBSP vs. Ti McASP,
> etc). and the SPI port would provide a very common API regardless of
> SoC. Is that true?
Some SPI ports could probably be used for audio, but this depends on the
SPI port HW capabilities. e.g. the SSP port on minnowboard can be
configured for TDM, I2S and SPI (afaik). I don't think any advantage
could be gained from running in SPI mode unless your HW permits some
special features ?
>
> * Is it feasible to integrate an SPI transport into the SoC/alsa
> layer? What are the difficulties involved with that?
>
Yes, that's doable providing the SPI port is capable of supporting audio
formats and has good DMA connectivity. A DAI driver would need to be
written for your SPI port to allow it to send audio data within ASoC.
Liam
>
> Cheers,
> -Caleb
next prev parent reply other threads:[~2015-10-09 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 15:51 Feasibility of adding alternative audio transport besides I2S/PWM/SPDIF, etc Caleb Crome
2015-10-09 9:34 ` Liam Girdwood [this message]
2015-10-09 16:11 ` Caleb Crome
2015-10-13 9:57 ` Liam Girdwood
2015-10-13 10:43 ` Lars-Peter Clausen
2015-10-13 12:32 ` Mark Brown
2015-10-13 15:33 ` Caleb Crome
2015-10-13 15:37 ` 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=1444383296.2479.8.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bernard.gautier@intel.com \
--cc=caleb@crome.org \
--cc=han.lu@intel.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.