Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Arnd Bergmann <arnd@arndb.de>, Baoquan He <bhe@redhat.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: pci-legacy: Override pci_address_to_pio
Date: Sun, 19 Jan 2025 12:42:30 +0100	[thread overview]
Message-ID: <017febf1-b801-4bdf-99bc-2e3c348c6643@o2.pl> (raw)
In-Reply-To: <6946ae6b-814c-4916-9428-e823c83aed3d@o2.pl>

W dniu 14.01.2025 o 19:42, Mateusz Jończyk pisze:
> W dniu 14.01.2025 o 19:11, Jiaxun Yang pisze:
>> pci-legacy systems are not using logic_pio to managed PIO
>> allocations, thus the generic pci_address_to_pio won't work
>> when PCI_IOBASE is defined.
>>
>> Override the function to use architecture implementation to
>> fix the problem.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: 4bfb53e7d317 ("mips: add <asm-generic/io.h> including")
>> Reported-by: Mateusz Jończyk <mat.jonczyk@o2.pl>
>> Closes: 
>> https://lore.kernel.org/r/99f75c66-4c2d-45dc-a808-b5ba440c7551@app.fastmail.com/
>> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>

Hello,

Tested on:

- mips64el, QEMU malta - RTC is working, no suspicious warnings in dmesg,

- mipsel, QEMU malta - RTC is working, no suspicious warnings in dmesg,

- fuloong2e_defconfig, in QEMU on Ubuntu 24.04 - kernel does not boot, 
with or without this patch:

         [...]
         pps_core: LinuxPPS API ver. 1 registered
         pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo 
Giometti <giometti@linux.it>
         PTP clock support registered
         PCI host bridge to bus 0000:00
         pci_bus 0000:00: root bus resource [mem 0x14000000-0x1c000000]
         pci_bus 0000:00: root bus resource [io  0x4000-0xffff]
         pci_bus 0000:00: No busn resource found for root bus, will use 
[bus 00-ff]
         pci 0000:00:00.0: [df53:00d5] type 00 class 0x060000 
conventional PCI endpoint
         pci 0000:00:05.0: [1106:0686] type 00 class 0x060100 
conventional PCI endpoint
         qemu-system-mips64el: hw/pci/pci.c:297: 
pci_bus_change_irq_level: Assertion `irq_num < bus->nirq' failed.

- loongson3_defconfig, in QEMU (target loongson3-virt) - no important 
differences in dmesg output, but this
   platform does not use RTC CMOS, but a Goldfish RTC,

Greetings,

Mateusz


  parent reply	other threads:[~2025-01-19 11:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 18:11 [PATCH] MIPS: pci-legacy: Override pci_address_to_pio Jiaxun Yang
2025-01-14 18:42 ` Mateusz Jończyk
2025-01-14 18:51   ` Jiaxun Yang
2025-01-19 11:42   ` Mateusz Jończyk [this message]
2025-01-14 18:46 ` Greg KH
2025-01-14 18:55   ` Jiaxun Yang
2025-01-14 19:03 ` Arnd Bergmann
2025-01-14 19:20   ` Jiaxun Yang
2025-01-15  7:38     ` Arnd Bergmann
2025-01-15  8:57       ` Maciej W. Rozycki
2025-01-15  9:26       ` Jiaxun Yang
2025-01-20 19:41 ` 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=017febf1-b801-4bdf-99bc-2e3c348c6643@o2.pl \
    --to=mat.jonczyk@o2.pl \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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