From: Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Jean-Francois Moine <moinejf-GANU6spQydw@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>,
Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Jaroslav Kysela <perex-/Fr2/VpizcU@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ASoC: kirkwood: add S/PDIF support
Date: Fri, 18 Oct 2013 15:27:40 +0100 [thread overview]
Message-ID: <20131018142740.GY25034@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131018134829.GQ2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Fri, Oct 18, 2013 at 02:48:29PM +0100, Mark Brown wrote:
> On Fri, Oct 18, 2013 at 01:56:38PM +0100, Russell King - ARM Linux wrote:
>
> > Let me remind you that I had a definition of what a front end and a back
> > end DAI was from Liam, and your definition is at odds with that.
>
> Could you please provide some detail on this? I was aware that you were
> for a time confused about this but had not been aware of the source of
> the confusion.
Let's see:
16:10 < rmk> broonie: can you explain this pcm frontend/backend stuff in
asoc. what exactly is a frontend and backend pcm, and how do they
relate to the CPU hardware and codec links? Which are the ones
which are given ALSA PCMs?
17:22 < broonie> rmk: A front end is the bit that does DMA from memory, a
back end is a physical interface.
17:22 < broonie> The bit in the middle is usually a DSP.
17:23 < broonie> To be frank I've not actually *used* this stuff myself
except in bolting a new CODEC on the edge of it during system
integrations - going to be rectifying that very soon with the
Samsung drivers I hope.
17:24 < broonie> But the general idea is that the front end is what the
application sees, the back end is what comes out of the hardware
at the other end.
17:25 < broonie> And the bit in the middle does any routing an rewriting
of formats between the two.
17:26 < broonie> (The Samsung picture should be very similar to Kirkwood
but the opposite way around - two front ends mixed togther to a
single back end)
...
16:49 < rmk> oh, another question
16:49 < rmk> .dynamic in the dai link structure, that's for backends only,
right?
16:50 < broonie> Think so, yes.
16:52 < rmk> hmm
16:52 < rmk> if (rtd->dai_link->dynamic) {
16:52 < rmk> rtd->ops.open = dpcm_fe_dai_open;
16:52 < rmk> probably needed for frontends
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-18 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 10:41 [PATCH] ASoC: kirkwood: add S/PDIF support Jean-Francois Moine
2013-09-24 10:51 ` Russell King - ARM Linux
[not found] ` <20130924105127.GB12758-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2013-09-24 15:37 ` Mark Brown
2013-09-24 16:32 ` Jean-Francois Moine
2013-10-18 0:34 ` Mark Brown
[not found] ` <20131018003439.GG2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-18 10:30 ` Russell King - ARM Linux
[not found] ` <20131018103019.GW25034-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2013-10-18 12:48 ` Mark Brown
[not found] ` <20131018124832.GK2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-18 12:56 ` Russell King - ARM Linux
[not found] ` <20131018125638.GX25034-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2013-10-18 13:48 ` Mark Brown
[not found] ` <20131018134829.GQ2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-18 14:27 ` Russell King - ARM Linux [this message]
2013-10-18 14:33 ` Russell King - ARM Linux
2013-10-18 15:38 ` Jean-Francois Moine
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=20131018142740.GY25034@n2100.arm.linux.org.uk \
--to=linux-lfz/pmaqli7xmaaqvzeohq@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=moinejf-GANU6spQydw@public.gmane.org \
--cc=perex-/Fr2/VpizcU@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=tiwai-l3A5Bk7waGM@public.gmane.org \
/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).