linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: dmaengine fixes for v5.10-rc5
Date: Fri, 20 Nov 2020 20:35:12 +0530	[thread overview]
Message-ID: <20201120150512.GL2925@vkoul-mobl> (raw)

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

Hello Linus

Please consider pull to receive the dmaengine subsystem fixes for
v5.10-rc5

The includes a solitary core fixes and few driver fixes. All the patches
are in linux-next

The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:

  Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git tags/dmaengine-fix-5.10-rc5

for you to fetch changes up to 7e4be1290a38b3dd4a77cdf4565c9ffe7e620013:

  dmaengine: fix error codes in channel_register() (2020-11-18 17:51:51 +0530)

----------------------------------------------------------------
dmaengine fixes for v5.10-rc5

Core:
*) channel_register error handling

Driver fixes for:
*) idxd: wq config registers programming and mapping of portal size
*) ioatdma: unused fn removal
*) pl330: fix burst size
*) ti: pm fix on busy and -Wenum-conversion warns
*) xilinx: SG capability check, usage of xilinx_aximcdma_tx_segment,
readl_poll_timeout_atomic variant

----------------------------------------------------------------
Arnd Bergmann (1):
      dmaengine: ti: k3-udma: fix -Wenum-conversion warning

Dan Carpenter (1):
      dmaengine: fix error codes in channel_register()

Dave Jiang (2):
      dmaengine: idxd: fix wq config registers offset programming
      dmaengine: idxd: fix mapping of portal size

Lukas Bulwahn (1):
      dmaengine: ioatdma: remove unused function missed during dma_v2 removal

Marc Ferland (1):
      dmaengine: xilinx_dma: use readl_poll_timeout_atomic variant

Matthew Murrian (2):
      dmaengine: xilinx_dma: Fix usage of xilinx_aximcdma_tx_segment
      dmaengine: xilinx_dma: Fix SG capability check for MCDMA

Sugar Zhang (1):
      dmaengine: pl330: _prep_dma_memcpy: Fix wrong burst size

Tony Lindgren (1):
      dmaengine: ti: omap-dma: Block PM if SDMA is busy to fix audio

 drivers/dma/dmaengine.c          | 17 +++++++++--------
 drivers/dma/idxd/device.c        | 31 +++++++++++++++----------------
 drivers/dma/idxd/idxd.h          |  3 ++-
 drivers/dma/idxd/init.c          |  5 +++++
 drivers/dma/idxd/registers.h     | 25 +++++++++++++++++++++++--
 drivers/dma/idxd/submit.c        |  2 +-
 drivers/dma/ioat/dca.c           | 10 ----------
 drivers/dma/pl330.c              |  2 +-
 drivers/dma/ti/k3-udma-private.c |  2 +-
 drivers/dma/ti/omap-dma.c        | 37 ++++++++++++++++++++++++-------------
 drivers/dma/xilinx/xilinx_dma.c  | 40 ++++++++++++++++++++++++++++++----------
 11 files changed, 111 insertions(+), 63 deletions(-)

Thanks
-- 
~Vinod

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-11-20 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 15:05 Vinod Koul [this message]
2020-11-20 18:40 ` [GIT PULL]: dmaengine fixes for v5.10-rc5 pr-tracker-bot

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=20201120150512.GL2925@vkoul-mobl \
    --to=vkoul@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;
as well as URLs for NNTP newsgroup(s).