From: Frank Li <Frank.li@nxp.com>
To: Devendra K Verma <devendra.verma@amd.com>
Cc: bhelgaas@google.com, mani@kernel.org, vkoul@kernel.org,
dmaengine@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, michal.simek@amd.com
Subject: Re: [PATCH v11 2/2] dmaengine: dw-edma: Add non-LL mode
Date: Fri, 6 Mar 2026 16:17:06 -0500 [thread overview]
Message-ID: <aatEUuynXVVYEhWy@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260306115228.3446528-3-devendra.verma@amd.com>
On Fri, Mar 06, 2026 at 05:22:28PM +0530, Devendra K Verma wrote:
...
> + /*
> + * When there is no valid LLP base address available then the
> + * default DMA ops will use the non-LL mode.
> + *
> + * Cases where LL mode is enabled and client wants to use the
> + * non-LL mode then also client can do so via providing the
> + * peripheral_config param.
> + */
> + cfg_non_ll = chan->dw->chip->cfg_non_ll;
> + if (config->peripheral_config) {
> + non_ll = *(int *)config->peripheral_config;
> +
> + if (cfg_non_ll && !non_ll) {
> + dev_err(dchan->device->dev, "invalid configuration\n");
> + return -EINVAL;
> + }
> + }
> +
> + if (cfg_non_ll || (!cfg_non_ll && non_ll))
> + chan->non_ll = true;
this logic have a little bit complex
if (cfg_non_ll)
chan->non_ll = true;
else
chan->non_ll = non_ll;
> + } else if (config->peripheral_config) {
> + dev_err(dchan->device->dev,
> + "peripheral config param applicable only for HDMA\n");
> + return -EINVAL;
> + }
>
...
>
> struct dw_edma_irq {
> diff --git a/drivers/dma/dw-edma/dw-edma-pcie.c b/drivers/dma/dw-edma/dw-edma-pcie.c
> index b8208186a250..f538d728609f 100644
> --- a/drivers/dma/dw-edma/dw-edma-pcie.c
> +++ b/drivers/dma/dw-edma/dw-edma-pcie.c
> @@ -295,6 +295,15 @@ static void dw_edma_pcie_get_xilinx_dma_data(struct pci_dev *pdev,
> pdata->devmem_phys_off = off;
> }
>
> +static u64 dw_edma_get_phys_addr(struct pci_dev *pdev,
> + struct dw_edma_pcie_data *pdata,
> + enum pci_barno bar)
> +{
> + if (pdev->vendor == PCI_VENDOR_ID_XILINX)
> + return pdata->devmem_phys_off;
> + return pci_bus_address(pdev, bar);
> +}
> +
Reduce each patches's changes, make each patch is straightforward
Create Prepare patch firstly, change pci_bus_address() to dw_edma_get_phys_addr()
just
dw_edma_get_phys_addr() {
{
return return pci_bus_address(pdev, bar);
}
So this patch just add
two lines here
if (pdev->vendor == PCI_VENDOR_ID_XILINX)
return pdata->devmem_phys_off;
others look good.
Frank
>
next prev parent reply other threads:[~2026-03-06 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 11:52 [PATCH v11 0/2] Add AMD MDB Endpoint and non-LL mode Support Devendra K Verma
2026-03-06 11:52 ` [PATCH v11 1/2] dmaengine: dw-edma: Add AMD MDB Endpoint Support Devendra K Verma
2026-03-06 20:59 ` Frank Li
2026-03-06 11:52 ` [PATCH v11 2/2] dmaengine: dw-edma: Add non-LL mode Devendra K Verma
2026-03-06 21:17 ` Frank Li [this message]
2026-03-09 11:18 ` Verma, Devendra
2026-03-09 15:40 ` Frank Li
2026-03-10 12:30 ` Verma, Devendra
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=aatEUuynXVVYEhWy@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--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 \
--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
all inboxes | Powered by JetHome®