public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] slave dmaengine fixes for 4.2-rc5
Date: Sat, 1 Aug 2015 21:53:29 +0530	[thread overview]
Message-ID: <20150801162329.GL29916@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 2565 bytes --]

Hi Linus,

Here is the first fixes request for 4.2

  We had a regression due to reuse of descriptor so we have reverted that.
  Rest are driver fixes:
     at_hdmac and at_xdmac for residue, trannfer width, and channel config
     pl330 final fix for dma fails and overflow issue
     xgene resouce map fix
     mv_xor big endian op fix

So, please PULL for dmaengine updates for 4.2-rc5 from

  git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-4.2-rc5

for you to fetch changes up to 8c8fe97b2b8a216523e2faf1ccca66ddab634e3e:

  Revert "dmaengine: virt-dma: don't always free descriptor upon completion" (2015-07-31 20:33:43 +0530)

----------------------------------------------------------------
dmaengine fixes for 4.2-rc5

  We had a regression due to reuse of descriptor so we have reverted that.
  Rest are driver fixes
     at_hdmac and at_xdmac for residue, trannfer width, and channel config
     pl330 final fix for dma fails and overflow issue
     xgene resouce map fix
     mv_xor big endian op fix

----------------------------------------------------------------
Cyrille Pitchen (2):
      dmaengine: at_hdmac: fix residue computation
      dmaengine: at_xdmac: fix transfer data width in at_xdmac_prep_slave_sg()

Jun Nie (1):
      Revert "dmaengine: virt-dma: don't always free descriptor upon completion"

Krzysztof Kozlowski (2):
      dmaengine: pl330: Fix overflow when reporting residue in memcpy
      dmaengine: pl330: Really fix choppy sound because of wrong residue calculation

Ludovic Desroches (1):
      dmaengine: at_xdmac: fix bug about channel configuration

Rameshwar Prasad Sahu (1):
      dmaengine: xgene-dma: Fix the resource map to handle overlapping

Thomas Petazzoni (1):
      dmaengine: mv_xor: fix big endian operation in register mode

 .../devicetree/bindings/dma/apm-xgene-dma.txt      |   2 +-
 arch/arm64/boot/dts/apm/apm-storm.dtsi             |   2 +-
 drivers/dma/at_hdmac.c                             | 132 ++++++++++++++-------
 drivers/dma/at_hdmac_regs.h                        |   3 +-
 drivers/dma/at_xdmac.c                             |  26 ++--
 drivers/dma/mv_xor.c                               |   9 +-
 drivers/dma/pl330.c                                |   3 +-
 drivers/dma/virt-dma.c                             |  19 +--
 drivers/dma/virt-dma.h                             |  13 +-
 drivers/dma/xgene-dma.c                            |   3 +
 10 files changed, 121 insertions(+), 91 deletions(-)

-- 
~Vinod

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2015-08-01 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150801162329.GL29916@localhost \
    --to=vinod.koul@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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