From: "Richard Röjfors" <richard.rojfors@mocean-labs.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, alsa-devel@vger.kernel.org
Subject: Re: [PATCH] alsa: Add support for timberdale I2S block
Date: Mon, 01 Feb 2010 16:20:38 +0100 [thread overview]
Message-ID: <4B66F146.2050201@mocean-labs.com> (raw)
In-Reply-To: <20091026130931.GA18781@sirena.org.uk>
Mark Brown wrote:
> On Mon, Oct 26, 2009 at 02:02:57PM +0100, Richard R?jfors wrote:
>> This driver adds support for the I2S block of the timberdale FPGA.
>>
>> The timberdale is a FPGA found on intel development boards for
>> In-Vehicle Infotainment.
>>
>> The block has support for up to 8 I2S channels, can be clocked
>> from either the FPGA or the device side.
>>
>> This driver introduces support for this block, by exposing each
>> I2S channel as an ALSA PCM channel.
>>
>> Signed-off-by: Richard R?jfors <richard.rojfors@mocean-labs.com>
>
> Without having investigated in any great detail I'd really expect this
> driver to be done within ASoC if it's producing generic I2S output. If
> it's producing I2S out then presumably system designers will be able to
> attach whatever CODECs they desire and if those CODECs require any soft
> control then there will be a need to interoperate with CODEC drivers.
This thing produces raw I2S/captures raw I2S as you say. It's used to
connect to bluetooth chips and radio DSP:s. So there are no CODEC:s
involved. Does it make sense to do it within ASoC?
--Richard
next prev parent reply other threads:[~2010-02-01 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 13:02 [PATCH] alsa: Add support for timberdale I2S block Richard Röjfors
2009-10-26 13:09 ` Mark Brown
2009-10-30 11:53 ` Takashi Iwai
2009-11-02 18:26 ` ASoC updates for 2.6.33 Mark Brown
2009-11-03 7:02 ` Takashi Iwai
2010-02-01 15:20 ` Richard Röjfors [this message]
2010-02-01 16:46 ` [PATCH] alsa: Add support for timberdale I2S block 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=4B66F146.2050201@mocean-labs.com \
--to=richard.rojfors@mocean-labs.com \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-devel@vger.kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).