From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: tsbogend@alpha.franken.de
Cc: bhelgaas@google.com, matthias.bgg@gmail.com,
gregkh@linuxfoundation.org, linux-mips@vger.kernel.org,
linux-pci@vger.kernel.org, linux-staging@lists.linux.dev,
neil@brown.name, linux-kernel@vger.kernel.org
Subject: [PATCH v2 3/3] staging: mt7621-pci: set end limit for 'ioport_resource'
Date: Sun, 22 Aug 2021 18:10:05 +0200 [thread overview]
Message-ID: <20210822161005.22467-4-sergio.paracuellos@gmail.com> (raw)
In-Reply-To: <20210822161005.22467-1-sergio.paracuellos@gmail.com>
We have increase IO_SPACE_LIMIT for ralink platform to get PCI IO resources
properly handled using PCI core APIs. To align those changes with driver
code we have to set 'ioport_resource' end limit to IO_SPACE_LIMIT to avoid
errors.
Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
drivers/staging/mt7621-pci/pci-mt7621.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/mt7621-pci/pci-mt7621.c b/drivers/staging/mt7621-pci/pci-mt7621.c
index 691030e1a5ed..6301397c3987 100644
--- a/drivers/staging/mt7621-pci/pci-mt7621.c
+++ b/drivers/staging/mt7621-pci/pci-mt7621.c
@@ -522,6 +522,8 @@ static int mt7621_pci_probe(struct platform_device *pdev)
if (!dev->of_node)
return -ENODEV;
+ ioport_resource.end = IO_SPACE_LIMIT;
+
bridge = devm_pci_alloc_host_bridge(dev, sizeof(*pcie));
if (!bridge)
return -ENOMEM;
--
2.25.1
next prev parent reply other threads:[~2021-08-22 16:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 16:10 [PATCH v2 0/3] MIPS: ralink: properly handle pci IO resources Sergio Paracuellos
2021-08-22 16:10 ` [PATCH v2 1/3] MIPS: ralink: don't define PC_IOBASE but increase IO_SPACE_LIMIT Sergio Paracuellos
2021-09-02 11:08 ` Thomas Bogendoerfer
2021-08-22 16:10 ` [PATCH v2 2/3] PCI: fix 'pci_remap_iospace' for architectures with PCI_IOBASE not defined Sergio Paracuellos
2021-09-15 10:52 ` Sergio Paracuellos
2021-09-15 10:52 ` Sergio Paracuellos
2021-09-21 17:49 ` Bjorn Helgaas
2021-09-21 18:36 ` Sergio Paracuellos
2021-09-21 18:36 ` Sergio Paracuellos
2021-09-21 19:38 ` Bjorn Helgaas
2021-09-22 4:28 ` Sergio Paracuellos
2021-09-22 4:28 ` Sergio Paracuellos
2021-08-22 16:10 ` Sergio Paracuellos [this message]
2021-08-27 9:01 ` [PATCH v2 3/3] staging: mt7621-pci: set end limit for 'ioport_resource' Greg KH
2021-08-29 15:14 ` Sergio Paracuellos
2021-08-29 15:14 ` Sergio Paracuellos
2021-09-02 9:15 ` Greg KH
2021-09-02 10:15 ` Sergio Paracuellos
2021-09-02 10:15 ` Sergio Paracuellos
2021-09-02 11:08 ` Thomas Bogendoerfer
2021-09-02 11:19 ` Sergio Paracuellos
2021-09-02 11:19 ` Sergio Paracuellos
2021-09-21 15:28 ` Greg KH
2021-09-21 17:02 ` Sergio Paracuellos
2021-09-21 17:02 ` Sergio Paracuellos
2021-09-21 17:08 ` Greg KH
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=20210822161005.22467-4-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=neil@brown.name \
--cc=tsbogend@alpha.franken.de \
/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.