alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Richard Röjfors" <richard.rojfors@mocean-labs.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsa: Add support for timberdale I2S block
Date: Mon, 1 Feb 2010 16:46:24 +0000	[thread overview]
Message-ID: <20100201164624.GA21643@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <4B66F146.2050201@mocean-labs.com>

On Mon, Feb 01, 2010 at 04:20:38PM +0100, Richard Röjfors wrote:
> Mark Brown wrote:

> > 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?

Presumably there's nothing intrinsic in the hardware which makes this
specific to bluetooth and other radios?  If it's just vanilla I2S out
I'd be shocked if nobody ever decided to hook it up to a CODEC for some
reason or other, even if that CODEC is just being used to hook up to an
analogue baseband that's been selected for some reason.

In any case, due to mobile phones things like the bluetooth are getting
represented in ASoC and it's trivial to provide a stub for them where
they aren't so it seems sensible to have the option to hook the device
up in ASoC.

      reply	other threads:[~2010-02-01 16:46 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   ` [PATCH] alsa: Add support for timberdale I2S block Richard Röjfors
2010-02-01 16:46     ` 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=20100201164624.GA21643@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=richard.rojfors@mocean-labs.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).