[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1508491009.23296.2.camel@mtksdaap41>
Date: Fri, 20 Oct 2017 17:16:49 +0800
From: CK Hu <ck.hu@...iatek.com>
To: Matthias Brugger <matthias.bgg@...il.com>
CC: <ulrich.hecht+renesas@...il.com>,
<laurent.pinchart@...asonboard.com>, <p.zabel@...gutronix.de>,
<airlied@...ux.ie>, <robh+dt@...nel.org>, <mark.rutland@....com>,
<linux@...linux.org.uk>, <catalin.marinas@....com>,
<will.deacon@....com>, <dri-devel@...ts.freedesktop.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
Matthias Brugger <mbrugger@...e.com>
Subject: Re: [RFC resend 3/4] arm64: dts: mt8173: Fix drm subsystem
Hi, Matthias:
On Thu, 2017-10-19 at 13:26 +0200, Matthias Brugger wrote:
> DRM subysystem and clock driver shared the same compatible mmsys.
> This stopped does not work, as only the first driver for a compatible
> gets probed. We change the comaptible to the new DRM identifier to fix
> this.
>
> Signed-off-by: Matthias Brugger <mbrugger@...e.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> index b99a27372965..89db0a3f5950 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> @@ -803,6 +803,11 @@
> #clock-cells = <1>;
> };
>
> + dispsys: display-system {
> + compatible = "mediatek,mt2701-dispsys";
Why do you probe "mediatek,mt2701-dispsys" in mt8173.dtsi?
Regards,
CK
> + mediatek,mmsys = <&mmsys>;
> + }
> +
> mdp_rdma0: rdma@...01000 {
> compatible = "mediatek,mt8173-mdp-rdma",
> "mediatek,mt8173-mdp";
Powered by blists - more mailing lists