Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>
Cc: marex@denx.de, Fabio Estevam <fabio.estevam@freescale.com>,
	alsa-devel@alsa-project.org, Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH] ASoC: mxs: mxs-saif: Fix the playback/record capabilities
Date: Mon, 03 Jun 2013 17:07:57 +0200	[thread overview]
Message-ID: <51ACB14D.2050205@metafoo.de> (raw)
In-Reply-To: <20130603092028.GD31367@sirena.org.uk>

On 06/03/2013 11:20 AM, Mark Brown wrote:
> On Sun, Jun 02, 2013 at 09:56:29PM +0200, Lars-Peter Clausen wrote:
> 
>> Not sure if this is the right approach, there is no limitation on either
>> saif0 or saif1 that it can only be used for capture or playback. Some
>> systems may use saif1 as playback and saif0 as capture, or both as playback
>> and so on...
> 
> Is there a limitation on the CODEC side or does the CODEC side have a
> single bidirectional interface?

I think the sgtl5000 has a single bidirectional DAI, but I'd assume that it
is not the only CODEC to be ever used with the mxs-saif. In my opinion a
better solution is to add support for being able to specify if a
snd_soc_dai_link is used playback, capture or both.

- Lars

  reply	other threads:[~2013-06-03 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 16:38 [PATCH] ASoC: mxs: mxs-saif: Fix the playback/record capabilities Fabio Estevam
2013-06-02 19:56 ` Lars-Peter Clausen
2013-06-03  9:20   ` Mark Brown
2013-06-03 15:07     ` Lars-Peter Clausen [this message]
2013-06-03 15:18       ` Fabio Estevam
2013-06-03 15:41         ` 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=51ACB14D.2050205@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=marex@denx.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