From: Frank Li <Frank.Li@nxp.com>
To: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Frank Li <Frank.Li@nxp.com>
Subject: [PATCH RFT 0/2] pci: clean up cpu_addr_fixup() for visconti
Date: Fri, 13 Jun 2025 17:33:28 -0400 [thread overview]
Message-ID: <20250613-tmpv-v1-0-4023aa386d17@nxp.com> (raw)
Since
7db02f725df44 PCI: dwc: Use devicetree 'reg[config]' to derive CPU -> ATU addr offset
dwc common code have handled address translate by bus fabric.
1. Correct dts
2. remove cpu_addr_fixup()
dts change need be merge firstly.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
Frank Li (2):
arm64: dts: toshiba: Update SoC and PCIe ranges to reflect hardware behavior
PCI: dwc: visconti: Remove cpu_addr_fix() after DTS fix ranges
arch/arm64/boot/dts/toshiba/tmpv7708.dtsi | 16 ++++++++++++----
drivers/pci/controller/dwc/pcie-visconti.c | 13 -------------
2 files changed, 12 insertions(+), 17 deletions(-)
---
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
change-id: 20250613-tmpv-f1cc6e463343
Best regards,
---
Frank Li <Frank.Li@nxp.com>
next reply other threads:[~2025-06-13 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 21:33 Frank Li [this message]
2025-06-13 21:33 ` [PATCH RFT 1/2] arm64: dts: toshiba: Update SoC and PCIe ranges to reflect hardware behavior Frank Li
2025-07-28 5:38 ` nobuhiro1.iwamatsu
2025-07-28 14:26 ` Frank Li
2025-07-30 0:13 ` nobuhiro1.iwamatsu
2025-06-13 21:33 ` [PATCH RFT 2/2] PCI: dwc: visconti: Remove cpu_addr_fix() after DTS fix ranges Frank 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=20250613-tmpv-v1-0-4023aa386d17@nxp.com \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--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
all inboxes | Powered by JetHome®