diff options
| author | Yong Wu <yong.wu@mediatek.com> | 2023-04-11 17:31:43 +0800 |
|---|---|---|
| committer | Joerg Roedel <jroedel@suse.de> | 2023-04-13 11:59:28 +0200 |
| commit | 88c531b42a986c02a2630b84521d3dfe19b01686 (patch) | |
| tree | 183ed0a4d18e6b5c8d38ce956bbe19e05b215ae1 /arch/arm64/boot | |
| parent | 2aa6e5f63ea2b1768afbde763a948534c190254e (diff) | |
| download | linux-stable-88c531b42a986c02a2630b84521d3dfe19b01686.tar.gz linux-stable-88c531b42a986c02a2630b84521d3dfe19b01686.tar.bz2 linux-stable-88c531b42a986c02a2630b84521d3dfe19b01686.zip | |
arm64: dts: mt8195: Add dma-ranges for the parent "soc" node
After commit f1ad5338a4d5 ("of: Fix "dma-ranges" handling for bus
controllers"), the dma-ranges property is not allowed for
the leaf node. But our iommu/dma-ranges is 16GB, we still expect
separate the 16GB dma-range like:
a) display is in 0 - 4GB;
b) vcodec is in 4GB - 8GB;
c) camera is in 8GB - 12GB.
We can not expect all the masters add a parent node for them,
especial for the existed drivers/nodes.
Thus, we add whole the 16GB dma-ranges in the parent "soc" node.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Link: https://lore.kernel.org/r/20230411093144.2690-14-yong.wu@mediatek.com
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'arch/arm64/boot')
| -rw-r--r-- | arch/arm64/boot/dts/mediatek/mt8195.dtsi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm64/boot/dts/mediatek/mt8195.dtsi b/arch/arm64/boot/dts/mediatek/mt8195.dtsi index 89f469ba9f6c..7d87cbabc9f1 100644 --- a/arch/arm64/boot/dts/mediatek/mt8195.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8195.dtsi @@ -364,6 +364,7 @@ #size-cells = <2>; compatible = "simple-bus"; ranges; + dma-ranges = <0x0 0x0 0x0 0x0 0x4 0x0>; gic: interrupt-controller@c000000 { compatible = "arm,gic-v3"; |