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 1/2] MIPS: Malta: Fix keyboard resource preventing i8042 driver from registering
Date: Tue, 21 Oct 2025 21:45:03 +0200 [thread overview]
Message-ID: <aPfivybVYb-1_tlk@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2510211919240.8377@angie.orcam.me.uk>
On Tue, Oct 21, 2025 at 08:38:22PM +0100, Maciej W. Rozycki wrote:
> MIPS Malta platform code registers the PCI southbridge legacy port I/O
> PS/2 keyboard range as a standard resource marked as busy. It prevents
> the i8042 driver from registering as it fails to claim the resource in
> a call to i8042_platform_init(). Consequently PS/2 keyboard and mouse
> devices cannot be used with this platform.
>
> Fix the issue by removing the busy marker from the standard reservation,
> making the driver register successfully:
>
> serio: i8042 KBD port at 0x60,0x64 irq 1
> serio: i8042 AUX port at 0x60,0x64 irq 12
>
> and the resource show up as expected among the legacy devices:
>
> 00000000-00ffffff : MSC PCI I/O
> 00000000-0000001f : dma1
> 00000020-00000021 : pic1
> 00000040-0000005f : timer
> 00000060-0000006f : keyboard
> 00000060-0000006f : i8042
> 00000070-00000077 : rtc0
> 00000080-0000008f : dma page reg
> 000000a0-000000a1 : pic2
> 000000c0-000000df : dma2
> [...]
>
> If the i8042 driver has not been configured, then the standard resource
> will remain there preventing any conflicting dynamic assignment of this
> PCI port I/O address range.
>
> Signed-off-by: Maciej W. Rozycki <macro@orcam.me.uk>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Cc: stable@vger.kernel.org
> ---
> arch/mips/mti-malta/malta-setup.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> linux-mips-malta-setup-resource-keyboard.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
> @@ -47,7 +47,7 @@ static struct resource standard_io_resou
> .name = "keyboard",
> .start = 0x60,
> .end = 0x6f,
> - .flags = IORESOURCE_IO | IORESOURCE_BUSY
> + .flags = IORESOURCE_IO
> },
> {
> .name = "dma page reg",
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 [this message]
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
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=aPfivybVYb-1_tlk@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