linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: svenkatr@ti.com (Venkatraman S)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/03] omap hsmmc: adaptation of sdma descriptor autoloading feature
Date: Thu, 11 Mar 2010 16:22:19 +0530	[thread overview]
Message-ID: <618f0c911003110252i36d6fc31wbaef4ad7a17565b1@mail.gmail.com> (raw)
In-Reply-To: <011301cac0b6$542b1190$544ff780@am.dhcp.ti.com>

Madhusudhan <madhu.cr@ti.com> wrote:
>> -----Original Message-----
>> From: linux-mmc-owner at vger.kernel.org [mailto:linux-mmc-
>> owner at vger.kernel.org] On Behalf Of Venkatraman S
>> Sent: Monday, March 01, 2010 5:27 AM
>> To: linux-mmc at vger.kernel.org; linux-arm-kernel at lists.infradead.org;
>> linux-omap at vger.kernel.org
>> Subject: [PATCH 03/03] omap hsmmc: adaptation of sdma descriptor
>> autoloading feature
>>
>> Start to use the sDMA descriptor autoloading feature.
>> For large datablocks, the MMC driver has to repeatedly setup, program
>> and teardown the
>> dma channel for each element of the sglist received in omap_hsmmc_request.
>>
>> By using descriptor autoloading, transfers from / to each element of
>> the sglist is pre programmed
>> into a linked list. The sDMA driver completes the entire transaction
>> and provides a single interrupt.
>>
>> Due to this, number of dma interrupts for a typical 100MB transfer on the
>> MMC is
>> reduced from 25000 to about 400 (approximate). Transfer speeds are
>> improved by ~5%
>> (Though it varies on the size of read / write & improves on huge
>> transfers)
>>
>> Descriptor autoloading is available only in 3630 and 4430 (as of now).
>> Hence normal DMA
>> mode is also retained.
>>
>> Tested on omap4430 sdp.
>>
>> Signed-off-by: Venkatraman S <svenkatr@ti.com>
>
> I don't see any issues with this patch except the concern I had on the first
> patch in the series. Why is that change linked to this series?
>
  Thanks. The problem was seen only in the context of using descriptor
load. Would
you prefer that I post it as a separate patch ?
Regards,
Venkat.

  reply	other threads:[~2010-03-11 10:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 11:27 [PATCH 03/03] omap hsmmc: adaptation of sdma descriptor autoloading feature Venkatraman S
2010-03-11  1:01 ` Madhusudhan
2010-03-11 10:52   ` Venkatraman S [this message]
2010-03-11 16:27     ` Madhusudhan
2010-03-11 17:42       ` Venkatraman S
2010-03-12  2:29         ` Madhusudhan
2010-03-12  6:03           ` Venkatraman S
  -- strict thread matches above, loose matches on Subject: below --
2010-03-10 14:12 Venkatraman S
2010-03-10 22:41 ` Tony Lindgren
2010-03-11 15:08   ` Venkatraman S
2010-03-11 18:39     ` Tony Lindgren
2010-03-12  8:18       ` Venkatraman S

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=618f0c911003110252i36d6fc31wbaef4ad7a17565b1@mail.gmail.com \
    --to=svenkatr@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).