Heiko,
? 2017?07?10? 20:12, Heiko Stuebner ??:
> The binding specifies the actual implementations only (mali-t760
> for example) but not the arm,mali-midgard used in some vendor kernels.
> So drop that compatible property from the rk3288 where it had slipped in.
>
> Signed-off-by: Heiko Stuebner <heiko at sntech.de>
> ---
> arch/arm/boot/dts/rk3288.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi
> index cb1d415d1201..e99d7ff4c939 100644
> --- a/arch/arm/boot/dts/rk3288.dtsi
> +++ b/arch/arm/boot/dts/rk3288.dtsi
> @@ -1135,7 +1135,7 @@
> };
>
> gpu: mali at ffa30000 {
> - compatible = "rockchip,rk3288-mali", "arm,mali-t760", "arm,mali-midgard";
> + compatible = "rockchip,rk3288-mali", "arm,mali-t760";
If we remove the "arm,mali-midgard", the mali driver maybe need update
first.
From the lastest MALI driver on ARM supply, the compatible only two
property.
mali_kbase_core_linux.c
4163: { .compatible = "arm,malit6xx" },
4164: { .compatible = "arm,mali-midgard" },
That's odd with the two compatible, the driver should support the more.
-Caesar
> reg = <0xffa30000 0x10000>;
> interrupts = <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>,
