From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: vinod.koul@intel.com, Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-omap@vger.kernel.org, misael.lopez@ti.com
Subject: Re: [PATCH v2 0/2] dmaengine: ti-dma-crossbar: Support for eDMA
Date: Wed, 1 Jul 2015 15:41:26 +0300 [thread overview]
Message-ID: <5593DFF6.4090100@ti.com> (raw)
In-Reply-To: <1433769762-31827-1-git-send-email-peter.ujfalusi@ti.com>
Hi,
On 06/08/2015 04:22 PM, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v01:
> - Drop change in compatible for the crossbar driver and do the configuration
> based on the DT structure.
>
> 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 sDMA driver expects to get the DMA request line with offset 1. The eDMA
> stack does not need the offset.
> The crosbbar itself is identical for sDMA and eDMA.
> At probe time the driver will do a match to figure out which dma engine it is
> connected to and based on that information it will configure the offset needed
> by the DMA driver.
Gentle ping, it has been almost a month ago this series has been sent.
> Regards,
> Peter
> ---
> Misael Lopez Cruz (1):
> dmaengine: ti-dma-crossbar: Make idr xbar instance-specific
>
> Peter Ujfalusi (1):
> dmaengine: ti-dma-crossbar: Add support for eDMA
>
> drivers/dma/ti-dma-crossbar.c | 34 +++++++++++++++++++++++++++++-----
> 1 file changed, 29 insertions(+), 5 deletions(-)
>
--
Péter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vinod.koul@intel.com>, Tony Lindgren <tony@atomide.com>
Cc: <linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <misael.lopez@ti.com>
Subject: Re: [PATCH v2 0/2] dmaengine: ti-dma-crossbar: Support for eDMA
Date: Wed, 1 Jul 2015 15:41:26 +0300 [thread overview]
Message-ID: <5593DFF6.4090100@ti.com> (raw)
In-Reply-To: <1433769762-31827-1-git-send-email-peter.ujfalusi@ti.com>
Hi,
On 06/08/2015 04:22 PM, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v01:
> - Drop change in compatible for the crossbar driver and do the configuration
> based on the DT structure.
>
> 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 sDMA driver expects to get the DMA request line with offset 1. The eDMA
> stack does not need the offset.
> The crosbbar itself is identical for sDMA and eDMA.
> At probe time the driver will do a match to figure out which dma engine it is
> connected to and based on that information it will configure the offset needed
> by the DMA driver.
Gentle ping, it has been almost a month ago this series has been sent.
> Regards,
> Peter
> ---
> Misael Lopez Cruz (1):
> dmaengine: ti-dma-crossbar: Make idr xbar instance-specific
>
> Peter Ujfalusi (1):
> dmaengine: ti-dma-crossbar: Add support for eDMA
>
> drivers/dma/ti-dma-crossbar.c | 34 +++++++++++++++++++++++++++++-----
> 1 file changed, 29 insertions(+), 5 deletions(-)
>
--
Péter
next prev parent reply other threads:[~2015-07-01 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 13:22 [PATCH v2 0/2] dmaengine: ti-dma-crossbar: Support for eDMA Peter Ujfalusi
2015-06-08 13:22 ` Peter Ujfalusi
2015-06-08 13:22 ` [PATCH v2 1/2] dmaengine: ti-dma-crossbar: Make idr xbar instance-specific Peter Ujfalusi
2015-06-08 13:22 ` Peter Ujfalusi
2015-06-08 13:22 ` [PATCH v2 2/2] dmaengine: ti-dma-crossbar: Add support for eDMA Peter Ujfalusi
2015-06-08 13:22 ` Peter Ujfalusi
2015-07-01 12:41 ` Peter Ujfalusi [this message]
2015-07-01 12:41 ` [PATCH v2 0/2] dmaengine: ti-dma-crossbar: Support " Peter Ujfalusi
2015-07-02 15:56 ` Vinod Koul
2015-07-03 14:10 ` Peter Ujfalusi
2015-07-03 14:10 ` Peter Ujfalusi
2015-07-06 13:06 ` Vinod Koul
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=5593DFF6.4090100@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=misael.lopez@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.