public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brown <davidb@codeaurora.org>
To: "Subhash Jadavani" <subhashj@codeaurora.org>
Cc: "'Daniel Walker'" <dwalker@fifo99.com>, <cjb@laptop.org>,
	<linux-mmc@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<bryanh@codeaurora.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] mmc: msm_sdcc: Use SPS BAM as DMA engine
Date: Thu, 24 Mar 2011 15:45:46 -0700	[thread overview]
Message-ID: <8yak4fo16jp.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <005601cbe9f5$a5088750$ef1995f0$@org> (Subhash Jadavani's message of "Thu, 24 Mar 2011 13:02:31 +0530")

On Thu, Mar 24 2011, Subhash Jadavani wrote:

> Here "DMA engine" means we are using SPS BAM as DMA HW.

> No, we are not using the "drivers/dma/dmaengine.c" because MSM SPS
> driver is not exporting the dma compliant APIs to client. We are using
> the MSM SPS driver's exported APIs directly from our driver. Not sure
> what extra description we can put it in commit text. Any suggestion?

I think the commit text should explain why this driver doesn't just use
the DMA engine API.  People are going to want to know that later on as
well.  I know you did an analysis for this driver, and it would be good
to include that information in the commit text.  Email me privately if
you want some help with that.

Currently none of the MSM DMA hardware uses the DMA engine API, and I
think we need to figure out if we want to move to that at some point.  I
realize that the hardware (especially SPS BAM) does a lot more than
regular DMA, this may involve extending DMA engine, which may or may not
be appropriate.

Thanks,
David

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-03-24 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 13:24 [RFC] mmc: msm_sdcc: Use SPS BAM as DMA engine Subhash Jadavani
2011-03-18 13:24 ` Subhash Jadavani
2011-03-23 13:05   ` Daniel Walker
2011-03-24  7:32     ` Subhash Jadavani
2011-03-24 22:45       ` David Brown [this message]
2011-03-29  4:30         ` Koul, Vinod
2011-03-24  7:37     ` Subhash Jadavani

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=8yak4fo16jp.fsf@huya.qualcomm.com \
    --to=davidb@codeaurora.org \
    --cc=bryanh@codeaurora.org \
    --cc=cjb@laptop.org \
    --cc=dwalker@fifo99.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=subhashj@codeaurora.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