From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: marex@denx.de, Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] ASoC: mxs: mxs-saif: Fix the playback/record capabilities
Date: Mon, 3 Jun 2013 16:41:45 +0100 [thread overview]
Message-ID: <20130603154145.GO31367@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5BVwMM2Q3CAoepmc0dQgHDARKoUuUrab--Y=6WNm-GA1Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]
On Mon, Jun 03, 2013 at 12:18:16PM -0300, Fabio Estevam wrote:
> On Mon, Jun 3, 2013 at 12:07 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
> > I think the sgtl5000 has a single bidirectional DAI, but I'd assume that it
> Yes, correct.
So this comes from the board wiring then.
> > 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.
> Yes, I think that adding a device tree property specifying the SAIF
> direction could do the trick.
No, this should be done at the board level as Lars-Peter suggests - it's
nothing to do with the SAIF driver. Probably doesn't even need to go
into device tree, just do it in the machine driver.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2013-06-03 15:41 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
2013-06-03 15:18 ` Fabio Estevam
2013-06-03 15:41 ` 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=20130603154145.GO31367@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
--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