The Linux Kernel Mailing List
 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 v6.13
Date: Thu, 26 Dec 2024 19:16:41 +0530	[thread overview]
Message-ID: <Z21eQafIgv+NfAVU@vaman> (raw)

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

Hello Linus,

Here is the last request for this year for dmaengine fixes.
Bunch of minor driver fixes for drivers in this cycle.


The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

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

for you to fetch changes up to ebc008699fd95701c9af5ebaeb0793eef81a71d5:

  dmaengine: tegra: Return correct DMA status when paused (2024-12-24 15:49:30 +0530)

----------------------------------------------------------------
dmaengine fixes for v6.13

Driver fixes for:
 - Kernel doc warning documentation fixes
 - apple driver fix for register access
 - amd driver dropping private dma_ops
 - freescale cleanup path fix
 - refcount fix for mv_xor driver
 - null pointer deref fix for at_xdmac driver
 - GENMASK to GENMASK_ULL fix for loongson2 apb driver
 - Tegra driver fix for correcting dma status

----------------------------------------------------------------
Akhil R (1):
      dmaengine: tegra: Return correct DMA status when paused

Andy Shevchenko (1):
      dmaengine: dw: Select only supported masters for ACPI devices

Binbin Zhou (1):
      dmaengine: loongson2-apb: Change GENMASK to GENMASK_ULL

Chen Ridong (1):
      dmaengine: at_xdmac: avoid null_prt_deref in at_xdmac_prep_dma_memset

Javier Carrasco (1):
      dmaengine: mv_xor: fix child node refcount handling in early exit

Joe Hattori (1):
      dmaengine: fsl-edma: implement the cleanup path of fsl_edma3_attach_pd()

Lizhi Hou (1):
      dmaengine: amd: qdma: Remove using the private get and set dma_ops APIs

Randy Dunlap (1):
      linux/dmaengine.h: fix a few kernel-doc warnings

Sasha Finkelstein (1):
      dmaengine: apple-admac: Avoid accessing registers in probe

 drivers/dma/amd/qdma/qdma.c            | 28 ++++++++++-------------
 drivers/dma/apple-admac.c              |  7 ++----
 drivers/dma/at_xdmac.c                 |  2 ++
 drivers/dma/dw/acpi.c                  |  6 +++--
 drivers/dma/dw/internal.h              |  8 +++++++
 drivers/dma/dw/pci.c                   |  4 ++--
 drivers/dma/fsl-edma-common.h          |  1 +
 drivers/dma/fsl-edma-main.c            | 41 +++++++++++++++++++++++++++++-----
 drivers/dma/loongson2-apb-dma.c        |  2 +-
 drivers/dma/mv_xor.c                   |  2 ++
 drivers/dma/tegra186-gpc-dma.c         | 10 +++++++++
 include/linux/dmaengine.h              | 13 ++++++++---
 include/linux/platform_data/amd_qdma.h |  2 ++
 13 files changed, 92 insertions(+), 34 deletions(-)

-- 
~Vinod

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

             reply	other threads:[~2024-12-26 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 13:46 Vinod Koul [this message]
2024-12-26 21:24 ` [GIT PULL]: Dmaengine fixes for v6.13 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=Z21eQafIgv+NfAVU@vaman \
    --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