linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Tiwei Bie" <tiwei.btw@antgroup.com>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Richard Weinberger" <richard@nod.at>,
	"Anton Ivanov" <anton.ivanov@cambridgegreys.com>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	linux-um@lists.infradead.org, "kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] um: Turn HAS_IOPORT_MAP off
Date: Wed, 02 Jul 2025 15:39:20 +0200	[thread overview]
Message-ID: <49982e79-957d-401b-882c-849d2892bf4c@app.fastmail.com> (raw)
In-Reply-To: <dcb0d307-a0cf-480e-888f-1020d1441d1d@antgroup.com>

On Wed, Jul 2, 2025, at 15:02, Tiwei Bie wrote:
> On 2025/7/2 19:09, Arnd Bergmann wrote:
>> On Tue, Jul 1, 2025, at 14:22, Tiwei Bie wrote:
>> xtensa selects NO_IOPORT_MAP, which means that HAS_IOPORT_MAP
>> gets disabled here:
>> 
>> arch/xtensa/Kconfig:config NO_IOPORT_MAP
>> arch/xtensa/Kconfig-    def_bool n
>
> The value of NO_IOPORT_MAP on xtensa is inverted compared to that
> on most other platforms that explicitly defines NO_IOPORT_MAP.

Ah of course, sorry for misunderstanding. Apparently this only
existed because it was selected by a long gone platform:

-config XTENSA_PLATFORM_S6105
-       bool "S6105"
-       select HAVE_IDE
-       select SERIAL_CONSOLE
-       select NO_IOPORT_MAP

Before commits

d38efc1f150f ("xtensa: adopt generic io routines")
d046f77ec4a4 ("xtensa: set NO_IOPORT to 'n' by default")

it was always-on, and I think the idea at the time was to
make it behave more like the generic PCI code, while it
was originally copied from sparc, which does things quite
differently.

It is rather clear that the I/O port implementation on
xtensa never actually worked, and some of the comments
on its PCI code suggest that it was never really used
either.

    Arnd


  reply	other threads:[~2025-07-02 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 16:47 [PATCH] um: Turn HAS_IOPORT_MAP off Tiwei Bie
2025-07-01  8:26 ` Geert Uytterhoeven
2025-07-01  8:43   ` Arnd Bergmann
2025-07-01 12:22     ` Tiwei Bie
2025-07-02 11:09       ` Arnd Bergmann
2025-07-02 13:02         ` Tiwei Bie
2025-07-02 13:39           ` Arnd Bergmann [this message]
2025-07-02 15:02             ` Tiwei Bie

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=49982e79-957d-401b-882c-849d2892bf4c@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=geert@linux-m68k.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-um@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=richard@nod.at \
    --cc=tiwei.btw@antgroup.com \
    /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).