From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux@arm.linux.org.uk, tony@atomide.com,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] dmaengine:omap-dma: Linked List transfer for slave_sg
Date: Wed, 10 Aug 2016 23:02:36 +0530 [thread overview]
Message-ID: <20160810173235.GI9681@localhost> (raw)
In-Reply-To: <20160720085032.2955-1-peter.ujfalusi@ti.com>
On Wed, Jul 20, 2016 at 11:50:26AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - dropped the patch changing the sequence of vchan_cookie_complete and
> omap_dma_start_sg in omap_dma_callback
> - Use appropriate macros to find omap_chan and omap_desc in patch 6
> - Use per-device pool instead of per-channel pools.
>
> The following series with the final patch will add support for sDMA Linked List
> transfer support.
> Linked List is supported by sDMA in OMAP3630+ (OMAP4/5, dra7 family).
> If the descriptor load feature is present we can create the descriptors for each
> SG beforehand and let sDMA to walk them through.
> This way the number of sDMA interrupts the kernel need to handle will drop
> dramatically.
Applied all, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] dmaengine:omap-dma: Linked List transfer for slave_sg
Date: Wed, 10 Aug 2016 23:02:36 +0530 [thread overview]
Message-ID: <20160810173235.GI9681@localhost> (raw)
In-Reply-To: <20160720085032.2955-1-peter.ujfalusi@ti.com>
On Wed, Jul 20, 2016 at 11:50:26AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - dropped the patch changing the sequence of vchan_cookie_complete and
> omap_dma_start_sg in omap_dma_callback
> - Use appropriate macros to find omap_chan and omap_desc in patch 6
> - Use per-device pool instead of per-channel pools.
>
> The following series with the final patch will add support for sDMA Linked List
> transfer support.
> Linked List is supported by sDMA in OMAP3630+ (OMAP4/5, dra7 family).
> If the descriptor load feature is present we can create the descriptors for each
> SG beforehand and let sDMA to walk them through.
> This way the number of sDMA interrupts the kernel need to handle will drop
> dramatically.
Applied all, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux@arm.linux.org.uk, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org, tony@atomide.com
Subject: Re: [PATCH v2 0/6] dmaengine:omap-dma: Linked List transfer for slave_sg
Date: Wed, 10 Aug 2016 23:02:36 +0530 [thread overview]
Message-ID: <20160810173235.GI9681@localhost> (raw)
In-Reply-To: <20160720085032.2955-1-peter.ujfalusi@ti.com>
On Wed, Jul 20, 2016 at 11:50:26AM +0300, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - dropped the patch changing the sequence of vchan_cookie_complete and
> omap_dma_start_sg in omap_dma_callback
> - Use appropriate macros to find omap_chan and omap_desc in patch 6
> - Use per-device pool instead of per-channel pools.
>
> The following series with the final patch will add support for sDMA Linked List
> transfer support.
> Linked List is supported by sDMA in OMAP3630+ (OMAP4/5, dra7 family).
> If the descriptor load feature is present we can create the descriptors for each
> SG beforehand and let sDMA to walk them through.
> This way the number of sDMA interrupts the kernel need to handle will drop
> dramatically.
Applied all, thanks
--
~Vinod
next prev parent reply other threads:[~2016-08-10 17:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:50 [PATCH v2 0/6] dmaengine:omap-dma: Linked List transfer for slave_sg Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` [PATCH v2 1/6] dmaengine: omap-dma: Simplify omap_dma_start_sg parameter list Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` [PATCH v2 2/6] dmaengine: omap-dma: Simplify omap_dma_callback Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` [PATCH v2 3/6] dmaengine: omap-dma: Dynamically allocate memory for lch_map Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` [PATCH v2 4/6] dmaengine: omap-dma: Add more debug information when freeing channel Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` [PATCH v2 5/6] dmaengine: omap-dma: Use pointer to omap_sg in slave_sg setup's loop Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` [PATCH v2 6/6] dmaengine: omap-dma: Support for LinkedList transfer of slave_sg Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-07-20 8:50 ` Peter Ujfalusi
2016-08-08 5:42 ` Vinod Koul
2016-08-08 5:42 ` Vinod Koul
2016-08-08 13:58 ` Peter Ujfalusi
2016-08-08 13:58 ` Peter Ujfalusi
2016-08-08 13:58 ` Peter Ujfalusi
2016-08-10 17:32 ` Vinod Koul [this message]
2016-08-10 17:32 ` [PATCH v2 0/6] dmaengine:omap-dma: Linked List transfer for slave_sg Vinod Koul
2016-08-10 17:32 ` 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=20160810173235.GI9681@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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.