devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: vinod.koul@intel.com, Tony Lindgren <tony@atomide.com>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	dmaengine@vger.kernel.org, linux-omap@vger.kernel.org,
	misael.lopez@ti.com
Subject: Re: [PATCH 0/3] dmaengine: ti-dma-crossbar: Support for eDMA
Date: Fri, 5 Jun 2015 19:17:17 +0300	[thread overview]
Message-ID: <5571CB8D.7030401@ti.com> (raw)
In-Reply-To: <1433518474-26628-1-git-send-email-peter.ujfalusi@ti.com>

On 06/05/2015 06:34 PM, Peter Ujfalusi wrote:
> Hi,
> 
> The ti-dma-crossbar driver in it's current form can work when it is used with
> sDMA (omap-dma). On DRA7x class of devices we have both sDMA and eDMA available.
> The DT bindings for sDMA has been done in a way that DMA users need to specify
> the required DMA request number + 1 when they request for channel and the driver
> stack has been written in this way also for sDMA.
> Since right now we do not have the crossbar enabled we can still change the
> compatible string to reflect the crossbar use. The TRM also refers the crossbars
> in this way.

Now that I have sent this series...
Would it be better to not touch the compatible strings, but add of_device_id
table in the ti-dma-crossbar driver containing the supported dma controllers,
like "ti,omap4430-sdma" and "ti,edma3" and to of_match_node() against the node
we got via dma-masters?

So we would keep the ti,dra7-dma-crossbar and depending on where the
dma-masters point us we can decide in the code on how to handle?

Just a thought.

> 
> Regards,
> Peter
> ---
> Misael Lopez Cruz (2):
>   dmaengine: ti-dma-crossbar: Make idr xbar instance-specific
>   dmaengine: ti-dma-crossbar: Add support for eDMA xbar
> 
> Peter Ujfalusi (1):
>   dmaengine: ti-dma-crossbar: Change the compatible string to
>     ti,dra7-sdma-crossbar
> 
>  Documentation/devicetree/bindings/dma/dma.txt      |  2 +-
>  .../devicetree/bindings/dma/ti-dma-crossbar.txt    |  5 +--
>  drivers/dma/ti-dma-crossbar.c                      | 37 ++++++++++++++++------
>  3 files changed, 31 insertions(+), 13 deletions(-)
> 


-- 
Péter

      parent reply	other threads:[~2015-06-05 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 15:34 [PATCH 0/3] dmaengine: ti-dma-crossbar: Support for eDMA Peter Ujfalusi
2015-06-05 15:34 ` [PATCH 1/3] dmaengine: ti-dma-crossbar: Change the compatible string to ti,dra7-sdma-crossbar Peter Ujfalusi
2015-06-05 15:34 ` [PATCH 2/3] dmaengine: ti-dma-crossbar: Make idr xbar instance-specific Peter Ujfalusi
2015-06-05 15:34 ` [PATCH 3/3] dmaengine: ti-dma-crossbar: Add support for eDMA xbar Peter Ujfalusi
2015-06-05 16:17 ` Peter Ujfalusi [this message]

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=5571CB8D.7030401@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=misael.lopez@ti.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).