From: jassi brar <jassisinghbrar@gmail.com>
To: Ben Dooks <ben-linux@fluff.org>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jassi Brar <jassi.brar@samsung.com>
Subject: Re: [PATCH 4/7] ASoC: S3C64XX: USE DMA info from platform data
Date: Thu, 28 Jan 2010 15:38:45 +0900 [thread overview]
Message-ID: <1b68c6791001272238q6f421a2dxc2522a06e8855889@mail.gmail.com> (raw)
In-Reply-To: <20100128042715.GR10014@trinity.fluff.org>
On Thu, Jan 28, 2010 at 1:27 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> 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?
btw, patch 5/7 http://mailman.alsa-project.org/pipermail/alsa-devel/2009-December/023782.html
is pending too for the same reason.
ofcourse, I will resend as you decide how to proceed.
thanks
prev parent reply other threads:[~2010-01-28 6:38 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
2010-01-28 6:38 ` jassi brar [this message]
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=1b68c6791001272238q6f421a2dxc2522a06e8855889@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jassi.brar@samsung.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).