[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <160587230018.19468.15360551479275381470.b4-ty@arm.com>
Date: Fri, 20 Nov 2020 11:39:34 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
linux-kernel@...r.kernel.org, robh+dt@...nel.org, ardb@...nel.org,
hch@....de
Cc: Will Deacon <will@...nel.org>, devicetree@...r.kernel.org,
linux-rpi-kernel@...ts.infradead.org, linux-acpi@...r.kernel.org,
robin.murphy@....com, jeremy.linton@....com,
iommu@...ts.linux-foundation.org, linux-riscv@...ts.infradead.org,
lorenzo.pieralisi@....com, linux-mm@...ck.org,
guohanjun@...wei.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v7 0/7] arm64: Default to 32-bit wide ZONE_DMA
On Thu, 19 Nov 2020 18:53:52 +0100, Nicolas Saenz Julienne wrote:
> Using two distinct DMA zones turned out to be problematic. Here's an
> attempt go back to a saner default.
>
> I tested this on both a RPi4 and QEMU.
Applied to arm64 (for-next/zone-dma-default-32-bit), thanks!
[1/7] arm64: mm: Move reserve_crashkernel() into mem_init()
https://git.kernel.org/arm64/c/0a30c53573b0
[2/7] arm64: mm: Move zone_dma_bits initialization into zone_sizes_init()
https://git.kernel.org/arm64/c/9804f8c69b04
[3/7] of/address: Introduce of_dma_get_max_cpu_address()
https://git.kernel.org/arm64/c/964db79d6c18
[4/7] of: unittest: Add test for of_dma_get_max_cpu_address()
https://git.kernel.org/arm64/c/07d13a1d6120
[5/7] arm64: mm: Set ZONE_DMA size based on devicetree's dma-ranges
https://git.kernel.org/arm64/c/8424ecdde7df
[6/7] arm64: mm: Set ZONE_DMA size based on early IORT scan
https://git.kernel.org/arm64/c/2b8652936f0c
[7/7] mm: Remove examples from enum zone_type comment
https://git.kernel.org/arm64/c/04435217f968
--
Catalin
Powered by blists - more mailing lists