summaryrefslogtreecommitdiff
path: root/drivers/net/wwan/iosm/iosm_ipc_protocol.c
diff options
context:
space:
mode:
authorNiklas Schnelle <schnelle@linux.ibm.com>2025-02-21 12:51:48 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-04-10 14:39:18 +0200
commit088a200ebf465a9699f6fd854a691159a9af9e56 (patch)
tree7ace7655a1795470cb85faf4bad576e16f4f68a2 /drivers/net/wwan/iosm/iosm_ipc_protocol.c
parentbd717b4dea872df69eef7d7c08e76089d99744e2 (diff)
s390: Remove ioremap_wt() and pgprot_writethrough()
[ Upstream commit c94bff63e49302d4ce36502a85a2710a67332a4f ] It turns out that while s390 architecture calls its memory-I/O mapping variants write-through and write-back the implementation of ioremap_wt() and pgprot_writethrough() does not match Linux notion of ioremap_wt(). In particular Linux expects ioremap_wt() to be weaker still than ioremap_wc(), allowing not just gathering and re-ordering but also reads to be served from cache. Instead s390's implementation is equivalent to normal ioremap() while its ioremap_wc() allows re-ordering. Note that there are no known users of ioremap_wt() on s390 and the resulting behavior is in line with asm-generic defining ioremap_wt() as ioremap(), if undefined, so no breakage is expected. As s390 does not have a mapping type matching the Linux notion of ioremap_wt() and pgprot_writethrough(), simply drop them and rely on the asm-generic fallbacks instead. Fixes: b02002cc4c0f ("s390/pci: Implement ioremap_wc/prot() with MIO") Fixes: b43b3fff042d ("s390: mm: convert to GENERIC_IOREMAP") Acked-by: Heiko Carstens <hca@linux.ibm.com> Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/net/wwan/iosm/iosm_ipc_protocol.c')
0 files changed, 0 insertions, 0 deletions