From: Devendra K Verma <devverma@amd.com>
To: <mani@kernel.org>, <vkoul@kernel.org>, <frank.li@kernel.org>,
<den@valinux.co.jp>
Cc: <dmaengine@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <michal.simek@amd.com>,
<devverma@amd.com>
Subject: [PATCH v3 0/2] CPM6 Channel Separation Support
Date: Mon, 10 Aug 2026 15:40:00 +0530 [thread overview]
Message-ID: <20260810101002.1726131-1-devverma@amd.com> (raw)
'Designware Cores PCI Express DM Controller - Reference
Manual', section 3.2.34.3, VSEC for DEVICE INFORMATION supports
the channel separation mechanisms. Basically, the HDMA IP allows
the user to configure the separation between DMA channel
registers and retrieve it via the VSEC capability mentioned
above.
In order to use the VSEC functionality following changes have
been made:
o Utilize the existing VSEC implementation to retrieve
the channel separation and translate it to correct size.
o Modify the structs and functions to calculate correct
DMA channel register base using the channel, direction
and channel separation selected.
Devendra K Verma (2):
dmaengine: dw-edma: Enable Chan Separation via VSEC
dmaengine: dw-edma: Add changes to support Channel Separation
drivers/dma/dw-edma/dw-edma-pcie.c | 24 +++++++++++++++++---
drivers/dma/dw-edma/dw-hdma-v0-core.c | 23 +++++++++++--------
drivers/dma/dw-edma/dw-hdma-v0-debugfs.c | 17 +++++---------
drivers/dma/dw-edma/dw-hdma-v0-regs.h | 10 --------
drivers/pci/controller/dwc/pcie-designware.c | 1 +
include/linux/dma/edma.h | 1 +
6 files changed, 43 insertions(+), 33 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-10 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 10:10 Devendra K Verma [this message]
2026-08-10 10:10 ` [PATCH v3 1/2] dmaengine: dw-edma: Enable Chan Separation via VSEC Devendra K Verma
2026-08-10 17:14 ` Frank Li
2026-08-10 10:10 ` [PATCH v3 2/2] dmaengine: dw-edma: Add changes to support Channel Separation Devendra K Verma
2026-08-10 17:18 ` Frank Li
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=20260810101002.1726131-1-devverma@amd.com \
--to=devverma@amd.com \
--cc=den@valinux.co.jp \
--cc=dmaengine@vger.kernel.org \
--cc=frank.li@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=michal.simek@amd.com \
--cc=vkoul@kernel.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