[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-5335a61e-b8f0-4441-9fe9-0827cdd67ce4-1596562816887@3c-app-gmx-bap28>
Date: Tue, 4 Aug 2020 19:40:16 +0200
From: Frank Wunderlich <frank-w@...lic-files.de>
To: David Woodhouse <dwmw2@...radead.org>
Cc: Frank Wunderlich <linux@...web.de>,
linux-mediatek@...ts.infradead.org,
Chun-Kuang Hu <chunkuang.hu@...nel.org>,
Ryder Lee <ryder.lee@...iatek.com>,
Daniel Vetter <daniel@...ll.ch>,
chunhui dai <chunhui.dai@...iatek.com>,
David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
Matthias Brugger <matthias.bgg@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
CK Hu <ck.hu@...iatek.com>,
Bibby Hsieh <bibby.hsieh@...iatek.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Aw: Re: [PATCH v4 6/6] arm: dts: mt7623: add display subsystem
related device nodes
> Gesendet: Dienstag, 04. August 2020 um 19:24 Uhr
> Von: "David Woodhouse" <dwmw2@...radead.org>
> > + mipi_tx0: mipi-dphy@...10000 {
> > + compatible = "mediatek,mt7623-mipi-tx",
> > + "mediatek,mt2701-mipi-tx";
> > + reg = <0 0x10010000 0 0x90>;
> > + clocks = <&clk26m>;
> > + clock-output-names = "mipi_tx0_pll";
> > + #clock-cells = <0>;
> > + #phy-cells = <0>;
> > + };
>
> Doesn't this (and some others) also need status="disabled" since
> they're not present on MT7623A? Or maybe it's time to split mt7623.dtsi
> into a mt7623n.dtsi which includes mt7623a.dtsi and adds the extra
> components?
do you have a MT7623A board for testing? is there any list which components are existing on mt7623a? or should i disable all of them and re-enable them in bpi-r2 dts?
regards Frank
Powered by blists - more mailing lists