From: Michael Ellerman <mpe@ellerman.id.au>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, linux-mm@kvack.org, arnd@arndb.de,
geert@linux-m68k.org, mcgrof@kernel.org, hch@infradead.org,
Baoquan He <bhe@redhat.com>,
linux-alpha@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures
Date: Sun, 05 Mar 2023 20:23:05 +1100 [thread overview]
Message-ID: <87sfej1rie.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20230303102817.212148-3-bhe@redhat.com>
Baoquan He <bhe@redhat.com> writes:
> ioremap_uc() is only meaningful on old x86-32 systems with the PAT
> extension, and on ia64 with its slightly unconventional ioremap()
> behavior, everywhere else this is the same as ioremap() anyway.
>
> Here, remove the ioremap_uc() definition in architecutures other
> than x86 and ia64. These architectures all have asm-generic/io.h
> included and will have the default ioremap_uc() definition which
> returns NULL.
>
> Note: This changes the existing behaviour and could break code
> calling ioremap_uc(). If any ARCH meets this breakage and really
> needs a specific ioremap_uc() for its own usage, one ioremap_uc()
> can be added in the ARCH.
I see one use in:
drivers/video/fbdev/aty/atyfb_base.c: par->ati_regbase = ioremap_uc(info->fix.mmio_start, 0x1000);
Which isn't obviously x86/ia64 specific.
I'm pretty sure some powermacs (powerpc) use that driver.
Maybe that exact code path is only reachable on x86/ia64? But if so
please explain why.
Otherwise it looks like this series could break that driver on powerpc
at least.
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Baoquan He <bhe@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, Baoquan He <bhe@redhat.com>,
arnd@arndb.de, linux-sh@vger.kernel.org,
linux-hexagon@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, hch@infradead.org,
linux-mm@kvack.org, mcgrof@kernel.org, geert@linux-m68k.org,
linux-parisc@vger.kernel.org, linux-alpha@vger.kernel.org,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures
Date: Sun, 05 Mar 2023 20:23:05 +1100 [thread overview]
Message-ID: <87sfej1rie.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20230303102817.212148-3-bhe@redhat.com>
Baoquan He <bhe@redhat.com> writes:
> ioremap_uc() is only meaningful on old x86-32 systems with the PAT
> extension, and on ia64 with its slightly unconventional ioremap()
> behavior, everywhere else this is the same as ioremap() anyway.
>
> Here, remove the ioremap_uc() definition in architecutures other
> than x86 and ia64. These architectures all have asm-generic/io.h
> included and will have the default ioremap_uc() definition which
> returns NULL.
>
> Note: This changes the existing behaviour and could break code
> calling ioremap_uc(). If any ARCH meets this breakage and really
> needs a specific ioremap_uc() for its own usage, one ioremap_uc()
> can be added in the ARCH.
I see one use in:
drivers/video/fbdev/aty/atyfb_base.c: par->ati_regbase = ioremap_uc(info->fix.mmio_start, 0x1000);
Which isn't obviously x86/ia64 specific.
I'm pretty sure some powermacs (powerpc) use that driver.
Maybe that exact code path is only reachable on x86/ia64? But if so
please explain why.
Otherwise it looks like this series could break that driver on powerpc
at least.
cheers
next prev parent reply other threads:[~2023-03-05 9:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 10:28 [PATCH v3 0/2] arch/*/io.h: remove ioremap_uc in some architectures Baoquan He
2023-03-03 10:28 ` [PATCH v3 1/2] mips: add <asm-generic/io.h> including Baoquan He
2023-03-03 12:40 ` Arnd Bergmann
2023-03-06 8:46 ` Baoquan He
2023-03-03 10:28 ` [PATCH v3 2/2] arch/*/io.h: remove ioremap_uc in some architectures Baoquan He
2023-03-03 10:28 ` Baoquan He
2023-03-05 9:23 ` Michael Ellerman [this message]
2023-03-05 9:23 ` Michael Ellerman
2023-03-05 9:29 ` Geert Uytterhoeven
2023-03-05 9:29 ` Geert Uytterhoeven
2023-03-05 9:29 ` Geert Uytterhoeven
2023-03-05 20:10 ` Arnd Bergmann
2023-03-05 20:10 ` Arnd Bergmann
2023-03-05 20:10 ` Arnd Bergmann
2023-03-07 0:58 ` Michael Ellerman
2023-03-07 0:58 ` Michael Ellerman
2023-03-07 0:58 ` Michael Ellerman
2023-03-07 1:30 ` Baoquan He
2023-03-07 1:30 ` Baoquan He
2023-03-07 1:30 ` Baoquan He
2023-03-07 7:17 ` Arnd Bergmann
2023-03-07 7:17 ` Arnd Bergmann
2023-03-07 7:17 ` 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=87sfej1rie.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcgrof@kernel.org \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.