From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: robh+dt@kernel.org, catalin.marinas@arm.com, hch@lst.de,
robin.murphy@arm.com, devicetree@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-mm@kvack.org,
Frank Rowand <frowand.list@gmail.com>
Cc: will@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: [PATCH 1/4] of/fdt: Update zone_dma_bits when running in bcm2711
Date: Thu, 1 Oct 2020 18:17:37 +0200 [thread overview]
Message-ID: <20201001161740.29064-2-nsaenzjulienne@suse.de> (raw)
In-Reply-To: <20201001161740.29064-1-nsaenzjulienne@suse.de>
arm64 wants to be able to set ZONE_DMA's size depending on the specific
platform its being run on. Ideally this could be achieved in a smart way
by parsing all dma-ranges and calculating the smaller DMA constraint in
the system. Easier said than done. We compromised on a simpler solution
as the only platform interested in using this is the Raspberry Pi 4.
So update zone_dma_bits if the machine's compatible string matches
Raspberry Pi 4's, otherwise let arm64's mm code deal with it.
Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
---
drivers/of/fdt.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 4602e467ca8b..cd0d115ef329 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -25,6 +25,7 @@
#include <linux/serial_core.h>
#include <linux/sysfs.h>
#include <linux/random.h>
+#include <linux/dma-direct.h> /* for zone_dma_bits */
#include <asm/setup.h> /* for COMMAND_LINE_SIZE */
#include <asm/page.h>
@@ -1198,6 +1199,14 @@ void __init early_init_dt_scan_nodes(void)
of_scan_flat_dt(early_init_dt_scan_memory, NULL);
}
+void __init early_init_dt_update_zone_dma_bits(void)
+{
+ unsigned long dt_root = of_get_flat_dt_root();
+
+ if (of_flat_dt_is_compatible(dt_root, "brcm,bcm2711"))
+ zone_dma_bits = 30;
+}
+
bool __init early_init_dt_scan(void *params)
{
bool status;
@@ -1207,6 +1216,7 @@ bool __init early_init_dt_scan(void *params)
return false;
early_init_dt_scan_nodes();
+ early_init_dt_update_zone_dma_bits();
return true;
}
--
2.28.0
next prev parent reply other threads:[~2020-10-01 16:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 16:17 [PATCH 0/4] arm64: Default to 32-bit wide ZONE_DMA Nicolas Saenz Julienne
2020-10-01 16:17 ` Nicolas Saenz Julienne [this message]
2020-10-01 17:15 ` [PATCH 1/4] of/fdt: Update zone_dma_bits when running in bcm2711 Catalin Marinas
2020-10-01 17:23 ` Catalin Marinas
2020-10-01 17:31 ` Nicolas Saenz Julienne
2020-10-01 20:02 ` Rob Herring
2020-10-02 11:55 ` Catalin Marinas
2020-10-08 10:05 ` Nicolas Saenz Julienne
2020-10-08 10:13 ` Catalin Marinas
2020-10-08 19:43 ` Ard Biesheuvel
2020-10-09 3:59 ` Jeremy Linton
2020-10-09 8:37 ` Nicolas Saenz Julienne
2020-10-09 7:10 ` Christoph Hellwig
2020-10-09 7:37 ` Ard Biesheuvel
2020-10-09 8:36 ` Nicolas Saenz Julienne
2020-10-09 9:13 ` Ard Biesheuvel
2020-10-09 13:33 ` Nicolas Saenz Julienne
2020-10-09 15:24 ` Lorenzo Pieralisi
2020-10-09 16:23 ` Ard Biesheuvel
2020-10-09 17:10 ` Catalin Marinas
2020-10-10 10:36 ` Ard Biesheuvel
2020-10-10 10:53 ` Nicolas Saenz Julienne
2020-10-10 12:38 ` Catalin Marinas
2020-10-12 6:47 ` Christoph Hellwig
2020-10-12 8:47 ` Catalin Marinas
2020-10-02 9:05 ` kernel test robot
2020-10-01 16:17 ` [PATCH 2/4] dma-direct: Turn zone_dma_bits default value into a define Nicolas Saenz Julienne
2020-10-01 16:17 ` [PATCH 3/4] arm64: Default to 32-bit ZONE_DMA Nicolas Saenz Julienne
2020-10-01 17:19 ` Catalin Marinas
2020-10-01 16:17 ` [PATCH 4/4] mm: Update DMA zones description Nicolas Saenz Julienne
2020-10-01 17:19 ` Catalin Marinas
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=20201001161740.29064-2-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).