[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1508416718.7665.14.camel@pengutronix.de>
Date: Thu, 19 Oct 2017 14:38:38 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Matthias Brugger <matthias.bgg@...il.com>,
ulrich.hecht+renesas@...il.com, laurent.pinchart@...asonboard.com,
ck.hu@...iatek.com, airlied@...ux.ie, robh+dt@...nel.org,
mark.rutland@....com
Cc: 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
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";
Same comment as for patch 1, I'd prefer the node to be called
"display-
subsystem" instead.
With that changed,
Acked-by: Philipp Zabel <p.zabel@...gutronix.de>
> + mediatek,mmsys = <&mmsys>;
> + }
> +
> mdp_rdma0: rdma@...01000 {
> compatible = "mediatek,mt8173-mdp-rdma",
> "mediatek,mt8173-mdp";
regards
Philipp
Powered by blists - more mailing lists