[PATCH v5 0/3] DMA: Freescale: driver cleanups and enhancements
vinod.koul at intel.com
Tue Jul 15 02:05:26 EST 2014
On Wed, May 21, 2014 at 04:03:00PM +0800, hongbo.zhang at freescale.com wrote:
> From: Hongbo Zhang <hongbo.zhang at freescale.com>
> Hi Dan,
> Please have a look at this 3/3 as Vinod mentioned.
> Hi Vinod Koul,
> Please have a look at the v5 patch set.
I dont see any objection, so applying all 3 with subject changed to reflect
correct subsystem name
> v4 -> v5 changes:
> - since previous 5 of 8 patches have been merged by Vinod, this iteration oly
> inludes the last 3 patches of v4.
> - patches order is changed for being reviewed and merged easier.
> - remove the .prepare functions, and use the suspend_late and resume_early in
> the suspend-and-resume patch.
> v3 -> v4 changes:
> - Fixed a typo in [2/8] commit message.
> - There was a potential double call of list_del() when apply [4/8] only,
> although this defect is removed again in later [6/8]. This version
> eliminates this problem by updating [4/8] and [6/8] slightly.
> - Updated [8/8] to use register access method introduced by [2/8]
> v2 -> v3 change:
> Only add "chan->pm_state = RUNNING" for patch[8/8].
> v1 -> v2 change:
> The only one change is introducing a new patch[1/7] to remove the unnecessary
> macro FSL_DMA_LD_DEBUG, thus the total patches number is 8 now (was 7)
> v1 notes:
> Note that patch 2~6 had beed sent out for upstream before, but were together
> with other storage patches at that time, that was not easy for being reviewed
> and merged, so I send them separately this time.
> Hongbo Zhang (3):
> DMA: Freescale: use spin_lock_bh instead of spin_lock_irqsave
> DMA: Freescale: add suspend resume functions for DMA driver
> DMA: Freescale: change descriptor release process for supporting
> drivers/dma/fsldma.c | 297 ++++++++++++++++++++++++++++++++++++++------------
> drivers/dma/fsldma.h | 32 +++++-
> 2 files changed, 260 insertions(+), 69 deletions(-)
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
More information about the Linuxppc-dev