From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-pci@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-mips@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] MIPS: Malta: Use pcibios_align_resource() to block io range
Date: Tue, 21 Oct 2025 15:51:09 +0300 (EEST) [thread overview]
Message-ID: <9ff182b0-076b-78fd-adec-99ae7ea5341f@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2510210145260.8377@angie.orcam.me.uk>
On Tue, 21 Oct 2025, Maciej W. Rozycki wrote:
> On Mon, 20 Oct 2025, Bjorn Helgaas wrote:
>
> > > Since ae81aad5c2e1 ("MIPS: PCI: Use pci_enable_resources()") came
> > > through the PCI tree, I'd be happy to merge this as well, given your
> > > ack, Thomas. It would be ideal to have a tested-by from Guenter.
> > >
> > > I provisionally put it on pci/for-linus to facilitate testing. If it
> > > doesn't solve the problem or you'd rather take it, Thomas, I'll be
> > > glad to drop it.
> >
> > Added:
> >
> > Tested-by: Guenter Roeck <linux@roeck-us.net>
> > Tested-by: Maciej W. Rozycki <macro@orcam.me.uk>
> > Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> >
> > and dropped the Fixes: aa0980b80908 ("Fixes for system controllers for
> > Atlas/Malta core cards.")
> >
> > If the missing resource reservations (dma1, tiger, dma page reg)
> > mentioned by Maciej are an issue or can be fixed up, let me know and
> > we can amend this.
>
> NB this comes from `plat_mem_setup' in arch/mips/mti-malta/malta-setup.c
> iterating over `standard_io_resources'. ISTR now this being my original
> reason to come up with the approach taken with commit aa0980b80908 rather
> than using PCIBIOS_MIN_IO. Since the ranges are now owned by the PCI host
> bridge, calls to `request_resource' referring `ioport_resource' fail.
So this platform would actually need multiple root bus IO resources to
cover PIIX4 range without capturing non-PCI ranges?
> I'm not sure offhand how to get a hold on the right handle under the new
> arrangement in this platform code, but clearly it must be doable as x86
> gets it right (and conversely Alpha gets it totally wrong).
>
> Also I think we should reserve the PCI port I/O window in the MMIO space
> as well; something that I pondered back those 20 years ago already. For
> the system I've used here that'd show up as:
>
> 10000000-1affffff : MSC PCI MEM
> 10000000-100fffff : 0000:00:0b.0
> [...]
> 10142080-1014209f : 0000:00:0b.0
> 1b000000-1bffffff : MSC PCI I/O
> 1e000000-1e3fffff : 1e000000.flash flash@1e000000
>
> Most non-x86 PCI host bridges have one, but I haven't come across a Linux
> platform that would report it.
>
> Maciej
>
--
i.
next prev parent reply other threads:[~2025-10-21 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 11:09 [PATCH v2 1/1] MIPS: Malta: Use pcibios_align_resource() to block io range Ilpo Järvinen
2025-10-17 22:12 ` Bjorn Helgaas
2025-10-18 0:33 ` Guenter Roeck
2025-10-20 22:37 ` Bjorn Helgaas
2025-10-21 12:15 ` Maciej W. Rozycki
2025-10-21 12:51 ` Ilpo Järvinen [this message]
2025-10-21 14:41 ` Maciej W. Rozycki
2025-10-18 12:35 ` Guenter Roeck
2025-10-18 21:38 ` Maciej W. Rozycki
2025-10-20 14:12 ` Thomas Bogendoerfer
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=9ff182b0-076b-78fd-adec-99ae7ea5341f@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=macro@orcam.me.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox