From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: lst@pengutronix.de
Subject: [PATCH RFC 00/12] ARM64: layerscape: make LS1046 DMA coherent
Date: Tue, 21 Feb 2023 09:05:12 +0100 [thread overview]
Message-ID: <20230221080524.607241-1-a.fatoum@pengutronix.de> (raw)
Upstream DT changes /soc of NXP Layerscape LS1046A to be dma-coherent.
This means that:
1) Linux v6.1 expects bootloader to configure DMA masters to snoop caches
2) bootloader needs to skip cache maintenance when talking to DMA
master when it has set snoop bits
This series does that and thereby restores USB functionality when
booting Linux v6.1 with barebox. For older kernels, dma-coherent is
fixed up into kernel DT, so newer barebox versions can boot both
kernels.
This series still needs some more testing, but it's fit for review IMO.
One thing I wasn't sure about is whether I need memory barriers in
dma_sync_single. I don't see the kernel using any though in the same
situation.
Let me know what you think.
Ahmad Fatoum (12):
usb: dwc3: populate parent of xHCI dev
usb: xhci: pass physical device to DMA API
net: rtl8169: pass physical device for DMA API
firmware: zynqmp-fpga: pass physical device to DMA API
net: designware: eqos: pass physical device to DMA API
x86: select OF_DMA_DEFAULT_COHERENT
dma: define CONFIG_OF_DMA_COHERENCY
RISC-V: StarFive: J7100: set /soc/dma-noncoherent
of: populate new device_d::dma_coherent attribute
dma: fix dma_sync when not all device DMA is equally coherent
dma: provide of_dma_coherent_fixup helper
ARM64: layerscape: configure all DMA masters to be cache-coherent
arch/arm/Kconfig | 1 +
arch/arm/mach-layerscape/Makefile | 1 +
arch/arm/mach-layerscape/dma-coherent.c | 20 +++++++++++
arch/arm/mach-layerscape/lowlevel-ls1046a.c | 10 +++---
arch/riscv/Kconfig.socs | 1 +
arch/riscv/dts/jh7100.dtsi | 1 +
arch/x86/Kconfig | 1 +
commands/devinfo.c | 5 +++
drivers/base/resource.c | 6 ++--
drivers/dma/Kconfig | 10 ++++++
drivers/dma/Makefile | 1 +
drivers/dma/map.c | 6 ++--
drivers/dma/of_fixups.c | 16 +++++++++
drivers/firmware/zynqmp-fpga.c | 7 ++--
drivers/net/designware_eqos.c | 13 ++++---
drivers/net/rtl8169.c | 9 ++---
drivers/of/platform.c | 3 ++
drivers/usb/dwc3/host.c | 8 ++---
drivers/usb/host/xhci-ring.c | 8 ++---
drivers/usb/host/xhci.c | 6 +++-
include/driver.h | 40 +++++++++++++++++++--
include/of_address.h | 8 +++++
include/soc/fsl/immap_lsch2.h | 7 ++++
23 files changed, 155 insertions(+), 33 deletions(-)
create mode 100644 arch/arm/mach-layerscape/dma-coherent.c
create mode 100644 drivers/dma/of_fixups.c
--
2.30.2
next reply other threads:[~2023-02-21 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 8:05 Ahmad Fatoum [this message]
2023-02-21 8:05 ` [PATCH RFC 01/12] usb: dwc3: populate parent of xHCI dev Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 02/12] usb: xhci: pass physical device to DMA API Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 03/12] net: rtl8169: pass physical device for " Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 04/12] firmware: zynqmp-fpga: pass physical device to " Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 05/12] net: designware: eqos: " Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 06/12] x86: select OF_DMA_DEFAULT_COHERENT Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 07/12] dma: define CONFIG_OF_DMA_COHERENCY Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 08/12] RISC-V: StarFive: J7100: set /soc/dma-noncoherent Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 09/12] of: populate new device_d::dma_coherent attribute Ahmad Fatoum
2023-02-27 10:41 ` Sascha Hauer
2024-01-11 7:05 ` Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 10/12] dma: fix dma_sync when not all device DMA is equally coherent Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 11/12] dma: provide of_dma_coherent_fixup helper Ahmad Fatoum
2023-02-21 8:05 ` [PATCH RFC 12/12] ARM64: layerscape: configure all DMA masters to be cache-coherent Ahmad Fatoum
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=20230221080524.607241-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=lst@pengutronix.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