From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Jamie Iles <jamie.iles@picochip.com>
Subject: Re: [PATCH repost 2/4] dmaengine/dw_dmac: allow src/dst masters to be configured at runtime
Date: Mon, 24 Jan 2011 15:54:57 +0100 [thread overview]
Message-ID: <1295880898.2903.2.camel@hcegtvedt> (raw)
In-Reply-To: <1295619115-18420-3-git-send-email-jamie@jamieiles.com>
On Fri, 2011-01-21 at 14:11 +0000, Jamie Iles wrote:
> Some platforms have flexible mastering capabilities and this needs
> to be selected at runtime. If the platform has specified private
> data in the form of the dw_dma_slave then fetch the source and
> destination masters from here. If this isn't present, default to
> the previous of 0 and 1.
>
> v2: cleanup whitespace
>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
> Signed-off-by: Jamie Iles <jamie.iles@picochip.com>
Acked-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
<snipp>
--
Hans-Christian Egtvedt
next prev parent reply other threads:[~2011-01-24 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 14:11 [PATCH repost 0/4] dmaengine/dw_dmac: enhancements to allow use Jamie Iles
2011-01-21 14:11 ` [PATCH repost 1/4] dmaengine/dw_dmac: don't scan descriptors if no xfers in progress Jamie Iles
2011-01-21 14:11 ` [PATCH repost 2/4] dmaengine/dw_dmac: allow src/dst masters to be configured at runtime Jamie Iles
2011-01-24 14:54 ` Hans-Christian Egtvedt [this message]
2011-01-21 14:11 ` [PATCH repost 3/4] dmaengine/dw_dmac: provide a mechanism to indicate private devices Jamie Iles
2011-01-21 14:11 ` [PATCH repost 4/4] avr32: at32ap700x: specify DMA src and dst masters Jamie Iles
2011-01-24 14:59 ` Hans-Christian Egtvedt
2011-01-30 6:33 ` Dan Williams
2011-02-04 11:06 ` Jamie Iles
2011-02-21 13:45 ` Hans-Christian Egtvedt
2011-02-21 14:45 ` Jamie Iles
2011-03-15 14:56 ` Jamie Iles
2011-03-16 2:08 ` Koul, Vinod
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=1295880898.2903.2.camel@hcegtvedt \
--to=hans-christian.egtvedt@atmel.com \
--cc=dan.j.williams@intel.com \
--cc=jamie.iles@picochip.com \
--cc=jamie@jamieiles.com \
--cc=linux-kernel@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