mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Dan Williams <dan.j.williams@intel.com>,
	Vinod Koul <vinod.koul@intel.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Warren <swarren@nvidia.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH V4] dma: add dma_get_any_slave_channel(), for use in of_xlate()
Date: Tue, 03 Dec 2013 10:50:31 -0700	[thread overview]
Message-ID: <529E19E7.8090402@wwwdotorg.org> (raw)
In-Reply-To: <1385494851-22640-1-git-send-email-swarren@wwwdotorg.org>

On 11/26/2013 12:40 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
> 
> mmp_pdma.c implements a custom of_xlate() function that is 95% identical
> to what Tegra will need. Create a function to implement the common part,
> so everyone doesn't just cut/paste the implementation.
> 
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vinod Koul <vinod.koul@intel.com>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Cc: dmaengine@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> v3:
> * Re-implemented the common code as dma_get_any_slave_channel(), in
>   dmaengine.c. This allows it to mutex_lock(&dma_list_mutex), and hence
>   avoid the retry loop.
> * Rather than having the common code call out to a driver-provided
>   callback at the tail (which avoided drivers having to implement an
>   of_xlate function themselves), have drivers implement a custom
>   of_xlate() again, which mostly just calls the new
>   dma_get_any_slave_channel(), then does any extra custom work.
> 
> v2:
> * Squashed the conversion of mmp_pdma.c into the patch that added the
>   common implementation, so it's easier to see the whole conversion in
>   one go.
> 
> This patch is a dependency for a series that reworks many of the Tegra
> drivers.
> 
> As such, it needs to go into a topic branch on its own, based directly
> on 3.13-rc1. If the DMA maintainers ack the patches I'm happy to create
> this topic branch myself and send a pull request to the DMA tree. Or the
> patches can be applied to a topic branch by the DMA maintainers and I
> will merge their topic branch into the Tegra rework branch that I
> mentioned.
> 
> Note that this patch is independant from the "dma: add channel request
> API that supports deferred probe" which I just sent, so it could
> (should?) be a different topic branch.

Vinod, does this patch look OK to you? Are you able to stage it into a
topic branch that I can pull into the Tegra tree as a dependency?

  reply	other threads:[~2013-12-03 17:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 19:40 Stephen Warren
2013-12-03 17:50 ` Stephen Warren [this message]
2013-12-10 12:22 ` Vinod Koul
2013-12-10 17:05   ` Stephen Warren

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=529E19E7.8090402@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=vinod.koul@intel.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

Powered by JetHome