From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Marek Vašut" <marex@denx.de>,
alsa-devel@alsa-project.org,
"Clemens Ladisch" <clemens@ladisch.de>
Subject: Re: aplay lists both Playback and Capture devices
Date: Sat, 1 Jun 2013 23:09:55 +0100 [thread overview]
Message-ID: <20130601220955.GX16790@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5Cn6ANtrb675v7A90aRsS1+L7nB3RaN+vp_OJc+FROF9g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]
On Sat, Jun 01, 2013 at 06:36:49PM -0300, Fabio Estevam wrote:
> On Sat, Jun 1, 2013 at 6:05 PM, Mark Brown <broonie@kernel.org> wrote:
> > If it's not got any playback or capture capabilities.
> On mx28evk there are two DAIs connected to a single sgtl5000:
> - One corresponds to the serial audio interface 0 (SAIF0) and it is
> playback only
> - The other corresponds to the serial audio interface 1 (SAIF1) and it
> is capture only.
These are not DAIs, they are DAI links. The capabilities of the links
should be being worked out by examining
> Should I create and pass device tree bindings like "playback-only" and
> "capture-only", so that we can avoid having both playback and capture
> capabilities for SAIF0 and SAIF1?
No, it's not sensible to require users to set DT properties for basic
features of the harwdare. If for some reason the interface could be
bidirectional but the board design breaks that for some reason then it
may make sense but otherwise the kernel ought to be able to work this
out based on the fact that one or both ends of the link can only do one
direction.
> Or is there already a mechanism in place that I can use to configure a
> DAI as unidirectional?
How is the kernel currently managing to get properties for playback?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-06-01 22:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 21:32 aplay lists both Playback and Capture devices Fabio Estevam
2013-05-30 10:43 ` Mark Brown
2013-05-30 11:23 ` Clemens Ladisch
2013-06-01 18:02 ` Fabio Estevam
2013-06-01 18:09 ` Fabio Estevam
2013-06-01 19:06 ` Mark Brown
2013-06-01 19:20 ` Fabio Estevam
2013-06-01 21:05 ` Mark Brown
2013-06-01 21:36 ` Fabio Estevam
2013-06-01 22:09 ` Mark Brown [this message]
2013-06-01 21:42 ` Marek Vasut
2013-06-01 22:12 ` 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=20130601220955.GX16790@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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