[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251216030959.GA87745@shlinux88>
Date: Tue, 16 Dec 2025 11:09:59 +0800
From: Joy Zou <joy.zou@....com>
To: Oreoluwa Babatunde <oreoluwa.babatunde@....qualcomm.com>
Cc: robh@...nel.org, m.szyprowski@...sung.com, ye.li@....nxp.com,
oreoluwa.babatunde@....qualcomm.com, kernel@....qualcomm.com,
saravanak@...gle.com, akpm@...ux-foundation.org, david@...hat.com,
lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, vbabka@...e.cz,
rppt@...nel.org, surenb@...gle.com, mhocko@...e.com,
robin.murphy@....com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
iommu@...ts.linux.dev, quic_c_gdjako@...cinc.com
Subject: Re: [PATCH] of: reserved_mem: Allow reserved_mem framework detect
"cma=" kernel param
On Tue, Dec 09, 2025 at 04:20:27PM -0800, Oreoluwa Babatunde wrote:
> When initializing the default cma region, the "cma=" kernel parameter
> takes priority over a DT defined linux,cma-default region. Hence, give
> the reserved_mem framework the ability to detect this so that the DT
> defined cma region can skip initialization accordingly.
>
Hi Oreoluwa,
Have tested i.MX6ULL 9x9, i.MX6ULL 14x14, i.MX6SLL EVK and i.MX7D
SABRE-SD boards.
Before this patch, i.MX6ULL 9x9 failed to allocate CMA memory when using
"cma=" kernel parameter. After applying the patch, CMA allocation works
correctly on all tested platforms.
Tested-by: Joy Zou <joy.zou@....com>
BR
Joy Zou
> Signed-off-by: Oreoluwa Babatunde <oreoluwa.babatunde@....qualcomm.com>
> ---
> drivers/of/of_reserved_mem.c | 19 +++++++++++++++++--
> include/linux/cma.h | 1 +
> kernel/dma/contiguous.c | 16 ++++++++++------
> 3 files changed, 28 insertions(+), 8 deletions(-)
> 2.34.1
Powered by blists - more mailing lists