All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>,
	alsa-devel@alsa-project.org
Subject: Re: simple-audio-card vs. platform question
Date: Tue, 27 Jan 2015 13:29:03 +0100	[thread overview]
Message-ID: <54C7848F.6070903@metafoo.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1501271301400.11532@lnxricardw1.se.axis.com>

On 01/27/2015 01:01 PM, Ricard Wanderlof wrote:
>
> I'm trying to set up a simple device tree framework so I can do some
> development on an I2S driver. I'm trying to use simple-audio-card, but I
> keep running into the problem that once soc_bind_dai_link() gets called,
> dai_link->platform is set to NULL (because it is not initialized by
> simple-card.c when there is a DT node), while dai_link->platform_of_node
> has been set to dai_link->cpu_of_node in asoc_simple_card_parse_of().
>
[...]
>
> I can't figure out either how to set up a platform (=DMA) driver in this
> environment. Perhaps the case of having a CPU DAI, DMA driver and codec
> DAI is not supported by simple-audio-card?
[...]

Usually in such a setup the CPU DAI driver also register the platform 
component. Which then as the same of_node as the CPU DAI and so the matching 
works. There are plenty of examples e.g. check the drivers using 
devm_snd_dmaengine_pcm_register().

- Lars

  reply	other threads:[~2015-01-27 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 12:01 simple-audio-card vs. platform question Ricard Wanderlof
2015-01-27 12:29 ` Lars-Peter Clausen [this message]
2015-01-27 16:31   ` Ricard Wanderlof
2015-01-27 18:11     ` Lars-Peter Clausen
2015-01-29  8:58       ` Ricard Wanderlof
2015-01-29 13:37         ` Lars-Peter Clausen
2015-01-29 17:05           ` Ricard Wanderlof

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=54C7848F.6070903@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ricard.wanderlof@axis.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.