From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: linux-pci@vger.kernel.org
Cc: bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, gregkh@linuxfoundation.org,
Liviu.Dudau@arm.com, robh@kernel.org, catalin.marinas@arm.com,
arnd@arndb.de
Subject: [PATCH v3] PCI: of: Avoid pci_remap_iospace() when PCI_IOBASE not defined
Date: Wed, 22 Sep 2021 06:20:41 +0200 [thread overview]
Message-ID: <20210922042041.16326-1-sergio.paracuellos@gmail.com> (raw)
Request for I/O resources from device tree call 'pci_remap_iospace()' from
'devm_pci_remap_iospace()' which is also called from device tree function
'pci_parse_request_of_pci_ranges()'. If PCI_IOBASE is not defined and I/O
resources are requested the following warning appears:
WARNING: CPU: 2 PID: 1 at ../drivers/pci/pci.c:4066 pci_remap_iospace+0x3c/0x54
This architecture does not support memory mapped I/O
Since there are architectures (like MIPS ralink) that can request I/O
resources from device tree but don't have mappable I/O space and therefore
don't define PCI_IOBASE avoid calling devm_pci_remap_iospace() in that case.
Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
Hi all,
This pach was part of a three patch series [0] and [1] but the other two
patches have been already added through staging git tree. I would like also
this patch going through the staging-tree to have all the three patches merged
together in the same tree, but if it is not possible I can also live with
that :).
Changes in v3:
- Went back to the same approach that was done in v1 of the series [0].
- Adjust commit message and description as I was suggested to do by Bjorn.
v1 series:
- [0]: https://lore.kernel.org/linux-pci/20210807072409.9018-2-sergio.paracuellos@gmail.com/T/#meb2e6c283f6d391407cb0c1158feea71de59b87d
v2 series:
- [1]: https://lore.kernel.org/all/20210822161005.22467-1-sergio.paracuellos@gmail.com/
Thanks in advance for your time.
Best regards,
Sergio Paracuellos
drivers/pci/of.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/pci/of.c b/drivers/pci/of.c
index d84381ce82b5..7d7aab1d1d64 100644
--- a/drivers/pci/of.c
+++ b/drivers/pci/of.c
@@ -564,12 +564,14 @@ static int pci_parse_request_of_pci_ranges(struct device *dev,
switch (resource_type(res)) {
case IORESOURCE_IO:
+#ifdef PCI_IOBASE
err = devm_pci_remap_iospace(dev, res, iobase);
if (err) {
dev_warn(dev, "error %d: failed to map resource %pR\n",
err, res);
resource_list_destroy_entry(win);
}
+#endif
break;
case IORESOURCE_MEM:
res_valid |= !(res->flags & IORESOURCE_PREFETCH);
--
2.25.1
next reply other threads:[~2021-09-22 4:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 4:20 Sergio Paracuellos [this message]
2021-09-22 15:47 ` [PATCH v3] PCI: of: Avoid pci_remap_iospace() when PCI_IOBASE not defined Arnd Bergmann
2021-09-22 17:42 ` Sergio Paracuellos
2021-09-22 18:07 ` Arnd Bergmann
2021-09-22 18:40 ` Sergio Paracuellos
2021-09-22 19:57 ` Arnd Bergmann
2021-09-22 20:55 ` Sergio Paracuellos
2021-09-23 5:51 ` Arnd Bergmann
2021-09-23 6:36 ` Sergio Paracuellos
2021-09-23 9:07 ` Arnd Bergmann
2021-09-23 11:08 ` Sergio Paracuellos
2021-09-23 13:26 ` Arnd Bergmann
2021-09-23 14:55 ` Sergio Paracuellos
2021-09-23 17:55 ` Arnd Bergmann
2021-09-23 20:32 ` Sergio Paracuellos
2021-09-24 8:53 ` Arnd Bergmann
2021-09-24 10:15 ` Sergio Paracuellos
2021-09-24 11:39 ` Arnd Bergmann
2021-09-24 12:46 ` Sergio Paracuellos
2021-09-24 13:27 ` Arnd Bergmann
2021-09-24 16:45 ` Sergio Paracuellos
2021-09-24 16:47 ` Sergio Paracuellos
2021-09-24 17:04 ` Arnd Bergmann
2021-09-24 17:15 ` Sergio Paracuellos
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=20210922042041.16326-1-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).