I found the reason for the renaming. If the kernel config CONFIG_CMA_SIZE_MBYTES is below the
given size of linux,cma item in the devicetree the new kernel rename the device to "reserved".
In my case the kernel config was:
CONFIG_CMA_SIZE_MBYTES=320
The devicetree (imx8mp.dtsi):
resmem: reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
ocram: ocram@900000 {
no-map;
reg = <0 0x900000 0 0x70000>;
};
/*
* Memory reserved for optee usage. Please do not use.
* This will be automaticky added to dtb if OP-TEE is installed.
* optee@56000000 {
* reg = <0 0x56000000 0 0x2000000>;
* no-map;
* };
*/
/* global autoconfigured region for contiguous allocations */
linux,cma {
compatible = "shared-dma-pool";
reusable;
size = <0 0x3C000000>;
alloc-ranges = <0 0x40000000 0 0xC0000000>;
linux,cma-default;
};
...
0x3C000000 is 960MiB. So it was over the 320MiB from the kernel configuration. After I changed the size to 0x14000000 the device names in /dev/dma_heap were as expect with linux,cma and linux,cma-uncached.
