RFC on writel and writel_relaxed
arnd at arndb.de
Fri Mar 30 03:29:32 AEDT 2018
On Thu, Mar 29, 2018 at 3:56 PM, Sinan Kaya <okaya at codeaurora.org> wrote:
> On 3/28/2018 11:55 AM, David Miller wrote:
>> From: Benjamin Herrenschmidt <benh at kernel.crashing.org>
>> Date: Thu, 29 Mar 2018 02:13:16 +1100
>>> Let's fix all archs, it's way easier than fixing all drivers. Half of
>>> the archs are unused or dead anyway.
> I pinged most of the maintainers yesterday.
> Which arches do we care about these days?
> I have not been paying attention any other architecture besides arm64.
> arch status detail
> ------ ------------- ------------------------------------
> alpha question sent
I'm guessing alpha has problems
extern inline u32 readl(const volatile void __iomem *addr)
u32 ret = __raw_readl(addr);
extern inline void writel(u32 b, volatile void __iomem *addr)
There is a barrier in writel /after/ the acess but not before.
> arc question sent ysato at users.sourceforge.jp will fix it.
> arm no issues
> arm64 no issues
> blackfin question sent about to be removed
> c6x question sent
no PCI, so it might not matter that much -- all drivers
are platform specific in the end.
> cris question sent
cris and frv are getting removed
> h8300 question sent
> hexagon question sent
> ia64 no issues confirmed by Tony Luck
> m68k question sent
> microblaze question sent
> mips question sent
I'm guessing that some mips platforms have problems, but others don't.
> mn10300 question sent
> nios2 question sent
> openrisc no issues shorne at gmail.com says should no issues
> parisc no issues grantgrundler at gmail.com says most probably no problem but still looking
> powerpc no issues
> riscv question sent
riscv should be fine
> s390 question sent
Pretty sure this is also fine
> score question sent
> sh question sent
> sparc question sent
> tile question sent
> unicore32 question sent
Note the maintainer's new email address in linux-next.
> x86 no issues
> xtensa question sent
More information about the Linuxppc-dev