alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: alsa-devel@alsa-project.org
Cc: broonie@opensource.wolfsonmicro.com, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: About the platform_name field in snd_soc_dai_link
Date: Tue, 10 Aug 2010 15:38:18 +0200	[thread overview]
Message-ID: <20100810133818.GL27749@pengutronix.de> (raw)

Hi,

I'm wondering what exactly a snd_soc_platform is. Apparently the
snd_pcm_ops/pcm_new/pcm_free are specific to a platform. For my
understanding these operations are more specific to a cpu_dai. Looking
at the tree it seems that each cpu_dai has exactly one possible
platform, which seems logical to me because the cpu_dai knows how to
transfer the data.

My problem on i.MX is that I currently have two possible cpu dais
(imx-ssi.[01]) and each can be configured to use dma or fiq depending
on the dma capabilities. So the cpu_dai knows which pcm_ops we have
to use, but currently it's the soc glue code which has to decide in
platform_name. Am I understanding something wrong here?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

             reply	other threads:[~2010-08-10 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 13:38 Sascha Hauer [this message]
2010-08-10 13:47 ` About the platform_name field in snd_soc_dai_link Mark Brown
2010-08-10 14:09   ` Sascha Hauer
2010-08-10 14:16   ` Liam Girdwood
2010-08-10 14:42     ` Mark Brown
2010-08-10 14:49       ` Liam Girdwood
2010-08-11 11:39     ` Sascha Hauer

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=20100810133818.GL27749@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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).