alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux@fluff.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, jassisinghbrar@gmail.com,
	Jassi Brar <jassi.brar@samsung.com>,
	ben-linux@fluff.org
Subject: Re: [PATCH 4/7] ASoC: S3C64XX: USE DMA info from platform data
Date: Thu, 28 Jan 2010 04:27:15 +0000	[thread overview]
Message-ID: <20100128042715.GR10014@trinity.fluff.org> (raw)
In-Reply-To: <20091209110024.GC19851@opensource.wolfsonmicro.com>

On Wed, Dec 09, 2009 at 11:00:24AM +0000, Mark Brown wrote:
> On Wed, Dec 09, 2009 at 01:29:38PM +0900, jassisinghbrar@gmail.com wrote:
> > From: Jassi Brar <jassi.brar@samsung.com>
> 
> > Instead of hardcoding DMA channel numbers and address, for each controller
> > in the driver, let the information be read from platform data.
> 
> > Signed-off-by: Jassi Brar <jassi.brar@samsung.com>
> 
> OK, but this needs to go along with the arch/arm side to avoid breaking
> the driver.

I've applied the arch/arm side of the patch already, as this was quite
eassy to do. It is then a case of whether I should take the patch to
remove it from sound/soc/s3c24xx/s3c64xx-i2s.c or should we wait until
my/rmk's tree has been merged into the mainline?

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-01-28  4:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09  4:29 [PATCH 4/7] ASoC: S3C64XX: USE DMA info from platform data jassisinghbrar
2009-12-09 11:00 ` Mark Brown
2010-01-28  4:27   ` Ben Dooks [this message]
2010-01-28  6:38     ` jassi brar

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=20100128042715.GR10014@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jassi.brar@samsung.com \
    --cc=jassisinghbrar@gmail.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 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).