From: Bjorn Helgaas <helgaas@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: "Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Richard Zhu" <hongxing.zhu@nxp.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
imx@lists.linux.dev, "Niklas Cassel" <cassel@kernel.org>
Subject: Re: [PATCH v10 08/10] PCI: dwc: Print warning message when cpu_addr_fixup() exists
Date: Wed, 12 Mar 2025 17:04:24 -0500 [thread overview]
Message-ID: <20250312220424.GA711004@bhelgaas> (raw)
In-Reply-To: <20250310-pci_fixup_addr-v10-8-409dafc950d1@nxp.com>
On Mon, Mar 10, 2025 at 04:16:46PM -0400, Frank Li wrote:
> If the parent 'ranges' property in DT correctly describes the address
> translation, the cpu_addr_fixup() callback is not needed. Print a warning
> message to inform users to correct their DT files.
> +++ b/drivers/pci/controller/dwc/pcie-designware.c
> @@ -1125,6 +1125,8 @@ int dw_pcie_init_parent_bus_offset(struct dw_pcie *pci, const char *reg_name,
>
> fixup = pci->ops->cpu_addr_fixup;
> if (fixup) {
> + dev_warn_once(pci->dev, "cpu_addr_fixup() usage detected. Please fix DT!\n");
I don't think we need this. The mere presence of .cpu_addr_fixup()
doesn't tell us the DT is broken. When we have .cpu_addr_fixup(), the
DT is only broken if DT tells us something different than
.cpu_addr_fixup() tells us. And we already warn about that in the
"reg_addr != fixup_addr" case.
> +
> fixup_addr = fixup(pci, cpu_phy_addr);
> if (reg_addr == fixup_addr) {
> dev_info(dev, "%#010llx %s reg[%d] == %#010llx; %ps is redundant\n",
This message is really just a hint that DT is fine and
.cpu_addr_fixup() is redundant but harmless. If you want a dev_warn()
here to encourage people to remove .cpu_addr_fixup(), I'm fine with
that.
Seems like "dev_warn()" would be enough, probably no need for
"dev_warn_once()" since we should only run this once per controller
anyway, so I don't think we'll get spammed with messages.
next prev parent reply other threads:[~2025-03-12 22:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 20:16 [PATCH v10 00/10] PCI: Use device bus range info to cleanup RC Host/EP pci_fixup_addr() Frank Li
2025-03-10 20:16 ` [PATCH v10 01/10] PCI: dwc: Use resource start as iomap() input in dw_pcie_pme_turn_off() Frank Li
2025-03-10 20:16 ` [PATCH v10 02/10] PCI: dwc: Rename cpu_addr to parent_bus_addr for ATU configuration Frank Li
2025-03-10 20:16 ` [PATCH v10 03/10] PCI: dwc: Move cfg0 setup to dw_pcie_cfg0_setup() Frank Li
2025-03-10 20:16 ` [PATCH v10 04/10] PCI: dwc: Add helper dw_pcie_init_parent_bus_offset() Frank Li
2025-03-12 22:16 ` Bjorn Helgaas
2025-03-10 20:16 ` [PATCH v10 05/10] PCI: dwc: Use devicetree 'ranges' property to get rid of cpu_addr_fixup() callback Frank Li
2025-03-12 21:37 ` Bjorn Helgaas
2025-03-13 14:17 ` Frank Li
2025-03-10 20:16 ` [PATCH v10 06/10] PCI: dwc: ep: Add parent_bus_addr for outbound window Frank Li
2025-03-10 20:16 ` [PATCH v10 07/10] PCI: dwc: Use parent_bus_offset Frank Li
2025-03-10 20:16 ` [PATCH v10 08/10] PCI: dwc: Print warning message when cpu_addr_fixup() exists Frank Li
2025-03-12 22:04 ` Bjorn Helgaas [this message]
2025-03-13 14:32 ` Frank Li
2025-03-10 20:16 ` [PATCH v10 09/10] PCI: dwc: ep: Ensure proper iteration over outbound map windows Frank Li
2025-03-12 21:47 ` Bjorn Helgaas
2025-03-13 14:27 ` Frank Li
2025-03-10 20:16 ` [PATCH v10 10/10] PCI: imx6: Remove cpu_addr_fixup() 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=20250312220424.GA711004@bhelgaas \
--to=helgaas@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=imx@lists.linux.dev \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kw@linux.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@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).