Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Sumit Kumar <sumit.kumar@oss.qualcomm.com>
To: Manivannan Sadhasivam <mani@kernel.org>,
	Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: "Jingoo Han" <jingoohan1@gmail.com>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pci: designware: Set DMA_BYPASS bit in outbound IATU CTRL2 register
Date: Tue, 8 Sep 2026 11:49:17 +0530	[thread overview]
Message-ID: <43009f4c-55c8-4f82-9efe-b72747f68cc5@oss.qualcomm.com> (raw)
In-Reply-To: <ycyc7cm4y6s4nmez3aojdenqikh35eqvk2ady2azbiyghbbg4v@r3dzmymx2xuf>



On 9/2/2026 9:47 PM, Manivannan Sadhasivam wrote:
> On Wed, Sep 02, 2026 at 08:44:57PM +0530, Krishna Chaitanya Chundru wrote:
>>
>> On 9/2/2026 7:37 PM, Manivannan Sadhasivam wrote:
>>> On Wed, Aug 26, 2026 at 02:41:20PM +0530, Sumit Kumar wrote:
>>>> Outbound IATU apertures are configured with local device-side addresses.
>>>> When DMA engine transactions use destination addresses which fall within
>>>> an outbound IATU aperture range, they get unintentionally translated by
>>>> the IATU, causing the wrong address to be sent on the PCIe link.
>>>> This results in data corruption or IOMMU errors at the host if the
>>>> translated address is not mapped.
>>>>
>>> Why are you using the same device address in both DMA and iATU mapping? This
>>> sounds like a mapping problem that you should fix instead.
>> issue happens, when host address(DMA destination address) matches with the
>> internal iova address programmed in iATU src address.
>> As we can cannot address in both,  we need to program iATU in DMA bypass mode,
>> so DMA transcations will not go through iATU window.
>>
> This needs to be explained clearly in the commit message with an example
> matching the DWC terminologies such as 'Target Address Registers'.
>
> - Mani
>
updated in v2.
- Sumit

      reply	other threads:[~2026-09-08  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  9:11 [PATCH] pci: designware: Set DMA_BYPASS bit in outbound IATU CTRL2 register Sumit Kumar
2026-08-26  9:26 ` sashiko-bot
2026-09-02 14:07 ` Manivannan Sadhasivam
2026-09-02 15:14   ` Krishna Chaitanya Chundru
2026-09-02 16:17     ` Manivannan Sadhasivam
2026-09-08  6:19       ` Sumit Kumar [this message]

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=43009f4c-55c8-4f82-9efe-b72747f68cc5@oss.qualcomm.com \
    --to=sumit.kumar@oss.qualcomm.com \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=robh@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