Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Arnd Bergmann" <arnd@arndb.de>,
	"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 <linux-arch@vger.kernel.org>,
	linux-kernel@vger.kernel.org, "Baoquan He" <bhe@redhat.com>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.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:22:24 +0000	[thread overview]
Message-ID: <99de6ed6-2577-42d7-949d-cd5adc740dbb@app.fastmail.com> (raw)
In-Reply-To: <08fe1ebb-b9c4-46c7-a6ab-5a336ec3b771@app.fastmail.com>



在2025年1月14日一月 上午9:59,Arnd Bergmann写道:
[...]
>
> This probably requires calling set_io_port_base() with the
> actual virtual address rather than self-assigning the
> uninitialized mips_io_port_base.
>
> I assume the reason for loongson64 being different from every
> other mips platform is the same as why it calls into the
> logic_pio_register_range() directly. I don't understand that
> code, but it's probably because it has ISA/LPC devices that
> are directly wired to a non-memory-mapped set of registers
> instead of them being behind a PCI bridge like the other
> platforms. The idea of logic_pio is to have a more generic
> way to redirect arbitrary port ranges into bus specific
> function calls, where normal PCI (on non-x86) assumes that
> all I/O ports are mapped into a small contiguous ranges
> of virtual addresses.

That's correct, Loongson systems has a memory-mapped LPC bridge
accessible via MMIO. We are handling registration and mapping
process here.

It also has ioport capable PCI bridge, which will be taken care by
platform code.

I think current problem of logic_pio is it handles creation of
mappings and PIO range registration separately.

Thanks
>
>    Arnd

-- 
- Jiaxun

  reply	other threads:[~2025-01-14 10:22 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 [this message]
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
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=99de6ed6-2577-42d7-949d-cd5adc740dbb@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