From: Vinod Koul <vkoul@kernel.org>
To: Devendra K Verma <devendra.verma@amd.com>
Cc: bhelgaas@google.com, mani@kernel.org, dmaengine@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
michal.simek@amd.com
Subject: Re: [PATCH v13 0/2] Add AMD MDB Endpoint and non-LL mode Support
Date: Tue, 17 Mar 2026 16:32:58 +0530 [thread overview]
Message-ID: <abk04pkF4mOR0rKP@vaman> (raw)
In-Reply-To: <20260311111834.3750297-1-devendra.verma@amd.com>
On 11-03-26, 16:48, Devendra K Verma wrote:
> This series of patch support the following:
>
> - AMD MDB Endpoint Support, as part of this patch following are
> added:
> o AMD supported device ID and vendor ID (Xilinx)
> o AMD MDB specific driver data
> o AMD specific VSEC capabilities to retrieve the base of
> phys address of MDB side DDR
> o Logic to assign the offsets to LL and data blocks if
> more number of channels are enabled than configured
> in the given pci_data struct.
>
> - Addition of non-LL mode
> o The IP supported non-LL mode functions
> o Flexibility to choose non-LL mode via dma_slave_config
> param peripheral_config, by the client for all the vendors
> using HDMA IP.
> o Allow IP utilization if LL mode is not available
There is trailing whitespace in patch2 and even then it fails for me on
dmaengine/next. Please rebase and resend
--
~Vinod
next prev parent reply other threads:[~2026-03-17 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 11:18 [PATCH v13 0/2] Add AMD MDB Endpoint and non-LL mode Support Devendra K Verma
2026-03-11 11:18 ` [PATCH v13 1/2] dmaengine: dw-edma: Add AMD MDB Endpoint Support Devendra K Verma
2026-03-11 11:18 ` [PATCH v13 2/2] dmaengine: dw-edma: Add non-LL mode Devendra K Verma
2026-03-17 11:02 ` Vinod Koul [this message]
2026-03-17 12:24 ` [PATCH v13 0/2] Add AMD MDB Endpoint and non-LL mode Support Verma, Devendra
2026-03-18 7:03 ` Verma, Devendra
2026-03-18 11:27 ` Vinod Koul
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=abk04pkF4mOR0rKP@vaman \
--to=vkoul@kernel.org \
--cc=bhelgaas@google.com \
--cc=devendra.verma@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=michal.simek@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.