From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Mateusz Jończyk" <mat.jonczyk@o2.pl>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
"Baoquan He" <bhe@redhat.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] mipsel: no RTC CMOS on the Malta platform in QEMU
Date: Tue, 14 Jan 2025 10:09:26 +0000 [thread overview]
Message-ID: <12aa35c3-3f74-40bf-9fa1-7540aa4292c3@app.fastmail.com> (raw)
In-Reply-To: <CAMuHMdXbuRLgDP2JtmdhnJF=AhpPa88356KU1yF1f8GMirWrcQ@mail.gmail.com>
在2025年1月14日一月 上午8:02,Geert Uytterhoeven写道:
> Hi Jiaxun,
[...]
>>
>> You are right, this is what should be done.
>>
>> A quick fix would be #undef PCI_IOBASE in arch/mips/include/asm/io.h
>> just after including #include <asm-generic/io.h>, with ralink and loongson64
>> as exception.
>
> Shouldn't arch/mips/include/asm/io.h do
>
> #define PCI_IOBASE mips_io_port_base
>
> unconditionally, _before_ including <asm-generic/io.h>?
The problem here is defining PCI_IOBASE implied use of logic_pio and VM mapped
io access, which is not true for many MIPS systems...
>
>> In the long term, we should scrutinize platform usage of mips_io_base
>> following ralink's approach.
>
> Currently ralink handles that in a mach-specific include:
>
> arch/mips/include/asm/mach-ralink/spaces.h:#define PCI_IOBASE
> mips_io_port_base
>
> Loongson does it differently:
>
> arch/mips/include/asm/mach-loongson64/spaces.h:#define PCI_IOBASE
> _AC(0xc000000000000000 + SZ_128K, UL)
>
> But still sets mips_io_port_base in prom_init():
>
> arch/mips/loongson64/init.c: set_io_port_base(PCI_IOBASE);
>
> so defining PCI_IOBASE to mips_io_port_base in the main <asm/io.h>
> should work.
Yes, we need to make sure malta problem won't happen on other platforms
before making this definition.
Thanks
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
--
- Jiaxun
next prev parent reply other threads:[~2025-01-14 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 22:16 [REGRESSION] mipsel: no RTC CMOS on the Malta platform in QEMU Mateusz Jończyk
2025-01-13 23:29 ` Jiaxun Yang
2025-01-14 7:01 ` Arnd Bergmann
2025-01-14 8:02 ` Geert Uytterhoeven
2025-01-14 9:59 ` Arnd Bergmann
2025-01-14 10:22 ` Jiaxun Yang
2025-01-14 16:11 ` Maciej W. Rozycki
2025-01-14 17:04 ` Arnd Bergmann
2025-01-14 19:10 ` Maciej W. Rozycki
2025-01-15 8:15 ` Arnd Bergmann
2025-01-14 17:56 ` Jiaxun Yang
2025-01-14 10:09 ` Jiaxun Yang [this message]
2025-01-14 10:30 ` Arnd Bergmann
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=12aa35c3-3f74-40bf-9fa1-7540aa4292c3@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
--cc=regressions@lists.linux.dev \
--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