|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 5/6] xen/arm: don't iomem_permit_access for reserved-memory regions
On 22.06.19 02:56, Stefano Stabellini wrote: Hi, Stefano
This filter doesn't catch child nodes if the "reserved-memory" node has ones.
Here is my "reserved-memory" node:
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
/* device specific region for Lossy Decompression */
lossy_decompress: linux,lossy_decompress@54000000 {
no-map;
reg = <0x00000000 0x54000000 0x0 0x03000000>;
};
/* For Audio DSP */
adsp_reserved: linux,adsp@57000000 {
compatible = "shared-dma-pool";
reusable;
reg = <0x00000000 0x57000000 0x0 0x01000000>;
};
/* global autoconfigured region for contiguous allocations */
linux,cma@58000000 {
compatible = "shared-dma-pool";
reusable;
reg = <0x00000000 0x58000000 0x0 0x18000000>;
linux,cma-default;
};
/* device specific region for contiguous allocations */
mmp_reserved: linux,multimedia@70000000 {
compatible = "shared-dma-pool";
reusable;
reg = <0x00000000 0x70000000 0x0 0x10000000>;
};
};
So, the dt_node_name(dev) for child nodes are:
- linux,lossy_decompress
- linux,adsp
- linux,cma
- linux,multimedia
Probably, we should check whether the parent node is "reserved-memory"
as well.
-- Regards, Oleksandr Tyshchenko _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |