linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Serge Semin <Sergey.Semin@baikalelectronics.ru>
To: "Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
	"Vinod Koul" <vkoul@kernel.org>, "Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Cai Huoqing" <cai.huoqing@linux.dev>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Jingoo Han" <jingoohan1@gmail.com>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>
Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
	Serge Semin <fancer.lancer@gmail.com>,
	Alexey Malahov <Alexey.Malahov@baikalelectronics.ru>,
	Pavel Parkhomenko <Pavel.Parkhomenko@baikalelectronics.ru>,
	caihuoqing <caihuoqing@baidu.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	<linux-pci@vger.kernel.org>, <dmaengine@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH v8 24/26] PCI: dwc: Set coherent DMA-mask on MSI-address allocation
Date: Mon, 19 Dec 2022 17:46:55 +0300	[thread overview]
Message-ID: <20221219144658.26620-25-Sergey.Semin@baikalelectronics.ru> (raw)
In-Reply-To: <20221219144658.26620-1-Sergey.Semin@baikalelectronics.ru>

The MSI target address requires to be reserved within the lowest 4GB
memory in order to support the PCIe peripherals with no 64-bit MSI TLPs
support. Since the allocation is done from the DMA-coherent memory let's
modify the allocation procedure to setting the coherent DMA-mask only and
avoiding the streaming DMA-mask modification. Thus at least the streaming
DMA operations would work with no artificial limitations. It will be
specifically useful for the eDMA-capable controllers so the corresponding
DMA-engine clients would map the DMA buffers with no need in the SWIOTLB
intervention for the buffers allocated above the 4GB memory region.

While at it let's add a brief comment about the reason of having the MSI
target address allocated from the DMA-coherent memory limited with the 4GB
upper bound.

Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>

---

Changelog v8:
- This is a new patch added on v8 stage of the series.
  (@Robin, @Christoph)
---
 drivers/pci/controller/dwc/pcie-designware-host.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
index 3ab6ae3712c4..e10608af39b4 100644
--- a/drivers/pci/controller/dwc/pcie-designware-host.c
+++ b/drivers/pci/controller/dwc/pcie-designware-host.c
@@ -366,7 +366,16 @@ static int dw_pcie_msi_host_init(struct dw_pcie_rp *pp)
 						    dw_chained_msi_isr, pp);
 	}
 
-	ret = dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32));
+	/*
+	 * Even though the iMSI-RX Module supports 64-bit addresses some
+	 * peripheral PCIe devices may lack the 64-bit messages support. In
+	 * order not to miss MSI TLPs from those devices the MSI target address
+	 * has to be reserved within the lowest 4GB.
+	 * Note until there is a better alternative found the reservation is
+	 * done by allocating from the artificially limited DMA-coherent
+	 * memory.
+	 */
+	ret = dma_set_coherent_mask(dev, DMA_BIT_MASK(32));
 	if (ret)
 		dev_warn(dev, "Failed to set DMA mask to 32-bit. Devices with only 32-bit MSI support may not work properly\n");
 
-- 
2.38.1



  parent reply	other threads:[~2022-12-19 14:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 14:46 [PATCH v8 00/26] dmaengine: dw-edma: Add RP/EP local DMA controllers support Serge Semin
2022-12-19 14:46 ` [PATCH v8 01/26] dmaengine: Fix dma_slave_config.dst_addr description Serge Semin
2022-12-19 14:46 ` [PATCH v8 02/26] dmaengine: dw-edma: Release requested IRQs on failure Serge Semin
2022-12-19 14:46 ` [PATCH v8 03/26] dmaengine: dw-edma: Convert ll/dt phys-address to PCIe bus/DMA address Serge Semin
2022-12-19 14:46 ` [PATCH v8 04/26] dmaengine: dw-edma: Fix missing src/dst address of the interleaved xfers Serge Semin
2022-12-19 14:46 ` [PATCH v8 05/26] dmaengine: dw-edma: Don't permit non-inc " Serge Semin
2022-12-19 14:46 ` [PATCH v8 06/26] dmaengine: dw-edma: Fix invalid interleaved xfers semantics Serge Semin
2022-12-19 14:46 ` [PATCH v8 07/26] dmaengine: dw-edma: Add CPU to PCIe bus address translation Serge Semin
2022-12-19 14:46 ` [PATCH v8 08/26] dmaengine: dw-edma: Add PCIe bus address getter to the remote EP glue-driver Serge Semin
2022-12-19 14:46 ` [PATCH v8 09/26] dmaengine: dw-edma: Drop chancnt initialization Serge Semin
2022-12-19 14:46 ` [PATCH v8 10/26] dmaengine: dw-edma: Fix DebugFS reg entry type Serge Semin
2022-12-19 14:46 ` [PATCH v8 11/26] dmaengine: dw-edma: Stop checking debugfs_create_*() return value Serge Semin
2022-12-19 14:46 ` [PATCH v8 12/26] dmaengine: dw-edma: Add dw_edma prefix to the DebugFS nodes descriptor Serge Semin
2022-12-19 14:46 ` [PATCH v8 13/26] dmaengine: dw-edma: Convert DebugFS descs to being kz-allocated Serge Semin
2022-12-19 14:46 ` [PATCH v8 14/26] dmaengine: dw-edma: Rename DebugFS dentry variables to 'dent' Serge Semin
2022-12-19 14:46 ` [PATCH v8 15/26] dmaengine: dw-edma: Simplify the DebugFS context CSRs init procedure Serge Semin
2022-12-19 14:46 ` [PATCH v8 16/26] dmaengine: dw-edma: Move eDMA data pointer to DebugFS node descriptor Serge Semin
2022-12-19 14:46 ` [PATCH v8 17/26] dmaengine: dw-edma: Join Write/Read channels into a single device Serge Semin
2022-12-19 14:46 ` [PATCH v8 18/26] dmaengine: dw-edma: Use DMA-engine device DebugFS subdirectory Serge Semin
2022-12-19 14:46 ` [PATCH v8 19/26] dmaengine: dw-edma: Use non-atomic io-64 methods Serge Semin
2022-12-19 14:46 ` [PATCH v8 20/26] dmaengine: dw-edma: Drop DT-region allocation Serge Semin
2022-12-19 14:46 ` [PATCH v8 21/26] dmaengine: dw-edma: Replace chip ID number with device name Serge Semin
2022-12-19 14:46 ` [PATCH v8 22/26] dmaengine: dw-edma: Skip cleanup procedure if no private data found Serge Semin
2022-12-19 14:46 ` [PATCH v8 23/26] dmaengine: dw-edma: Relax driver config settings Serge Semin
2022-12-19 14:46 ` Serge Semin [this message]
2023-01-11 13:39   ` [PATCH v8 24/26] PCI: dwc: Set coherent DMA-mask on MSI-address allocation Robin Murphy
2023-01-12 18:46     ` Serge Semin
2022-12-19 14:46 ` [PATCH v8 25/26] PCI: bt1: Set 64-bit DMA-mask Serge Semin
2022-12-19 14:46 ` [PATCH v8 26/26] PCI: dwc: Add DW eDMA engine support Serge Semin

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=20221219144658.26620-25-Sergey.Semin@baikalelectronics.ru \
    --to=sergey.semin@baikalelectronics.ru \
    --cc=Alexey.Malahov@baikalelectronics.ru \
    --cc=Frank.Li@nxp.com \
    --cc=Pavel.Parkhomenko@baikalelectronics.ru \
    --cc=bhelgaas@google.com \
    --cc=cai.huoqing@linux.dev \
    --cc=caihuoqing@baidu.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jingoohan1@gmail.com \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=vkoul@kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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 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).