From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] MIPS: Malta: Fix PCI southbridge legacy resource reservations
Date: Tue, 21 Oct 2025 21:45:16 +0200 [thread overview]
Message-ID: <aPfizMmOQEl0_DaG@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2510212001250.8377@angie.orcam.me.uk>
On Tue, Oct 21, 2025 at 08:38:29PM +0100, Maciej W. Rozycki wrote:
> Covering the PCI southbridge legacy port I/O range with a northbridge
> resource reservation prevents MIPS Malta platform code from claiming its
> standard legacy resources. This is because request_resource() calls
> cause a clash with the previous reservation and consequently fail.
>
> Change to using insert_resource() so as to prevent the clash, switching
> the legacy reservations from:
>
> 00000000-00ffffff : MSC PCI I/O
> 00000020-00000021 : pic1
> 00000070-00000077 : rtc0
> 000000a0-000000a1 : pic2
> [...]
>
> to:
>
> 00000000-00ffffff : MSC PCI I/O
> 00000000-0000001f : dma1
> 00000020-00000021 : pic1
> 00000040-0000005f : timer
> 00000060-0000006f : keyboard
> 00000070-00000077 : rtc0
> 00000080-0000008f : dma page reg
> 000000a0-000000a1 : pic2
> 000000c0-000000df : dma2
> [...]
>
> Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> Fixes: ae81aad5c2e1 ("MIPS: PCI: Use pci_enable_resources()")
> Cc: stable@vger.kernel.org # v6.18+
> ---
> arch/mips/mti-malta/malta-setup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> linux-mips-malta-setup-insert-resource.diff
> Index: linux-macro/arch/mips/mti-malta/malta-setup.c
> ===================================================================
> --- linux-macro.orig/arch/mips/mti-malta/malta-setup.c
> +++ linux-macro/arch/mips/mti-malta/malta-setup.c
> @@ -213,7 +213,7 @@ void __init plat_mem_setup(void)
>
> /* Request I/O space for devices used on the Malta board. */
> for (i = 0; i < ARRAY_SIZE(standard_io_resources); i++)
> - request_resource(&ioport_resource, standard_io_resources+i);
> + insert_resource(&ioport_resource, standard_io_resources + i);
>
> /*
> * Enable DMA channel 4 (cascade channel) in the PIIX4 south bridge.
Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2025-10-21 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 19:38 [PATCH 0/2] MIPS: Malta: Fix PCI southbridge legacy resource clashes Maciej W. Rozycki
2025-10-21 19:38 ` [PATCH 1/2] MIPS: Malta: Fix keyboard resource preventing i8042 driver from registering Maciej W. Rozycki
2025-10-21 19:45 ` Thomas Bogendoerfer
2025-10-21 19:38 ` [PATCH 2/2] MIPS: Malta: Fix PCI southbridge legacy resource reservations Maciej W. Rozycki
2025-10-21 19:45 ` Thomas Bogendoerfer [this message]
2025-10-22 11:42 ` Jonas Gorski
2025-10-22 12:48 ` Maciej W. Rozycki
2025-10-21 20:59 ` [PATCH 0/2] MIPS: Malta: Fix PCI southbridge legacy resource clashes Bjorn Helgaas
2025-10-22 11:08 ` Ilpo Järvinen
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=aPfizMmOQEl0_DaG@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
/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).