From: Jyri Sarha <jsarha@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Darren Etheridge <detheridge@ti.com>,
alsa-devel@alsa-project.org, Joel Fernandes <joelf@ti.com>,
Jyri Sarha <oku@iki.fi>,
"Hebbar, Gururaja" <gururaja.hebbar@ti.com>,
liam.r.girdwood@linux.intel.com
Subject: Re: [PATCH RFC 3/8] ASoC: davinci-mcasp: Get DMA related properties from DT
Date: Fri, 13 Sep 2013 13:50:31 +0300 [thread overview]
Message-ID: <5232EDF7.2010000@ti.com> (raw)
In-Reply-To: <20130913103431.GG29403@sirena.org.uk>
On 09/13/2013 01:34 PM, Mark Brown wrote:
> On Thu, Sep 12, 2013 at 03:10:12PM +0300, Jyri Sarha wrote:
>> On 2013-09-12 14:56, Mark Brown wrote:
>
>>> What exactly is the dma register location here - what hardware is being
>>> controlled?
>
>> They is the McASP-bus receive/transmit buffer data port addresses.
>> So those
>> are McASP entity specific properties that need to be passed to
>> DMA-engine.
>
> OK, and presumably this is just part of the main McASP register block
> and doesn't need to go into DT?
>
Not really. For instance on am33xx SoCs the MPU usually accesses McASP
registers trough L4 interconnect, which is not accessible by DMA
controller. For DMA controller the data port is also mapped trough L3
bus to entirely different address and a simple register offset is not
enough. Naturally this mapping may change SoC to SoC.
I have been working with OMAP family chips so long that I start think
everybody would know their internal workings. Sorry about that.
Best regards,
Jyri
next prev parent reply other threads:[~2013-09-13 10:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 15:12 [PATCH RFC 0/8] Fix AM335x-evm analog audio support oku
2013-09-09 15:12 ` [PATCH RFC 1/8] ASoC: davinci-mcasp: Add pinctrl support oku
2013-09-09 15:19 ` Mark Brown
2013-09-09 15:12 ` [PATCH RFC 2/8] ASoC: davinci-evm: Add device tree binding oku
2013-09-09 15:21 ` Mark Brown
2013-09-11 10:38 ` Jyri Sarha
2013-09-11 11:35 ` Mark Brown
2013-09-11 18:02 ` Jyri Sarha
2013-09-12 11:47 ` Mark Brown
2013-09-09 15:12 ` [PATCH RFC 3/8] ASoC: davinci-mcasp: Get DMA related properties from DT oku
2013-09-09 15:25 ` Mark Brown
2013-09-11 11:48 ` Jyri Sarha
2013-09-12 11:08 ` Mark Brown
2013-09-12 11:34 ` Jyri Sarha
2013-09-12 11:56 ` Mark Brown
2013-09-12 12:10 ` Jyri Sarha
2013-09-13 10:34 ` Mark Brown
2013-09-13 10:50 ` Jyri Sarha [this message]
2013-09-13 17:53 ` Mark Brown
2013-09-09 15:12 ` [PATCH RFC 4/8] ASoC: davinci-mcasp: Extract DMA channels directly " oku
2013-09-09 15:12 ` [PATCH RFC 5/8] ASoC: davinci: Add support for AM33xx SoC Audio oku
2013-09-09 15:24 ` Mark Brown
2013-09-09 15:12 ` [PATCH RFC 6/8] ARM/dts: am33xx: Add mcasp0 and mcasp1 device tree entries oku
2013-09-09 15:27 ` Mark Brown
2013-09-09 15:12 ` [PATCH RFC 7/8] ARM/dts: am33xx: mcasp: Add new dma related properties oku
2013-09-09 15:12 ` [PATCH RFC 8/8] ARM/dts: am335x-evm: Add audio support for am335x-evm.dts oku
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=5232EDF7.2010000@ti.com \
--to=jsarha@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=detheridge@ti.com \
--cc=gururaja.hebbar@ti.com \
--cc=joelf@ti.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=oku@iki.fi \
/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.