All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jyri Sarha <oku@iki.fi>
Cc: Darren Etheridge <detheridge@ti.com>,
	alsa-devel@alsa-project.org, Joel Fernandes <joelf@ti.com>,
	Jyri Sarha <jsarha@ti.com>,
	"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: Thu, 12 Sep 2013 12:08:00 +0100	[thread overview]
Message-ID: <20130912110800.GI29403@sirena.org.uk> (raw)
In-Reply-To: <d56ff517b8d6e29af7639665bb17c1bb@kapsi.fi>


[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]

On Wed, Sep 11, 2013 at 02:48:19PM +0300, Jyri Sarha wrote:

> I have not studied the code enough to give a good work estimate about
> the conversion, but at least the current EDMA driver would need cyclic
> mode to be implemented before the conversion would be possible. It may

The other option is to support non-cyclic mode in the generic code.

> However, after taking a another look at the added DT bindings, I think
> we could survive with mcasp dma register addresses only for now. To my
> understanding those are anyway need in mcasp node. In DT boot the
> mcasp EDMA event queue could be hardcoded to the highest priority for
> now.

> How does this sound?

I'm not clear what that means in concrete terms, sorry.  Do you mean you
can just use the existing register ranges for the McASP?  Please bear in
mind that I don't really know anything about this hardware.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2013-09-12 11:08 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 [this message]
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
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=20130912110800.GI29403@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=detheridge@ti.com \
    --cc=gururaja.hebbar@ti.com \
    --cc=joelf@ti.com \
    --cc=jsarha@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.