All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Xincheng Zhang <zhangxincheng@ultrarisc.com>
Cc: jingoohan1@gmail.com, mani@kernel.org, lpieralisi@kernel.org,
	kwilczynski@kernel.org, robh@kernel.org, bhelgaas@google.com,
	wangjia@ultrarisc.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, Frank Li <Frank.Li@kernel.org>
Subject: Re: [PATCH 1/2] PCI: dwc: Allow drivers to skip MEM outbound iATU setup
Date: Thu, 3 Sep 2026 17:30:18 +0200	[thread overview]
Message-ID: <apmSiooxKzb9l-TB@ryzen> (raw)
In-Reply-To: <apmPeZEdanf80HVB@ryzen>

On Thu, Sep 03, 2026 at 05:17:13PM +0200, Niklas Cassel wrote:
> 
> To consider allowing this, at the bare minimum you would have to:
> 
> if pp->bypass_ob_mem_iatu is set:
> 
> 1) Verify that the glue driver has no .cpu_addr_fixup callback defined.

Looking at dw_pcie_parent_bus_offset(), I can see that it already computes
pci->parent_bus_offset correctly, regardless of pci->ops->cpu_addr_fixup and
pci->use_parent_dt_ranges, so atu.parent_bus_addr will be set correctly.

Thus, you can ignore 1).

But 2) would still be very much needed.


Kind regards,
Niklas

  reply	other threads:[~2026-09-03 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  5:54 [PATCH 0/2] PCI: dwc: Support large BARs on UltraRISC DP1000 Xincheng Zhang
2026-08-27  5:54 ` [PATCH 1/2] PCI: dwc: Allow drivers to skip MEM outbound iATU setup Xincheng Zhang
2026-08-27  5:59   ` sashiko-bot
2026-09-02 14:18   ` Manivannan Sadhasivam
2026-09-03  3:00     ` Xincheng Zhang
2026-09-03 15:17   ` Niklas Cassel
2026-09-03 15:30     ` Niklas Cassel [this message]
2026-09-04  1:51       ` Xincheng Zhang
2026-09-04  5:37         ` Niklas Cassel
2026-08-27  5:54 ` [PATCH 2/2] PCI: ultrarisc: Skip MEM outbound iATU setup on DP1000 Xincheng Zhang
2026-08-27  6:08   ` sashiko-bot

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=apmSiooxKzb9l-TB@ryzen \
    --to=cassel@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.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 \
    --cc=wangjia@ultrarisc.com \
    --cc=zhangxincheng@ultrarisc.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.