mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: lst@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH RFC 09/12] of: populate new device_d::dma_coherent attribute
Date: Tue, 21 Feb 2023 09:05:21 +0100	[thread overview]
Message-ID: <20230221080524.607241-10-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20230221080524.607241-1-a.fatoum@pengutronix.de>

So far, whether device DMA is coherent was a one-time global decision.
This is insufficient, because some platforms:

 - are cache coherent, while the architecture isn't in general, e.g. ARM
   with CONFIG_MMU=y assumes non-coherent DMA, but LS1046A is coherent

 - have a mix of devices that snoop caches and devices that don't
   (StarFive JH7100).

To enable dev_dma_(map|unmap)_single to take the correct device-specific
action with regards to cache maintenance, provide dev_is_dma_coherent()
with semantics similar to what Linux provides.

This admittedly looks a bit ugly, but we will refrain from making
dma_coherent defined independent of ifdef CONFIG_ARCH_HAS_NONCOHERENT_DMA:
On platforms that are cache-coherent, we will want dev->dma_coherent to
be true. Yet not all code allocating devices uses dev_alloc(), so adding
a global toggle is a bit too much refactoring effort for now.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 commands/devinfo.c    |  5 +++++
 drivers/of/platform.c |  3 +++
 include/driver.h      | 28 ++++++++++++++++++++++++++++
 3 files changed, 36 insertions(+)

diff --git a/commands/devinfo.c b/commands/devinfo.c
index 2487786c7101..be28d02028c3 100644
--- a/commands/devinfo.c
+++ b/commands/devinfo.c
@@ -50,6 +50,7 @@ static int do_devinfo(int argc, char *argv[])
 	struct param_d *param;
 	int i;
 	int first;
+	int coherent;
 	struct resource *res;
 
 	if (argc == 1) {
@@ -82,6 +83,10 @@ static int do_devinfo(int argc, char *argv[])
 		if (dev->bus)
 			printf("Bus: %s\n", dev->bus->name);
 
+		coherent = dev_is_dma_coherent(dev);
+		if (coherent >= 0)
+			printf("DMA Coherent: %s\n", coherent ? "true" : "false");
+
 		if (dev->info)
 			dev->info(dev);
 
diff --git a/drivers/of/platform.c b/drivers/of/platform.c
index 0982873446a6..1bd5d41ba226 100644
--- a/drivers/of/platform.c
+++ b/drivers/of/platform.c
@@ -128,6 +128,9 @@ static void of_dma_configure(struct device *dev, struct device_node *np)
 	}
 
 	dev->dma_offset = offset;
+#ifdef CONFIG_OF_DMA_COHERENCY
+	dev->dma_coherent = of_dma_is_coherent(np);
+#endif
 }
 
 /**
diff --git a/include/driver.h b/include/driver.h
index 7e25c060280b..f6301d954bb5 100644
--- a/include/driver.h
+++ b/include/driver.h
@@ -8,6 +8,7 @@
 
 #include <linux/list.h>
 #include <linux/ioport.h>
+#include <linux/bitops.h>
 #include <of.h>
 #include <filetype.h>
 
@@ -43,6 +44,13 @@ struct device {
 	 * something like eth0 or nor0. */
 	int id;
 
+	/*! This particular device is dma coherent, even if the
+         * architecture supports non-coherent devices.
+	 */
+#ifdef CONFIG_OF_DMA_COHERENCY
+	bool dma_coherent:1;
+#endif
+
 	struct resource *resource;
 	int num_resources;
 
@@ -652,6 +660,26 @@ static inline struct device_node *dev_of_node(struct device *dev)
 	return IS_ENABLED(CONFIG_OFDEVICE) ? dev->of_node : NULL;
 }
 
+#ifdef CONFIG_OF_DMA_COHERENCY
+static inline int __dev_is_dma_coherent(struct device *dev)
+{
+	return dev->dma_coherent;
+}
+#else
+static inline bool __dev_is_dma_coherent(struct device *dev)
+{
+	return IS_ENABLED(CONFIG_OF_DMA_DEFAULT_COHERENT);
+}
+#endif
+
+static inline int dev_is_dma_coherent(struct device *dev)
+{
+	if (!dev_of_node(dev))
+		return -EINVAL;
+
+	return __dev_is_dma_coherent(dev);
+}
+
 static inline void *dev_get_priv(const struct device *dev)
 {
 	return dev->priv;
-- 
2.30.2




  parent 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 [PATCH RFC 00/12] ARM64: layerscape: make LS1046 DMA coherent Ahmad Fatoum
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 ` Ahmad Fatoum [this message]
2023-02-27 10:41   ` [PATCH RFC 09/12] of: populate new device_d::dma_coherent attribute 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-10-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