From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: gustavo.pimentel@synopsys.com, hongxing.zhu@nxp.com,
l.stach@pengutronix.de, linux-imx@nxp.com,
linux-pci@vger.kernel.org, lznuaa@gmail.com, vkoul@kernel.org,
lorenzo.pieralisi@arm.com, robh@kernel.org, kw@linux.com,
bhelgaas@google.com, shawnguo@kernel.org
Subject: Re: [PATCH v2 4/5] PCI: imx6: add PCIe embedded DMA support
Date: Wed, 9 Mar 2022 17:31:49 +0530 [thread overview]
Message-ID: <20220309120149.GB134091@thinkpad> (raw)
In-Reply-To: <20220303184635.2603-4-Frank.Li@nxp.com>
On Thu, Mar 03, 2022 at 12:46:34PM -0600, Frank Li wrote:
> Add support for the DMA controller in the DesignWare PCIe core
>
> The DMA can transfer data to any remote address location
> regardless PCI address space size.
>
> Prepare struct dw_edma_chip() and call dw_edma_probe()
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
>
> This patch depended on some ep enable patch for imx.
>
> Change from v1 to v2
> - rework commit message
> - align dw_edma_chip change
>
> drivers/pci/controller/dwc/pci-imx6.c | 51 +++++++++++++++++++++++++++
> 1 file changed, 51 insertions(+)
>
> diff --git a/drivers/pci/controller/dwc/pci-imx6.c b/drivers/pci/controller/dwc/pci-imx6.c
> index efa8b81711090..7dc55986c947d 100644
> --- a/drivers/pci/controller/dwc/pci-imx6.c
> +++ b/drivers/pci/controller/dwc/pci-imx6.c
> @@ -38,6 +38,7 @@
> #include "../../pci.h"
>
> #include "pcie-designware.h"
> +#include "linux/dma/edma.h"
>
> #define IMX8MQ_PCIE_LINK_CAP_REG_OFFSET 0x7c
> #define IMX8MQ_PCIE_LINK_CAP_L1EL_64US GENMASK(18, 17)
> @@ -164,6 +165,8 @@ struct imx6_pcie {
> const struct imx6_pcie_drvdata *drvdata;
> struct regulator *epdev_on;
> struct phy *phy;
> +
> + struct dw_edma_chip dma_chip;
> };
>
> /* Parameters for the waiting for PCIe PHY PLL to lock on i.MX7 */
> @@ -2031,6 +2034,51 @@ static const struct dw_pcie_ep_ops pcie_ep_ops = {
> .get_features = imx_pcie_ep_get_features,
> };
>
> +static int imx_dma_irq_vector(struct device *dev, unsigned int nr)
> +{
> + struct platform_device *pdev = to_platform_device(dev);
> +
> + return platform_get_irq_byname(pdev, "dma");
> +}
> +
> +static struct dw_edma_core_ops dma_ops = {
> + .irq_vector = imx_dma_irq_vector,
> +};
> +
> +static int imx_add_pcie_dma(struct imx6_pcie *imx6_pcie)
> +{
> + unsigned int pcie_dma_offset;
> + struct dw_pcie *pci = imx6_pcie->pci;
> + struct device *dev = pci->dev;
> + struct dw_edma_chip *dma = &imx6_pcie->dma_chip;
> + int i = 0;
Unused?
> + int sz = PAGE_SIZE;
> +
> + pcie_dma_offset = 0x970;
Can you get this offset from the devicetree node of ep?
> +
> + dma->dev = dev;
> +
> + dma->reg_base = pci->dbi_base + pcie_dma_offset;
> +
> + dma->ops = &dma_ops;
> + dma->nr_irqs = 1;
> +
> + dma->flags = DW_EDMA_CHIP_NO_MSI | DW_EDMA_CHIP_REG32BIT | DW_EDMA_CHIP_LOCAL_EP;
> +
> + dma->ll_wr_cnt = dma->ll_rd_cnt=1;
Is this a hard limitation of the eDMA implementation or because of difficulties
in requesting the correct channel from client driver?
If it's the latter, you could use my patch:
https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/commit/?h=tracking-qcomlt-sdx55-drivers&id=c77ad9d929372b1ff495709714b24486d266a810
> + dma->ll_region_wr[0].sz = sz;
> + dma->ll_region_wr[0].vaddr = dmam_alloc_coherent(dev, sz,
> + &dma->ll_region_wr[i].paddr,
> + GFP_KERNEL);
Allocation could fail. Please add error checking here and below.
Thanks,
Mani
> +
> + dma->ll_region_rd[0].sz = sz;
> + dma->ll_region_rd[0].vaddr = dmam_alloc_coherent(dev, sz,
> + &dma->ll_region_rd[i].paddr,
> + GFP_KERNEL);
> +
> + return dw_edma_probe(dma);
> +}
> +
> static int imx_add_pcie_ep(struct imx6_pcie *imx6_pcie,
> struct platform_device *pdev)
> {
> @@ -2694,6 +2742,9 @@ static int imx6_pcie_probe(struct platform_device *pdev)
> goto err_ret;
> }
>
> + if (imx_add_pcie_dma(imx6_pcie))
> + dev_info(dev, "pci edma probe failure\n");
> +
> return 0;
>
> err_ret:
> --
> 2.24.0.rc1
>
next prev parent reply other threads:[~2022-03-09 12:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 18:46 [PATCH v2 1/5] dmaengine: dw-edma: fix dw_edma_probe() can't be call globally Frank Li
2022-03-03 18:46 ` [PATCH v2 2/5] dmaengine: dw-edma-pcie: don't touch internal struct dw_edma Frank Li
2022-03-03 18:46 ` [PATCH v2 3/5] dmaengine: dw-edma: add flags at struct dw_edma_chip Frank Li
2022-03-04 16:19 ` Manivannan Sadhasivam
2022-03-04 17:16 ` Zhi Li
2022-03-07 13:59 ` Manivannan Sadhasivam
2022-03-04 21:31 ` Bjorn Helgaas
2022-03-03 18:46 ` [PATCH v2 4/5] PCI: imx6: add PCIe embedded DMA support Frank Li
2022-03-04 21:33 ` Bjorn Helgaas
2022-03-05 1:31 ` Zhi Li
2022-03-09 12:01 ` Manivannan Sadhasivam [this message]
2022-03-09 18:31 ` Zhi Li
2022-03-09 18:42 ` Manivannan Sadhasivam
2022-03-09 19:14 ` Zhi Li
2022-03-09 20:48 ` Zhi Li
2022-03-10 4:45 ` Manivannan Sadhasivam
2022-03-03 18:46 ` [PATCH v2 5/5] PCI: endpoint: functions/pci-epf-test: Support PCI controller DMA Frank Li
2022-03-10 22:07 ` [PATCH v2 1/5] dmaengine: dw-edma: fix dw_edma_probe() can't be call globally Zhi 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=20220309120149.GB134091@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=hongxing.zhu@nxp.com \
--cc=kw@linux.com \
--cc=l.stach@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lznuaa@gmail.com \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).