public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "shekhar, chandra" <x0044955@ti.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2]  McBSP DMA support for  34xx
Date: Thu, 28 Aug 2008 16:50:59 +0530	[thread overview]
Message-ID: <01fe01c90900$26f83320$LocalHost@wipultra806> (raw)
In-Reply-To: 20080828135202.657264e6.jarkko.nikula@nokia.com


----- Original Message ----- 
From: "Jarkko Nikula" <jarkko.nikula@nokia.com>
To: "ext chandra shekhar" <x0044955@ti.com>
Cc: <linux-omap@vger.kernel.org>
Sent: Thursday, August 28, 2008 4:22 PM
Subject: Re: [PATCH 1/2] McBSP DMA support for 34xx


> On Thu, 28 Aug 2008 13:56:00 +0530 (IST)
> "ext chandra shekhar" <x0044955@ti.com> wrote:
>
>> This patch supports DMA chaining mode and one time configuration for
>> entire transfer to improve performance.
>> Signed-off-by: chandra shekhar <x0044955@ti.com>
>> ---
>>  arch/arm/mach-omap2/mcbsp.c       |  702 ++++++++++++++++++++++++++++
>> +++++++++- arch/arm/plat-omap/mcbsp.c        |   19 -
>>  include/asm-arm/arch-omap/mcbsp.h |  127 +++++-
>>  3 files changed, 811 insertions(+), 37 deletions(-)
>>
> Hi
>
> What's the expected use case for DMA chaining mode or existing driver
> which would get improved performance? There should have some reason why
> this amount of new lines should be added.

current McBSP ( arch/arm/plat-omap/mcbsp.c) code request and releases dma 
channel for each transfer .
so there is latency involved. Chaining help with smooth audio play because we 
can enque the buffer
while another transfer is ongoing.

>
> Also ideally this should cover also OMAP1's from 16xx onward since they
> can link DMA channels together as well?

Current code might even work for 16xx and later versions for 16 bit data. ( or 
can be extended to work on 16xx and later versions)
but i dont have board or TRM to check for any changes in DMA subsytem or McBSP. 
better to play safe.

2430 onwards McBSP dxr/drr is 32 bits, which allows 24 bit mono/stereo transfer 
easily. if we had to have 16 bit dxr1,2/drr1,2
then we will have to perform the manipulation on data for 24 bit ops. we will 
have to consider all the options before extending it to 16xx.

>
>
> Jarkko
> 


  reply	other threads:[~2008-08-28 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  8:26 [PATCH 1/2] McBSP DMA support for 34xx chandra shekhar
2008-08-28 10:10 ` Felipe Balbi
2008-08-28 10:52 ` Jarkko Nikula
2008-08-28 11:20   ` shekhar, chandra [this message]
2008-09-09 16:31     ` Tony Lindgren
2008-09-10 10:17       ` shekhar, chandra
2008-09-10 11:14         ` Jarkko Nikula
2008-09-10 11:44           ` shekhar, chandra
2008-09-24  9:28             ` Tony Lindgren

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='01fe01c90900$26f83320$LocalHost@wipultra806' \
    --to=x0044955@ti.com \
    --cc=jarkko.nikula@nokia.com \
    --cc=linux-omap@vger.kernel.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